[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4pj1Xb6mrIWxLEm@hoboy.vegasvil.org>
Date: Fri, 2 Dec 2022 12:45:09 -0800
From: Richard Cochran <richardcochran@...il.com>
To: Rahul Rameshbabu <rrameshbabu@...dia.com>
Cc: Saeed Mahameed <saeedm@...dia.com>,
Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Jacob Keller <jacob.e.keller@...el.com>,
Aya Levin <ayal@...dia.com>, Gal Pressman <gal@...dia.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] ptp: Introduce .getfine callback to
ptp_clock_info
On Fri, Dec 02, 2022 at 12:15:27PM -0800, Rahul Rameshbabu wrote:
> The current state of the ptp driver provides the ability to query the frequency
> of the ptp clock device by caching the frequency values used in previous
> adjustments done through the ptp driver. This works great when the ptp driver is
> the only means for changing the clock frequency. However, some devices support
> ways to adjust the frequency outside the ptp driver stack.
The kernel provides no other way to adjust the frequency.
So NAK on this series.
Thanks,
Richard
Powered by blists - more mailing lists