[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3c2b9fb5-5ad5-4db7-81ee-9defbdf7b4f3@ti.com>
Date: Mon, 16 Jun 2025 13:57:12 +0530
From: Beleswar Prasad Padhi <b-padhi@...com>
To: Krzysztof Kozlowski <krzk@...nel.org>, <linux@...linux.org.uk>,
<arnd@...db.de>
CC: <afd@...com>, <u-kumar1@...com>, <praneeth@...com>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm: multi_v7_defconfig: Enable more OMAP related configs
On 11/06/25 15:52, Krzysztof Kozlowski wrote:
> On 11/06/2025 09:49, Beleswar Padhi wrote:
>> From: Sinthu Raja <sinthu.raja@...com>
>>
>> This allows us to use various peripherals in the TI OMAP family devices
> Which ones for example? Explain which upstream boards use which devices
> needing these.
>
>> using the multi-v7 config, instead of only with the OMAP specific
> multi_v7
>
>> defconfigs.
>>
>> Signed-off-by: Sinthu Raja <sinthu.raja@...com>
>> Signed-off-by: Beleswar Padhi <b-padhi@...com>
>> ---
>> arch/arm/configs/multi_v7_defconfig | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
>> index c79495e113c8..10ad7026bb4d 100644
>> --- a/arch/arm/configs/multi_v7_defconfig
>> +++ b/arch/arm/configs/multi_v7_defconfig
>> @@ -166,6 +166,7 @@ CONFIG_BT_MRVL_SDIO=m
>> CONFIG_BT_QCOMSMD=m
>> CONFIG_CFG80211=m
>> CONFIG_MAC80211=m
>> +CONFIG_IWLWIFI=m
>> CONFIG_RFKILL=y
>> CONFIG_RFKILL_INPUT=y
>> CONFIG_RFKILL_GPIO=y
>> @@ -788,6 +789,7 @@ CONFIG_FRAMEBUFFER_CONSOLE=y
>> CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
>> CONFIG_SOUND=m
>> CONFIG_SND=m
>> +CONFIG_SND_SOC_OMAP_HDMI=m
>> CONFIG_SND_HDA_TEGRA=m
>> CONFIG_SND_HDA_INPUT_BEEP=y
>> CONFIG_SND_HDA_PATCH_LOADER=y
>> @@ -1095,6 +1097,7 @@ CONFIG_TEGRA_IOMMU_SMMU=y
>> CONFIG_EXYNOS_IOMMU=y
>> CONFIG_QCOM_IOMMU=y
>> CONFIG_REMOTEPROC=y
>> +CONFIG_WKUP_M3_RPROC=m
>> CONFIG_OMAP_REMOTEPROC=m
>> CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
>> CONFIG_KEYSTONE_REMOTEPROC=m
>> @@ -1102,6 +1105,7 @@ CONFIG_QCOM_Q6V5_MSS=m
>> CONFIG_QCOM_SYSMON=m
>> CONFIG_QCOM_WCNSS_PIL=m
>> CONFIG_ST_REMOTEPROC=m
>> +CONFIG_OMAP_REMOTEPROC=m
>> CONFIG_RPMSG_CHAR=m
>> CONFIG_RPMSG_CTRL=m
>> CONFIG_RPMSG_QCOM_SMD=y
>> @@ -1127,6 +1131,8 @@ CONFIG_ARCH_TEGRA_3x_SOC=y
>> CONFIG_ARCH_TEGRA_114_SOC=y
>> CONFIG_ARCH_TEGRA_124_SOC=y
>> CONFIG_SOC_TI=y
>> +CONFIG_AMX3_PM=m
>> +CONFIG_WKUP_M3_IPC=m
>> CONFIG_KEYSTONE_NAVIGATOR_QMSS=y
>> CONFIG_KEYSTONE_NAVIGATOR_DMA=y
>> CONFIG_RASPBERRYPI_POWER=y
>> @@ -1138,11 +1144,13 @@ CONFIG_TI_SCI_PM_DOMAINS=y
>> CONFIG_ARM_EXYNOS_BUS_DEVFREQ=m
>> CONFIG_ARM_TEGRA_DEVFREQ=m
>> CONFIG_DEVFREQ_EVENT_EXYNOS_NOCP=m
>> +CONFIG_EXTCON_PALMAS=m
>> CONFIG_EXTCON_MAX14577=m
>> CONFIG_EXTCON_MAX77693=m
>> CONFIG_EXTCON_MAX8997=m
>> CONFIG_EXTCON_USB_GPIO=y
>> CONFIG_TI_AEMIF=y
>> +CONFIG_TI_EMIF_SRAM=m
>> CONFIG_STM32_FMC2_EBI=y
>> CONFIG_EXYNOS5422_DMC=m
>> CONFIG_IIO=y
>> @@ -1287,6 +1295,7 @@ CONFIG_CRYPTO_AES_ARM=m
>> CONFIG_CRYPTO_AES_ARM_BS=m
>> CONFIG_CRYPTO_AES_ARM_CE=m
>> CONFIG_CRYPTO_CHACHA20_NEON=m
>> +CONFIG_CRYPTO_XCBC=m
> Why this is needed?
>
>> CONFIG_CRYPTO_DEV_SUN4I_SS=m
>> CONFIG_CRYPTO_DEV_FSL_CAAM=m
>> CONFIG_CRYPTO_DEV_EXYNOS_RNG=m
>> @@ -1300,6 +1309,10 @@ CONFIG_CRYPTO_DEV_QCOM_RNG=m
>> CONFIG_CRYPTO_DEV_ROCKCHIP=m
>> CONFIG_CRYPTO_DEV_STM32_HASH=m
>> CONFIG_CRYPTO_DEV_STM32_CRYP=m
>> +CONFIG_CRYPTO_DEV_OMAP=m
>> +CONFIG_CRYPTO_DEV_OMAP_SHAM=m
>> +CONFIG_CRYPTO_DEV_OMAP_AES=m
>> +CONFIG_CRYPTO_DEV_OMAP_DES=m
>> CONFIG_CMA_SIZE_MBYTES=64
>> CONFIG_PRINTK_TIME=y
>> CONFIG_DEBUG_KERNEL=y
>> @@ -1307,3 +1320,5 @@ CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
>> CONFIG_DEBUG_INFO_REDUCED=y
>> CONFIG_MAGIC_SYSRQ=y
>> CONFIG_DEBUG_FS=y
>> +CONFIG_CAN_C_CAN=m
>> +CONFIG_CAN_C_CAN_PLATFORM=m
> Does not look like placed according to Kconfig.
Thank you for the review.. Using savedefconfig eliminated some redundant configs.
I have addresses all comments in v2:
https://lore.kernel.org/all/20250616082038.3241346-1-b-padhi@ti.com/
Powered by blists - more mailing lists