From: Andrew Lunn <andrew@lunn.ch>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, netdev <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Zoltan HERPAI <wigyori@uid0.hu>,
Raylynn Knight <rayknight@me.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/3 net-next v3] net: ethernet: ixp4xx: Add DT bindings
Date: Sun, 25 Apr 2021 02:37:10 +0200 [thread overview]
Message-ID: <YIS5trXADzDb/yJz@lunn.ch> (raw)
In-Reply-To: <CACRpkdZp8OYyQtuhRqGmjc2gVpmjyBMFivHbk3xBiQk5NKbbww@mail.gmail.com>
On Sun, Apr 25, 2021 at 02:24:26AM +0200, Linus Walleij wrote:
> On Fri, Apr 23, 2021 at 4:49 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > (...) it should be impossible for multiple devices to
> > instantiate an MDIO bus. But with device tree, is that still true?
> > Should there be validation that only one device has an MDIO bus in its
> > device tree?
>
> This would be more of a question to Rob.
Hi Linus
Sorry. I was thinking C code. The driver already has the global
variable mdio_bus. It is initially a NULL pointer. It gets sent when
the first MDIO bus driver probes. If it is not NULL when an MDIO bus
driver probes, throw an error.
Andrew
next prev parent reply other threads:[~2021-04-25 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 8:22 [PATCH 1/3 net-next v3] net: ethernet: ixp4xx: Add DT bindings Linus Walleij
2021-04-23 14:49 ` Andrew Lunn
2021-04-25 0:24 ` Linus Walleij
2021-04-25 0:37 ` Andrew Lunn [this message]
2021-04-23 17:58 ` Rob Herring
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=YIS5trXADzDb/yJz@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=rayknight@me.com \
--cc=robh+dt@kernel.org \
--cc=wigyori@uid0.hu \
/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;
as well as URLs for NNTP newsgroup(s).