forked from Minki/linux
3b4c362e5e
The Exynos ChipID driver on Exynos SoCs has only informational purpose - to expose the SoC device in sysfs. No other drivers depend on it so there is really no benefit of initializing it early. Instead, initialize everything with arch_initcall which: 1. Allows to use dev_info() as the SoC bus is present (since core_initcall), 2. Could speed things up because of execution in a SMP environment (after bringing up secondary CPUs, unlike early_initcall), 3. Reduces the amount of work to be done early, when the kernel has to bring up critical devices. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Link: https://lore.kernel.org/r/20201202195955.128633-2-krzk@kernel.org |
||
|---|---|---|
| .. | ||
| exynos4-pmu.c | ||
| exynos3250-pmu.c | ||
| exynos5250-pmu.c | ||
| exynos5420-pmu.c | ||
| exynos5422-asv.c | ||
| exynos5422-asv.h | ||
| exynos-asv.c | ||
| exynos-asv.h | ||
| exynos-chipid.c | ||
| exynos-pmu.c | ||
| exynos-pmu.h | ||
| exynos-regulator-coupler.c | ||
| Kconfig | ||
| Makefile | ||
| pm_domains.c | ||
| s3c-pm-check.c | ||
| s3c-pm-debug.c | ||