From: Cai Xinchen <caixinchen1@huawei.com>
To: <ioana.ciornei@nxp.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<caixinchen1@huawei.com>
Subject: [PATCH v3 -next 0/2] dpaa2: fix config relation with FSL_DPAA2_SWITCH
Date: Thu, 12 Mar 2026 06:59:05 +0000 [thread overview]
Message-ID: <20260312065907.476663-1-caixinchen1@huawei.com> (raw)
When compile FSL_DPAA2_SWITCH, it needs to set CONFIG_FSL_DPAA2_ETH=y,
otherwise it cannot be compiled.
And as Ioana Ciornei sugggested, FSL_DPAA2_SWITCH included dpaa2-mac.o in
the driver, but it does not select PCS_LYNX, PHYLINK and FSL_XGMAC_MDIO.
And FSL_DPAA2_SWITCH depends on FSL_MC_BUS && FSL_MC_DPIO becuase it uses
fsl_mc_driver APIs.
v2->v3
Add depends on FSL_MC_BUS && FSL_MC_DPIO for FSL_DPAA2_SWITCH which also
satisfy FSL_XGMAC_MDIO's OF requirement.
v1->v2
There is no code dependency between the dpaa2-switch driver and the
dpaa2-eth, so use Makefile to control dpaa2-eth instead of using depending
on in Kconfig.
And add select PCS_LYNX, PHYLINK and FSL_XGMAC_MDIO for FSL_DPAA2_SWITCH.
Cai Xinchen (2):
dpaa2: add independent dependencies for FSL_DPAA2_SWITCH
dpaa2: compile dpaa2 even CONFIG_FSL_DPAA2_ETH=n
drivers/net/ethernet/freescale/Makefile | 3 +--
drivers/net/ethernet/freescale/dpaa2/Kconfig | 4 ++++
2 files changed, 5 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2026-03-12 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 6:59 Cai Xinchen [this message]
2026-03-12 6:59 ` [PATCH v3 -next 1/2] dpaa2: add independent dependencies for FSL_DPAA2_SWITCH Cai Xinchen
2026-03-12 6:59 ` [PATCH v3 -next 2/2] dpaa2: compile dpaa2 even CONFIG_FSL_DPAA2_ETH=n Cai Xinchen
2026-03-14 20:40 ` [PATCH v3 -next 0/2] dpaa2: fix config relation with FSL_DPAA2_SWITCH patchwork-bot+netdevbpf
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=20260312065907.476663-1-caixinchen1@huawei.com \
--to=caixinchen1@huawei.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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