From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] net: dsa: various fixes
Date: Wed, 24 Feb 2021 17:40:38 +0100 [thread overview]
Message-ID: <20210224164042.21747-1-michael@walle.cc> (raw)
Before a DSA port is probed, the master port needs to be probed first. For
now this worked, because the probing order was correct. But it already
falls short if you use the enetc6 port on the LS1028A SoC:
Device tree snippet:
&enetc6 {
status = "okay";
};
&mscc_felix_port5 {
ethernet = <&enetc6>;
status = "okay";
};
NB. keep enetc2 enabled, otherwise you will trigger an access violation.
Michael Walle (4):
net: dsa: return early if there is no master
net: dsa: probe master device
net: dsa: remove NULL check for priv and platform data
net: dsa: remove master santiy check
net/dsa-uclass.c | 63 ++++++++++++++++++------------------------------
1 file changed, 24 insertions(+), 39 deletions(-)
--
2.20.1
next reply other threads:[~2021-02-24 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:40 Michael Walle [this message]
2021-02-24 16:40 ` [PATCH 1/4] net: dsa: return early if there is no master Michael Walle
2021-02-25 19:12 ` Ramon Fried
2021-02-24 16:40 ` [PATCH 2/4] net: dsa: probe master device Michael Walle
2021-02-25 19:13 ` Ramon Fried
2021-02-24 16:40 ` [PATCH 3/4] net: dsa: remove NULL check for priv and platform data Michael Walle
2021-02-24 22:23 ` Vladimir Oltean
2021-02-25 19:14 ` Ramon Fried
2021-02-24 16:40 ` [PATCH 4/4] net: dsa: remove master santiy check Michael Walle
2021-02-24 17:11 ` Vladimir Oltean
2021-02-24 17:29 ` Michael Walle
2021-02-24 17:45 ` Vladimir Oltean
2021-02-24 18:08 ` Michael Walle
2021-02-24 18:19 ` Vladimir Oltean
2021-02-24 19:03 ` Michael Walle
2021-02-24 21:40 ` Vladimir Oltean
2021-02-24 22:25 ` Vladimir Oltean
2021-02-24 22:52 ` Michael Walle
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=20210224164042.21747-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=u-boot@lists.denx.de \
/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