From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: Correct cmode to PHY_INTERFACE_
Date: Tue, 11 Apr 2023 06:00:48 -0700 [thread overview]
Message-ID: <8e36fa45-129c-4bb1-3ebb-1b0871355ef2@gmail.com> (raw)
In-Reply-To: <a7a0dc51-c3dd-49e5-b66e-da9ddcc9e071@lunn.ch>
On 4/11/2023 5:48 AM, Andrew Lunn wrote:
>> On 4/11/2023 4:38 AM, Vladimir Oltean wrote:
>>> On Tue, Apr 11, 2023 at 04:35:41AM +0200, Andrew Lunn wrote:
>>>> The switch can either take the MAC or the PHY role in an MII or RMII
>>>> link. There are distinct PHY_INTERFACE_ macros for these two roles.
>>>> Correct the mapping so that the `REV` version is used for the PHY
>>>> role.
>
>>>> static const u8 mv88e6xxx_phy_interface_modes[] = {
>>>> - [MV88E6XXX_PORT_STS_CMODE_MII_PHY] = PHY_INTERFACE_MODE_MII,
>>>> + [MV88E6XXX_PORT_STS_CMODE_MII_PHY] = PHY_INTERFACE_MODE_REVMII,
>>
>> Is this hunk correct?
>
> Hi Florian
>
> I don't see why it is wrong, but you can be blind to bugs in your own
> code. What do you think is wrong?
I was not thinking it was wrong, just curious about the meaning of a
CMODE value suffixed with _PHY, though it seems clear(er) now that this
means the port is configured as a PHY and provides PHY signals to the
MAC it connects to.
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
PS: you can be blind without enough coffee as well :p
--
Florian
next prev parent reply other threads:[~2023-04-11 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 2:35 [PATCH net-next] net: dsa: mv88e6xxx: Correct cmode to PHY_INTERFACE_ Andrew Lunn
2023-04-11 10:48 ` Russell King (Oracle)
2023-04-11 11:38 ` Vladimir Oltean
2023-04-11 12:33 ` Florian Fainelli
2023-04-11 12:48 ` Andrew Lunn
2023-04-11 13:00 ` Florian Fainelli [this message]
2023-04-12 4:30 ` 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=8e36fa45-129c-4bb1-3ebb-1b0871355ef2@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).