From: Philippe Schenker <philippe.schenker@toradex.com>
To: "matthias.schiffer@ew.tq-group.com" <matthias.schiffer@ew.tq-group.com>
Cc: "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH] net: phy: micrel: make *-skew-ps check more lenient
Date: Wed, 13 Oct 2021 10:18:59 +0000 [thread overview]
Message-ID: <bf2c71d5f73839bdc585c19490e40d08f26d644a.camel@toradex.com> (raw)
In-Reply-To: <987224f4ca93f928c8ddb69710d3aa72b336b6dc.camel@ew.tq-group.com>
On Wed, 2021-10-13 at 10:46 +0200, Matthias Schiffer wrote:
> On Wed, 2021-10-13 at 08:25 +0000, Philippe Schenker wrote:
> > On Tue, 2021-10-12 at 12:34 +0200, Matthias Schiffer wrote:
> > > It seems reasonable to fine-tune only some of the skew values when
> > > using
> > > one of the rgmii-*id PHY modes, and even when all skew values are
> > > specified, using the correct ID PHY mode makes sense for
> > > documentation
> > > purposes. Such a configuration also appears in the binding docs in
> > > Documentation/devicetree/bindings/net/micrel-ksz90x1.txt, so the
> > > driver
> > > should not warn about it.
> >
> > I don't think your commit message is right. The rgmii-*id PHY modes
> > are
> > no longer just for documentation purposes on KSZ9031 PHY. They are
> > used
> > to set the skew-registers according to .
>
> Yes, this was implemented in [1]. The commit message explicitly states
> that fine-tuning is still possible using *-skew-ps.
>
> >
> > The warning is there, that in case you override the skew registers
> > of
> > one of the modes rgmii-id, rgmii-txid, rgmii-rxid with *-skew-ps
> > settings in DT.
>
> The "rgmii" mode should not be handled differently from "rgmii-*id" in
> my opinion. Otherwise for a device that is basically "rgmii-id", but
> requires slight fine-tuning, you have to set the mode to the incorrect
> value "rgmii" in the DTS to avoid this warning.
Now I have understood your argument. But then I suggest to delete the
warning entirely as it completely changes its meaning with that patch.
Philippe
>
>
> >
> > Therefore I also think the warning is valuable and should be kept.
> > We
> > may want to reword it though.
> >
> > Philippe
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/phy/micrel.c?id=bcf3440c6dd78bfe5836ec0990fe36d7b4bb7d20
>
>
> >
> > >
> > > Signed-off-by: Matthias Schiffer
> > > <matthias.schiffer@ew.tq-group.com>
> > > ---
> > > drivers/net/phy/micrel.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> > > index c330a5a9f665..03e58ebf68af 100644
> > > --- a/drivers/net/phy/micrel.c
> > > +++ b/drivers/net/phy/micrel.c
> > > @@ -863,9 +863,9 @@ static int ksz9031_config_init(struct
> > > phy_device
> > > *phydev)
> > > MII_KSZ9031RN_TX_DATA_PAD_SKEW, 4,
> > > tx_data_skews, 4, &update);
> > >
> > > - if (update && phydev->interface !=
> > > PHY_INTERFACE_MODE_RGMII)
> > > + if (update && !phy_interface_is_rgmii(phydev))
> > > phydev_warn(phydev,
> > > - "*-skew-ps values should be
> > > used
> > > only with phy-mode = \"rgmii\"\n");
> > > + "*-skew-ps values should be
> > > used
> > > only with RGMII PHY modes\n");
> > >
> > > /* Silicon Errata Sheet (DS80000691D or
> > > DS80000692D):
> > > * When the device links in the 1000BASE-T slave
> > > mode
> > > only,
> >
> >
>
next prev parent reply other threads:[~2021-10-13 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 10:34 Matthias Schiffer
2021-10-13 8:25 ` Philippe Schenker
2021-10-13 8:46 ` Matthias Schiffer
2021-10-13 10:18 ` Philippe Schenker [this message]
2021-10-13 11:01 ` Matthias Schiffer
2021-10-15 2: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=bf2c71d5f73839bdc585c19490e40d08f26d644a.camel@toradex.com \
--to=philippe.schenker@toradex.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@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
all inboxes | Powered by JetHome®