public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Parvathi Pudi <parvathi@couthit.com>
To: nm@ti.com, vigneshr@ti.com, linux@armlinux.org.uk,
	ardb@kernel.org, ebiggers@kernel.org,
	krzysztof.kozlowski@oss.qualcomm.com, khilman@baylibre.com,
	arnd@arndb.de, geert+renesas@glider.be, parvathi@couthit.com,
	tiwai@suse.de, kory.maincent@bootlin.com, andreas@kemnade.info,
	dmitry.baryshkov@oss.qualcomm.com,
	prabhakar.mahadev-lad.rj@bp.renesas.com, twoerner@gmail.com
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, pratheesh@ti.com,
	j-rameshbabu@ti.com, praneeth@ti.com, srk@ti.com, rogerq@ti.com,
	danishanwar@ti.com, m-malladi@ti.com, krishna@couthit.com,
	mohan@couthit.com, pmohan@couthit.com, basharath@couthit.com
Subject: [PATCH v4] arm: multi_v7_defconfig: Enable BRIDGE and DP83848_PHY for TI AM57xx, AM437x and AM335x
Date: Tue, 28 Apr 2026 14:17:31 +0530	[thread overview]
Message-ID: <20260428085003.3023464-1-parvathi@couthit.com> (raw)

This patch enables BRIDGE and DP83848_PHY as kernel modules for AM57xx,
AM437x and AM335x SoCs. BRIDGE is to support STP/RSTP Switch mode using
PRU-ICSS which got recently merged and DP83848 PHY driver to support
TI TLK10X PHY.

Signed-off-by: Parvathi Pudi <parvathi@couthit.com>
---
Changes from v3 to v4:
*) No changes were made, only the version was updated.
*) Rebased the series on latest linux-next.

Changes from v2 to v3 :
*) No changes were made, only the version was updated.
*) Rebased the series on latest linux-next.

Changes from v1 to v2 :
*) Addressed  Krzysztof's comments on this patch.
*) Rebased the series on latest linux-next.

 arch/arm/configs/multi_v7_defconfig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index bcc9aabc1202..13362286b111 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -149,6 +149,7 @@ CONFIG_INET6_IPCOMP=m
 CONFIG_IPV6_MIP6=m
 CONFIG_IPV6_TUNNEL=m
 CONFIG_IPV6_MULTIPLE_TABLES=y
+CONFIG_BRIDGE=m
 CONFIG_NET_DSA=m
 CONFIG_QRTR=m
 CONFIG_QRTR_SMD=m
@@ -288,6 +289,7 @@ CONFIG_ICPLUS_PHY=y
 CONFIG_MARVELL_PHY=y
 CONFIG_AT803X_PHY=y
 CONFIG_ROCKCHIP_PHY=y
+CONFIG_DP83848_PHY=m
 CONFIG_DP83867_PHY=y
 CONFIG_CAN_AT91=m
 CONFIG_CAN_FLEXCAN=m
-- 
2.43.0



                 reply	other threads:[~2026-04-28  8:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260428085003.3023464-1-parvathi@couthit.com \
    --to=parvathi@couthit.com \
    --cc=andreas@kemnade.info \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=basharath@couthit.com \
    --cc=danishanwar@ti.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=ebiggers@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=j-rameshbabu@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kory.maincent@bootlin.com \
    --cc=krishna@couthit.com \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m-malladi@ti.com \
    --cc=mohan@couthit.com \
    --cc=nm@ti.com \
    --cc=pmohan@couthit.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=praneeth@ti.com \
    --cc=pratheesh@ti.com \
    --cc=rogerq@ti.com \
    --cc=srk@ti.com \
    --cc=tiwai@suse.de \
    --cc=twoerner@gmail.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox