From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Andrew Lunn <andrew@lunn.ch>, Simon Horman <horms@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Jacob Keller <jacob.e.keller@intel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/4] net: phy: micrel: improve HW timestamping config logic
Date: Mon, 1 Dec 2025 10:34:13 +0000 [thread overview]
Message-ID: <287e67fa-44fc-4f70-8399-49dea01e8262@linux.dev> (raw)
In-Reply-To: <20251201103321.47cb4ceb@kmaincent-XPS-13-7390>
On 01/12/2025 09:33, Kory Maincent wrote:
> On Sat, 29 Nov 2025 19:53:31 +0000
> Vadim Fedorenko <vadim.fedorenko@linux.dev> wrote:
>
>> The driver was adjusting stored values independently of what was
>> actually supported and configured. Improve logic to store values
>> once all checks are passing
>>
>> Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
>> ---
>> drivers/net/phy/micrel.c | 21 +++++++++++++++------
>> 1 file changed, 15 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
>> index 05de68b9f719..1ada05dd305c 100644
>> --- a/drivers/net/phy/micrel.c
>> +++ b/drivers/net/phy/micrel.c
>> @@ -3157,9 +3157,6 @@ static int lan8814_hwtstamp_set(struct mii_timestamper
>> *mii_ts, int txcfg = 0, rxcfg = 0;
>> int pkt_ts_enable;
>>
>> - ptp_priv->hwts_tx_type = config->tx_type;
>> - ptp_priv->rx_filter = config->rx_filter;
>> -
>> switch (config->rx_filter) {
>> case HWTSTAMP_FILTER_NONE:
>> ptp_priv->layer = 0;
>> @@ -3187,6 +3184,18 @@ static int lan8814_hwtstamp_set(struct mii_timestamper
>> *mii_ts, return -ERANGE;
>> }
>>
>> + switch (config->rx_filter) {
>
> You want to check tx_type here, not rx_filter.
>
>> + case HWTSTAMP_TX_OFF:
>> + case HWTSTAMP_TX_ON:
>> + case HWTSTAMP_TX_ONESTEP_SYNC:
>> + break;
>> + default:
>> + return -ERANGE;
>> + }
>> +
>> + ptp_priv->hwts_tx_type = config->tx_type;
>> + ptp_priv->rx_filter = config->rx_filter;
>> +
>> if (ptp_priv->layer & PTP_CLASS_L2) {
>> rxcfg = PTP_RX_PARSE_CONFIG_LAYER2_EN_;
>> txcfg = PTP_TX_PARSE_CONFIG_LAYER2_EN_;
>> @@ -5051,9 +5060,6 @@ static int lan8841_hwtstamp_set(struct mii_timestamper
>> *mii_ts, int txcfg = 0, rxcfg = 0;
>> int pkt_ts_enable;
>>
>> - ptp_priv->hwts_tx_type = config->tx_type;
>> - ptp_priv->rx_filter = config->rx_filter;
>> -
>> switch (config->rx_filter) {
>> case HWTSTAMP_FILTER_NONE:
>> ptp_priv->layer = 0;
>> @@ -5081,6 +5087,9 @@ static int lan8841_hwtstamp_set(struct mii_timestamper
>> *mii_ts, return -ERANGE;
>> }
>>
>> + ptp_priv->hwts_tx_type = config->tx_type;
>> + ptp_priv->rx_filter = config->rx_filter;
>
> I there a reason to not add the check in the hwtstamp ops for lan8841 as well?
> because the issue is also present.
Hm... I thought I added it... Well, looks like I shouldn't work during
vacation :) Going to add it in v3, thanks!
>
> Regards,
next prev parent reply other threads:[~2025-12-01 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 19:53 [PATCH net-next v2 0/4] support for hwtstamp_get in phy - part 2 Vadim Fedorenko
2025-11-29 19:53 ` [PATCH net-next v2 1/4] net: phy: micrel: improve HW timestamping config logic Vadim Fedorenko
2025-11-29 20:49 ` Andrew Lunn
2025-12-01 9:33 ` Kory Maincent
2025-12-01 10:34 ` Vadim Fedorenko [this message]
2025-11-29 19:53 ` [PATCH net-next v2 2/4] net: phy: micrel: add HW timestamp configuration reporting Vadim Fedorenko
2025-11-29 20:49 ` Andrew Lunn
2025-12-01 9:28 ` Kory Maincent
2025-11-29 19:53 ` [PATCH net-next v2 3/4] net: phy: microchip_rds_ptp: improve HW ts config logic Vadim Fedorenko
2025-11-29 20:51 ` Andrew Lunn
2025-12-01 9:34 ` Kory Maincent
2025-12-01 10:28 ` Vadim Fedorenko
2025-11-29 19:53 ` [PATCH net-next v2 4/4] net: phy: microchip_rds_ptp: add HW timestamp configuration reporting Vadim Fedorenko
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=287e67fa-44fc-4f70-8399-49dea01e8262@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--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).