11.11.2020 13:25, Dmitry Osipenko пишет: > 11.11.2020 12:26, Krzysztof Kozlowski пишет: >>> 11.11.2020 12:04, Krzysztof Kozlowski пишет: >>>>> -obj-$(CONFIG_TEGRA124_EMC) += clk-tegra124-emc.o >>>>> +obj-$(CONFIG_ARCH_TEGRA_124_SOC) += clk-tegra124-emc.o >>>>> +obj-$(CONFIG_ARCH_TEGRA_132_SOC) += clk-tegra124-emc.o >>>> How is it related to modularization? It looks like different issue is >>>> fixed here. >>> The CONFIG_TEGRA124_EMC now could be 'm', while the clock code must be >>> built-in. The TEGRA124 EMC driver is used by T124 and T132 SoCs.\ >> Mhmm, the CONFIG_TEGRA124_EMC depends on ARCH_TEGRA_124_SOC so on the >> config !ARCH_TEGRA_124_SOC && ARCH_TEGRA_132_SOC this was not >> selected. Now it will be selected. >> > > The driver isn't exposed on ARM64 probably because nobody bothered to do > it so far. But it's not also the memory driver which depends on > clk-tegra124-emc.o, it's also the main clk/tegra/clk-tegra124.c driver > itself, which is also used by both T124/132. > Actually, it shouldn't be difficult to keep the old condition for clk-tegra124-emc.o by slightly improving the Kconfig. I'll do it in the next revision.
