[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2e316ec4-8f5b-4dbd-96d2-aabc29bfae17@lunn.ch>
Date: Wed, 5 Feb 2025 18:42:31 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
kernel@...gutronix.de, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net: phy: Add support for
driver-specific next update time
> + if (phy_polling_mode(phydev) && phy_is_started(phydev)) {
> + unsigned int next_update_time =
> + phy_get_next_update_time(phydev);
> +
> + phy_queue_state_machine(phydev,
> + msecs_to_jiffies(next_update_time));
Ah, i missed the msecs_to_jiffies() call. But the driver change now
looks wrong. I think to keep things simple, the API should use
jiffies, since that is what phy_queue_state_machine() and
mod_delayed_work() expect.
Did you test with Timer frequency = 100, that should make errors more
obvious.
Andrew
Powered by blists - more mailing lists