From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: mw@semihalf.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: mvpp2: add support for mii
Date: Thu, 7 Dec 2023 12:27:16 +0100 [thread overview]
Message-ID: <20231207122716.7ff58c91@device.home> (raw)
In-Reply-To: <ZXGJXIK3cl/9lfKi@eichest-laptop>
Hello Stefan,
On Thu, 7 Dec 2023 10:01:08 +0100
Stefan Eichenberger <eichest@gmail.com> wrote:
> Hi Maxime,
>
> On Wed, Dec 06, 2023 at 06:27:05PM +0100, Maxime Chevallier wrote:
> > > @@ -6973,6 +6988,9 @@ static int mvpp2_port_probe(struct platform_device *pdev,
> > > port->phylink_config.supported_interfaces);
> > > __set_bit(PHY_INTERFACE_MODE_SGMII,
> > > port->phylink_config.supported_interfaces);
> > > + } else if (phy_mode == PHY_INTERFACE_MODE_MII) {
> > > + __set_bit(PHY_INTERFACE_MODE_100BASEX,
> > > + port->phylink_config.supported_interfaces);
> >
> > Can you explain that part ? I don't understand why 100BaseX is being
> > reported as a supported mode here. This whole section of the function
> > is about detecting what can be reported based on the presence or not of
> > a comphy driver / hardcoded comphy config. I don't think the comphy
> > here has anything to do with MII / 100BaseX
> >
> > If 100BaseX can be carried on MII (which I don't know), shouldn't it be
> > reported no matter what ?
>
> I missunderstood that part, I thought it is a translation from interface
> type to speed but it is obviously not. I already verfied that everything
> works without this part and will remove it in version 2 of the patch.
> Thanks a lot for the review!
No problem, thanks for the patch :)
Maxime
prev parent reply other threads:[~2023-12-07 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 16:01 [PATCH net-next] net: mvpp2: add support for mii Stefan Eichenberger
2023-12-06 17:27 ` Maxime Chevallier
2023-12-07 9:01 ` Stefan Eichenberger
2023-12-07 11:27 ` Maxime Chevallier [this message]
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=20231207122716.7ff58c91@device.home \
--to=maxime.chevallier@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eichest@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.