From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
<linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [RFC PATCH] net: phy/mdio: enable mmd indirect access through phy_mii_ioctl()
Date: Wed, 3 Nov 2021 00:22:16 +0200 [thread overview]
Message-ID: <8d24c421-064c-9fee-577a-cbbf089cdf33@ti.com> (raw)
In-Reply-To: <YYGxvomL/0tiPzvV@lunn.ch>
On 02/11/2021 23:46, Andrew Lunn wrote:
>> @@ -300,8 +301,18 @@ int phy_mii_ioctl(struct phy_device *phydev, struct ifreq *ifr, int cmd)
>> prtad = mii_data->phy_id;
>> devad = mii_data->reg_num;
>> }
>> - mii_data->val_out = mdiobus_read(phydev->mdio.bus, prtad,
>> - devad);
>> +
>> + if (prtad != phydev->mdio.addr)
>> + phydev_rq = mdiobus_get_phy(phydev->mdio.bus, prtad);
>> +
>> + if (!phydev_rq) {
>> + mii_data->val_out = mdiobus_read(phydev->mdio.bus, prtad, devad);
>> + } else if (mdio_phy_id_is_c45(mii_data->phy_id) && !phydev->is_c45) {
>> + mii_data->val_out = phy_read_mmd(phydev_rq, mdio_phy_id_devad(mii_data->phy_id), mii_data->reg_num);
>> + } else {
>> + mii_data->val_out = phy_read(phydev_rq, mii_data->reg_num);
>> + }
>> +
>
> One thing i don't like about this is you have little idea what it has
> actually done.
>
> If you pass a C45 address, i expect a C45 access. If i pass a C22 i
> expect a C22 access.
I might be doing smth wrong and that's why it's RFC.
I wanted to understand if i hook into the kernel side first correctly, so
if above doesn't violate PHYs/mdiodev access any more there seems reason
try to continue.
>
> What i find interesting is that you and the other resent requester are
> using the same user space tool. If you implement C45 over C22 in that
> tool, you get your solution, and it will work for older kernels as
> well. Also, given the diverse implementations of this IOTCL, it
> probably works for more drivers than just those using phy_mii_ioctl().
Do you mean change uapi, like
add mdio_phy_id_is_c45_over_c22() and
flag #define MDIO_PHY_ID_C45_OVER_C22 0x4000?
Thank you for your comments and patience.
--
Best regards,
grygorii
next prev parent reply other threads:[~2021-11-02 22:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 18:28 Grygorii Strashko
2021-11-01 19:33 ` Andrew Lunn
2021-11-01 19:54 ` Russell King (Oracle)
2021-11-02 0:49 ` Andrew Lunn
2021-11-02 12:39 ` Russell King (Oracle)
2021-11-02 17:13 ` Andrew Lunn
2021-11-02 19:46 ` Sean Anderson
2021-11-02 23:38 ` Russell King (Oracle)
2021-11-04 15:05 ` Sean Anderson
2021-11-02 17:19 ` Grygorii Strashko
2021-11-02 17:41 ` Russell King (Oracle)
2021-11-02 18:37 ` Grygorii Strashko
2021-11-02 19:12 ` Grygorii Strashko
2021-11-02 21:46 ` Andrew Lunn
2021-11-02 22:22 ` Grygorii Strashko [this message]
2021-11-03 0:27 ` Andrew Lunn
2021-11-03 18:42 ` Grygorii Strashko
2021-11-03 19:36 ` Andrew Lunn
2021-11-04 11:17 ` Tobias Waldekranz
2021-11-04 12:35 ` Russell King (Oracle)
2021-11-04 12:40 ` Russell King (Oracle)
2021-11-04 13:13 ` Tobias Waldekranz
2021-11-04 13:06 ` Tobias Waldekranz
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=8d24c421-064c-9fee-577a-cbbf089cdf33@ti.com \
--to=grygorii.strashko@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®