1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 5fd8df6..f497c96 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -403,6 +403,7 @@ CONFIG_REGULATOR_MAX8973...
1 files changed, 15 insertions(+), 17 deletions(-) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 2e67a27..8a5cd5c 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -1,23 +1,20 @@ -C...
DesignWare MMC Controller's transfer mode should be decided at runtime instead of compile-time. So we remove this config option and read dw_mmc's register to select DMA master.
DesignWare MMC Controller's transfer mode should be decided at runtime instead of compile-time. So we remove this config option and read dw_mmc's register to select DMA master.
>> stuff atm :( > > Ping, can you please resend a...@kernel.org? Would be good to have these > working for v4.4. > > Anyways, untagging this old thread so don't expect more pings from > me on this. >
>> > This patch adds stih415 and stih416 support to multi_v7_defconfig. > This seems to drop a few options also: > > CONFIG_ARM_ARCH_TIMER Same as last comment 2: > CONFIG_ARM_ERRATA_754322 ARM_ERRATA_754322 gets selected by the mach level Kconfig of stixxxx, so ...
> savedefconfig CONFIG_ARM_ARCH_TIMER, CONFIG_EXPERIMENTAL, > CONFIG_GPIO_PL061 and CONFIG_MMC_WMT disappears. > Which suggests that these options seems to be selected by another > kconfigs or mach level. And since then the multi_v7_defconfig was not ...