[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a7e434a5-b5f6-4736-98e4-e671f88d1873@intel.com>
Date: Fri, 21 Feb 2025 14:22:49 -0800
From: Jacob Keller <jacob.e.keller@...el.com>
To: Jakub Kicinski <kuba@...nel.org>, Meghana Malladi <m-malladi@...com>
CC: <lokeshvutla@...com>, <vigneshr@...com>, <javier.carrasco.cruz@...il.com>,
<diogo.ivo@...mens.com>, <horms@...nel.org>, <pabeni@...hat.com>,
<edumazet@...gle.com>, <davem@...emloft.net>, <andrew+netdev@...n.ch>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <srk@...com>, Roger Quadros
<rogerq@...nel.org>, <danishanwar@...com>
Subject: Re: [PATCH net v2 0/2] Fixes for perout configuration in IEP driver
On 2/20/2025 5:24 PM, Jakub Kicinski wrote:
> On Wed, 19 Feb 2025 15:37:16 -0800 Jacob Keller wrote:
>> On 2/18/2025 10:26 PM, Meghana Malladi wrote:
>>> IEP driver supports both pps and perout signal generation using testptp
>>> application. Currently the driver is missing to incorporate the perout
>>> signal configuration. This series introduces fixes in the driver to
>>> configure perout signal based on the arguments passed by the perout
>>> request.
>>>
>>
>> This could be interpreted as a feature implementation rather than a fix.
>>
>> Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
>
> Agreed, ideally we should get a patch for net which rejects
> all currently (as in - in Linus's tree) unsupported settings.
> That would be a fix.
>
> Then once that's merged add support for the new settings in net-next.
>
> Hope that makes sense?
+1 on this direction, its important that the driver does not accept
configuration which is incorrect.
Reminds me of my backlog to refactor this whole mess into a
supported_flags field in the PTP ops structure. Maybe it is again time
to revive that.
Thanks,
Jake
Powered by blists - more mailing lists