From: Andrew Lunn <andrew@lunn.ch>
To: "Allan W. Nielsen" <allan.nielsen@microchip.com>
Cc: Horatiu Vultur <horatiu.vultur@microchip.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, hkallweit1@gmail.com,
linux@armlinux.org.uk, Divya.Koppera@microchip.com,
davem@davemloft.net, kuba@kernel.org, richardcochran@gmail.com,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net 2/3] net: phy: micrel: Remove latency from driver
Date: Fri, 1 Apr 2022 16:05:38 +0200 [thread overview]
Message-ID: <YkcGsiEmnk9sKjEj@lunn.ch> (raw)
In-Reply-To: <20220401135918.4tvwe6cfyku6l5wf@lx-anielsen>
> I would like to keep the default values. With default values, you can
> get PTP working (accuracy is not great - but it is much better than
> if set to zero).
>
> There is no risk of bootloaders to pre-load other values, as the kernel
> will reset the PHY, and after reset we will be back to these numbers.
O.K, that is what i wanted to know. It should be reasonable safe to
assume these values, and userspace daemons can apply whatever
correction they want, assuming this is what the hardware is doing.
Andrew
next prev parent reply other threads:[~2022-04-01 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:48 [PATCH net 0/3] net: phy: micrel: Remove latencies support lan8814 Horatiu Vultur
2022-04-01 9:48 ` [PATCH net 1/3] dt-bindings: net: micrel: Revert latency support and timestamping check Horatiu Vultur
2022-04-01 12:37 ` Andrew Lunn
2022-04-01 9:48 ` [PATCH net 2/3] net: phy: micrel: Remove latency from driver Horatiu Vultur
2022-04-01 12:47 ` Andrew Lunn
2022-04-01 13:34 ` Horatiu Vultur
2022-04-01 13:59 ` Allan W. Nielsen
2022-04-01 14:05 ` Andrew Lunn [this message]
2022-04-01 14:00 ` Andrew Lunn
2022-04-01 9:48 ` [PATCH net 3/3] net: phy: micrel: Remove DT option lan8814,ignore-ts Horatiu Vultur
2022-04-01 12:47 ` Andrew Lunn
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=YkcGsiEmnk9sKjEj@lunn.ch \
--to=andrew@lunn.ch \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=allan.nielsen@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--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=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
Powered by JetHome