From: Vladimir Oltean <olteanv@gmail.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
netdev <netdev@vger.kernel.org>,
erkin.bozoglu@xeront.com, Thibaut <hacks@slashdirt.org>
Subject: Re: mt7530: dsa_switch_parse_of() fails, causes probe code to run twice
Date: Sat, 15 Apr 2023 17:20:14 +0300 [thread overview]
Message-ID: <20230415142014.katsq5axop6gov3i@skbuf> (raw)
In-Reply-To: <ZDquYkt_5Ku2ysSA@makrotopia.org>
On Sat, Apr 15, 2023 at 03:02:10PM +0100, Daniel Golle wrote:
> As the PHYs are accessed over the MDIO bus which is exposed by the mt7530.c
> DSA driver the only middle ground would possibly be to introduce a MFD
> driver taking care of creating the bus access regmap (MDIO vs. MDIO) and
> expose the mt7530-controlled MDIO bus.
Which is something I had already mentioned as a possible way forward in
the other thread. One would need to take care of ensuring a reasonable
migration path in terms of device tree compatibility though.
>
> Obviously that'd be a bit more work than just moving some things from the
> switch setup function to the probe function...
On the other hand, it would actually work reliably, and would not depend
on whomever wanted to reorder things just a little bit differently for
his system to probe faster.
next prev parent reply other threads:[~2023-04-15 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 22:41 mt7530: dsa_switch_parse_of() fails, causes probe code to run twice Arınç ÜNAL
2023-04-14 22:48 ` Daniel Golle
2023-04-14 23:23 ` Arınç ÜNAL
2023-04-14 23:53 ` Daniel Golle
2023-04-15 0:28 ` Arınç ÜNAL
2023-04-15 0:52 ` Daniel Golle
2023-04-15 7:53 ` Arınç ÜNAL
2023-04-15 9:43 ` Arınç ÜNAL
2023-04-15 12:43 ` Daniel Golle
2023-04-15 13:19 ` Arınç ÜNAL
2023-04-15 13:38 ` Vladimir Oltean
2023-04-15 13:40 ` Arınç ÜNAL
2023-04-15 13:46 ` Vladimir Oltean
2023-04-15 14:02 ` Daniel Golle
2023-04-15 14:20 ` Vladimir Oltean [this message]
2023-04-15 14:28 ` Vladimir Oltean
2023-04-15 14:57 ` Arınç ÜNAL
2023-04-16 9:38 ` Arınç ÜNAL
2023-04-16 11:57 ` Daniel Golle
2023-04-15 10:12 ` Vladimir Oltean
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=20230415142014.katsq5axop6gov3i@skbuf \
--to=olteanv@gmail.com \
--cc=arinc.unal@arinc9.com \
--cc=daniel@makrotopia.org \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=hacks@slashdirt.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.