From: Martin Schiller <ms@dev.tdt.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: hauke@hauke-m.de, martin.blumenstingl@googlemail.com,
f.fainelli@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6] net: phy: intel-xway: Add RGMII internal delay configuration
Date: Tue, 20 Jul 2021 13:50:48 +0200 [thread overview]
Message-ID: <7f427d3c93f2cbacbb7273a5af9e4b41@dev.tdt.de> (raw)
In-Reply-To: <YPXm9avkMoD/oat8@lunn.ch>
On 2021-07-19 22:56, Andrew Lunn wrote:
>> + if (phydev->interface == PHY_INTERFACE_MODE_RGMII_ID ||
>> + phydev->interface == PHY_INTERFACE_MODE_RGMII_RXID) {
>> + int_delay = phy_get_internal_delay(phydev, dev,
>> + xway_internal_delay,
>> + delay_size, true);
>> +
>> + if (int_delay < 0) {
>> + phydev_warn(phydev, "rx-internal-delay-ps is missing, use default
>> of 2.0 ns\n");
>> + int_delay = 4; /* 2000 ps */
>
> The binding say:
>
> rx-internal-delay-ps:
> description: |
> RGMII Receive PHY Clock Delay defined in pico seconds. This is
> used for
> PHY's that have configurable RX internal delays. If this
> property is
> present then the PHY applies the RX delay.
>
> So the property is optional. It being missing should not generate a
> warning. Please just use the default of 2ns. This makes the usage the
> same as the other drivers using phy_get_internal_delay().
>
> Andrew
OK, I'll remove the warnings. Thanks.
next prev parent reply other threads:[~2021-07-20 11:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 8:27 [PATCH net-next v6] net: phy: intel-xway: Add RGMII internal delay configuration Martin Schiller
2021-07-19 20:56 ` Andrew Lunn
2021-07-20 11:50 ` Martin Schiller [this message]
2022-01-10 23:12 ` Tim Harvey
2022-01-11 7:44 ` Martin Schiller
2022-01-11 13:34 ` Andrew Lunn
2022-01-11 19:12 ` Tim Harvey
2022-01-12 11:07 ` Martin Schiller
2022-01-12 13:14 ` Andrew Lunn
2022-01-12 18:24 ` Tim Harvey
2022-01-12 13:46 ` Russell King (Oracle)
2022-01-12 18:25 ` Tim Harvey
2022-01-13 6:32 ` Martin Schiller
2022-02-01 20:28 ` Tim Harvey
2022-02-01 20:49 ` Andrew Lunn
2023-02-22 16:04 ` Michael Walle
2023-02-24 6:25 ` Martin Schiller
2023-02-24 8:04 ` Michael Walle
2023-02-24 8:48 ` Martin Schiller
2023-03-02 15:03 ` Michael Walle
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=7f427d3c93f2cbacbb7273a5af9e4b41@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.blumenstingl@googlemail.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;
as well as URLs for NNTP newsgroup(s).