From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Pierluigi Passaro <pierluigi.p@variscite.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Pierluigi Passaro <pierluigi.passaro@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Eran Matityahu <eran.m@variscite.com>,
Nate Drude <Nate.D@variscite.com>,
Francesco Ferraro <francesco.f@variscite.com>
Subject: Re: [PATCH] net: mdio: force deassert MDIO reset signal
Date: Mon, 16 Jan 2023 10:21:53 +0000 [thread overview]
Message-ID: <Y8UlQaymWcYdqKJ/@shell.armlinux.org.uk> (raw)
In-Reply-To: <AM6PR08MB437630CD49B50D66543EC3BDFFC19@AM6PR08MB4376.eurprd08.prod.outlook.com>
On Mon, Jan 16, 2023 at 09:44:01AM +0000, Pierluigi Passaro wrote:
> I can't really understand why the MDIO bus must check the PHY presence.
> Other busses try the communication only while probing the slaves,
> never before.
That is not true.
Any bus that relies on hardware identification to bind drivers reads
the identifying information prior to probing. For example, PCI, USB,
AMBA to name a few. AMBA didn't used to have this problem, but does
now - but at least under AMBA there's a bit more standardisation to
what needs to be done. With ethernet PHYs, what's needed is highly
platform specific.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2023-01-16 10:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 16:10 [PATCH] net: mdio: force deassert MDIO reset signal Pierluigi Passaro
2023-01-15 17:08 ` Andrew Lunn
2023-01-15 18:38 ` Pierluigi Passaro
2023-01-15 19:02 ` Andrew Lunn
2023-01-15 20:34 ` Pierluigi Passaro
2023-01-15 21:58 ` Lars-Peter Clausen
2023-01-15 22:33 ` Pierluigi Passaro
2023-01-15 22:56 ` Lars-Peter Clausen
2023-01-15 23:16 ` Pierluigi Passaro
2023-01-16 0:11 ` Andrew Lunn
2023-01-16 9:44 ` Pierluigi Passaro
2023-01-16 10:21 ` Russell King (Oracle) [this message]
2023-01-17 14:01 ` Andrew Lunn
2023-01-17 15:20 ` Pierluigi Passaro
2023-01-15 23:55 ` Andrew Lunn
2023-01-16 2:21 ` Lars-Peter Clausen
2023-01-16 9:51 ` Pierluigi Passaro
2023-01-17 13:40 ` Andrew Lunn
2023-01-17 13:48 ` Lars-Peter Clausen
2023-01-17 14:13 ` Andrew Lunn
2023-01-16 8:39 ` Pierluigi Passaro
2023-01-17 13:43 ` Andrew Lunn
2023-01-16 8:43 ` kernel test robot
2023-01-16 10:32 ` Pierluigi Passaro
2023-01-16 10:34 ` Russell King (Oracle)
2023-01-16 14:35 ` Pierluigi Passaro
2023-01-17 20:30 ` Dan Carpenter
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=Y8UlQaymWcYdqKJ/@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Nate.D@variscite.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eran.m@variscite.com \
--cc=francesco.f@variscite.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pierluigi.p@variscite.com \
--cc=pierluigi.passaro@gmail.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