[PATCH v2] arm64: defconfig: Enable various configs for TI platforms

[PATCH v2] arm64: defconfig: Enable various configs for TI platforms

[Udit Kumar]

Enable TI ECAP, DP83869 driver, TI OMAP2, K3 remote proc
SND_SOC_J721E_EVM, MCAN, UFS and RTI driver to be built
as module.
These are needed on different TI platforms.

Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
---
bloat-o-meter reports after this change
add/remove: 4/0 grow/shrink: 2/0 up/down: 1592/0 (1592)
[...]
Total: Before=27997071, After=27998663, chg +0.01%

Change log:
Changes in v2:
 Squashed all patches into one
link to v1:.
https://lore.kernel.org/all/20230725105346.1981285-1-u-kumar1@ti.com/

 arch/arm64/configs/defconfig | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 6cbf6eb59378..dedf1bd9c29f 100644
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@ -180,6 +180,8 @@ CONFIG_NET_ACT_GATE=m
 CONFIG_QRTR_SMD=m
 CONFIG_QRTR_TUN=m
 CONFIG_CAN=m
+CONFIG_CAN_M_CAN=m
+CONFIG_CAN_M_CAN_PLATFORM=m
 CONFIG_BT=m
 CONFIG_BT_HIDP=m
 # CONFIG_BT_LE is not set
@@ -375,6 +377,7 @@ CONFIG_AT803X_PHY=y
 CONFIG_REALTEK_PHY=y
 CONFIG_ROCKCHIP_PHY=y
 CONFIG_DP83867_PHY=y
+CONFIG_DP83869_PHY=m
 CONFIG_DP83TD510_PHY=y
 CONFIG_VITESSE_PHY=y
 CONFIG_CAN_FLEXCAN=m
@@ -687,6 +690,7 @@ CONFIG_UNIPHIER_WATCHDOG=y
 CONFIG_PM8916_WATCHDOG=m
 CONFIG_BCM2835_WDT=y
 CONFIG_BCM7038_WDT=m
+CONFIG_K3_RTI_WATCHDOG=m
 CONFIG_MFD_ALTERA_SYSMGR=y
 CONFIG_MFD_BD9571MWV=y
 CONFIG_MFD_AXP20X_I2C=y
@@ -927,6 +931,7 @@ CONFIG_SND_SOC_MSM8916_WCD_ANALOG=m
 CONFIG_SND_SOC_MSM8916_WCD_DIGITAL=m
 CONFIG_SND_SOC_PCM3168A_I2C=m
 CONFIG_SND_SOC_RT5640=m
+CONFIG_SND_SOC_J721E_EVM=m
 CONFIG_SND_SOC_RT5659=m
 CONFIG_SND_SOC_SIMPLE_AMPLIFIER=m
 CONFIG_SND_SOC_SIMPLE_MUX=m
@@ -1048,10 +1053,13 @@ CONFIG_MMC_SDHCI_XENON=y
 CONFIG_MMC_SDHCI_AM654=y
 CONFIG_MMC_OWL=y
 CONFIG_SCSI_UFSHCD=y
+CONFIG_SCSI_UFS_BSG=y
 CONFIG_SCSI_UFSHCD_PLATFORM=y
+CONFIG_SCSI_UFS_CDNS_PLATFORM=m
 CONFIG_SCSI_UFS_QCOM=m
 CONFIG_SCSI_UFS_HISI=y
 CONFIG_SCSI_UFS_RENESAS=m
+CONFIG_SCSI_UFS_TI_J721E=m
 CONFIG_SCSI_UFS_EXYNOS=y
 CONFIG_NEW_LEDS=y
 CONFIG_LEDS_CLASS=y
@@ -1230,6 +1238,7 @@ CONFIG_TEGRA186_TIMER=y
 CONFIG_RENESAS_OSTM=y
 CONFIG_ARM_MHU=y
 CONFIG_IMX_MBOX=y
+CONFIG_OMAP2PLUS_MBOX=m
 CONFIG_PLATFORM_MHU=y
 CONFIG_BCM2835_MBOX=y
 CONFIG_QCOM_APCS_IPC=y
@@ -1242,6 +1251,8 @@ CONFIG_MTK_IOMMU=y
 CONFIG_QCOM_IOMMU=y
 CONFIG_REMOTEPROC=y
 CONFIG_IMX_REMOTEPROC=y
+CONFIG_TI_K3_R5_REMOTEPROC=m
+CONFIG_TI_K3_DSP_REMOTEPROC=m
 CONFIG_MTK_SCP=m
 CONFIG_QCOM_Q6V5_ADSP=m
 CONFIG_QCOM_Q6V5_MSS=m
@@ -1356,6 +1367,7 @@ CONFIG_PWM_SAMSUNG=y
 CONFIG_PWM_SL28CPLD=m
 CONFIG_PWM_SUN4I=m
 CONFIG_PWM_TEGRA=m
+CONFIG_PWM_TIECAP=m
 CONFIG_PWM_TIEHRPWM=m
 CONFIG_PWM_VISCONTI=m
 CONFIG_SL28CPLD_INTC=y
@@ -1441,6 +1453,7 @@ CONFIG_FPGA_REGION=m
 CONFIG_OF_FPGA_REGION=m
 CONFIG_TEE=y
 CONFIG_OPTEE=y
+CONFIG_MUX_GPIO=m
 CONFIG_MUX_MMIO=y
 CONFIG_SLIMBUS=m
 CONFIG_SLIM_QCOM_CTRL=m
-- 
2.34.1

Re: [PATCH v2] arm64: defconfig: Enable various configs for TI platforms

[Nishanth Menon]

on $subject: I think mentioning K3 will help narrow things down a bit.

On 19:00-20230726, Udit Kumar wrote:
> Enable TI ECAP, DP83869 driver, TI OMAP2, K3 remote proc

I think you mean to state TI mailbox and not omap2 :)

> SND_SOC_J721E_EVM, MCAN, UFS and RTI driver to be built
> as module.
> These are needed on different TI platforms.

Please elaborate the list of boards this benefits TI platforms are a
big variant list. TI Platforms is too generic a term that scales
architectures.. that is not the point you are trying to make.
> 
> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> Signed-off-by: Judith Mendez <jm@ti.com>
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>

If the various contributers are ok, just my 2 cents:
Could you drop all other sign-offs other than yours? I understand the
contributions from various members on the TI SDK tree, but I'vent seen
them attempt to upstream and you took the effort in ensuring the new
squashed patch contains all the relevant components.

[..]
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Re: [PATCH v2] arm64: defconfig: Enable various configs for TI platforms

[Kumar, Udit]

Thanks Nishanth

On 7/26/2023 7:13 PM, Nishanth Menon wrote:
> on $subject: I think mentioning K3 will help narrow things down a bit.
>
> On 19:00-20230726, Udit Kumar wrote:
>> Enable TI ECAP, DP83869 driver, TI OMAP2, K3 remote proc
> I think you mean to state TI mailbox and not omap2 :)

Not really :)

This driver TI OMAP2, (CONFIG_OMAP2PLUS_MBOX) is used in

TI K3 platforms as well for communications with remote processors.

Rest comments will address in v3.


>
>> SND_SOC_J721E_EVM, MCAN, UFS and RTI driver to be built
>> as module.
>> These are needed on different TI platforms.
> Please elaborate the list of boards this benefits TI platforms are a
> big variant list. TI Platforms is too generic a term that scales
> architectures.. that is not the point you are trying to make.
>> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
>> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
>> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
>> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
>> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
>> Signed-off-by: Judith Mendez <jm@ti.com>
>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> If the various contributers are ok, just my 2 cents:
> Could you drop all other sign-offs other than yours? I understand the
> contributions from various members on the TI SDK tree, but I'vent seen
> them attempt to upstream and you took the effort in ensuring the new
> squashed patch contains all the relevant components.
>
> [..]

Re: [PATCH v2] arm64: defconfig: Enable various configs for TI platforms

[Nishanth Menon]

On 19:38-20230726, Kumar, Udit wrote:
> > On 19:00-20230726, Udit Kumar wrote:
> > > Enable TI ECAP, DP83869 driver, TI OMAP2, K3 remote proc
> > I think you mean to state TI mailbox and not omap2 :)
> 
> Not really :)
> 
> This driver TI OMAP2, (CONFIG_OMAP2PLUS_MBOX) is used in

OMAP2 is an SoC Architecture with a bunch of SoCs - OMAP2420,
OMAP2430... OMAP2+ refers to the combination of platforms from OMAP2,
OMAP3, OMAP4, OMAP5. Mailbox is a inter-processor communication
hardware block that has been used since OMAP2 generation of SoCs. The
same hardware block is used in K3 architecture as well.

So, call it OMAP2 Mailbox rather than TI OMAP2.
[...]

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D