From: Andrew Lunn <andrew@lunn.ch>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, UNGLinuxDriver@microchip.com,
richardcochran@gmail.com
Subject: Re: [RFC PATCH net-next 0/2] net: phy: Extend sysfs to adjust PHY latency.
Date: Tue, 19 Apr 2022 14:17:40 +0200 [thread overview]
Message-ID: <Yl6oZLIaBnPVkeqN@lunn.ch> (raw)
In-Reply-To: <20220419083704.48573-1-horatiu.vultur@microchip.com>
On Tue, Apr 19, 2022 at 10:37:02AM +0200, Horatiu Vultur wrote:
> The previous try of setting the PHY latency was here[1]. But this approach
> could not work for multiple reasons:
> - the interface was not generic enough so it would be hard to be extended
> in the future
> - if there were multiple time stamper in the system then it was not clear
> to which one should adjust these values.
>
> So the next try is to extend sysfs and configure exactly the desired PHY.
What about timestampers which are not PHYs? Ideally you want one
interface which will work for any sort of stamper, be it MAC, PHY, or
a bump in the wire between the MAC and the PHY.
Andrew
next prev parent reply other threads:[~2022-04-19 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 8:37 [RFC PATCH net-next 0/2] net: phy: Extend sysfs to adjust PHY latency Horatiu Vultur
2022-04-19 8:37 ` [RFC PATCH net-next 1/2] net: phy: Add phy latency adjustment support in phy framework Horatiu Vultur
2022-04-19 12:32 ` Andrew Lunn
2022-04-19 8:37 ` [RFC PATCH net-next 2/2] net: phy: micrel: Implement set/get_adj_latency for lan8814 Horatiu Vultur
2022-04-19 12:42 ` Andrew Lunn
2022-04-19 12:17 ` Andrew Lunn [this message]
2022-04-20 7:57 ` [RFC PATCH net-next 0/2] net: phy: Extend sysfs to adjust PHY latency Horatiu Vultur
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=Yl6oZLIaBnPVkeqN@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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