From: Andrew Lunn <andrew@lunn.ch>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Juergen Beisert <jbe@pengutronix.de>,
Jerry Ray <jerry.ray@microchip.com>,
Mans Rullgard <mans@mansr.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] net: dsa: lan9303: consequently nested-lock physical MDIO
Date: Fri, 27 Oct 2023 13:55:16 +0200 [thread overview]
Message-ID: <f0e67b6e-e226-46fc-9e7c-60da35938d3f@lunn.ch> (raw)
In-Reply-To: <20231027065741.534971-1-alexander.sverdlin@siemens.com>
On Fri, Oct 27, 2023 at 08:57:38AM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> When LAN9303 is MDIO-connected two callchains exist into
> mdio->bus->write():
>
> 1. switch ports 1&2 ("physical" PHYs):
>
> virtual (switch-internal) MDIO bus (lan9303_switch_ops->phy_{read|write})->
> lan9303_mdio_phy_{read|write} -> mdiobus_{read|write}_nested
>
> 2. LAN9303 virtual PHY:
>
> virtual MDIO bus (lan9303_phy_{read|write}) ->
> lan9303_virt_phy_reg_{read|write} -> regmap -> lan9303_mdio_{read|write}
> Cc: stable@vger.kernel.org
> Fixes: dc7005831523 ("net: dsa: LAN9303: add MDIO managed mode support")
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2023-10-27 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 6:57 [PATCH] net: dsa: lan9303: consequently nested-lock physical MDIO A. Sverdlin
2023-10-27 11:55 ` Andrew Lunn [this message]
2023-11-02 10:20 ` 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=f0e67b6e-e226-46fc-9e7c-60da35938d3f@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexander.sverdlin@siemens.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jbe@pengutronix.de \
--cc=jerry.ray@microchip.com \
--cc=kuba@kernel.org \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox