From: Andrew Lunn <andrew@lunn.ch>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Kurt Kanzenbach <kurt@linutronix.de>,
Michael Walle <michael@walle.cc>,
richardcochran@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
mlichvar@redhat.com, netdev@vger.kernel.org,
qiangqing.zhang@nxp.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH RFC V1 net-next 3/4] net: Let the active time stamping layer be selectable.
Date: Tue, 5 Apr 2022 15:29:05 +0200 [thread overview]
Message-ID: <YkxEIZfA0H8yvrzn@lunn.ch> (raw)
In-Reply-To: <defe77d9-1a41-7112-0ef6-a12aa2b725ab@ti.com>
> > Yes, the limitations described above are exactly one of the reasons to
> > make the timestamping layer configurable at run time as done by these
> > patches.
>
> Seems like PHY TS support belongs to HW description category, so could it be device tree material,
> like generic property defining which layer should do timestamping?
Maybe. Device tree is supposed to describe the hardware, not how you
configure the hardware. Which PTP you using is a configuration choice,
so i expect some people will argue it should not be in DT.
Andrew
next prev parent reply other threads:[~2022-04-05 22:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 23:25 [PATCH RFC V1 net-next 3/4] net: Let the active time stamping layer be selectable Richard Cochran
2022-01-03 23:53 ` Russell King (Oracle)
2022-01-04 1:42 ` Richard Cochran
2022-04-04 15:05 ` Michael Walle
2022-04-04 15:20 ` Andrew Lunn
2022-04-04 17:12 ` Michael Walle
2022-04-05 5:59 ` Richard Cochran
2022-04-05 8:48 ` Michael Walle
2022-04-05 15:46 ` Richard Cochran
2022-04-05 9:01 ` Kurt Kanzenbach
2022-04-05 9:19 ` Michael Walle
2022-04-05 11:19 ` Kurt Kanzenbach
2022-04-05 13:15 ` Grygorii Strashko
2022-04-05 13:29 ` Andrew Lunn [this message]
2022-04-05 15:48 ` Richard Cochran
2022-04-06 11:18 ` Grygorii Strashko
2022-01-04 6:29 ` kernel test robot
2022-01-04 6:50 ` kernel test robot
2022-01-20 16:48 ` Vladimir Oltean
2022-01-21 3:38 ` Andrew Lunn
2022-01-21 4:05 ` Richard Cochran
2022-01-21 14:50 ` Vladimir Oltean
2022-01-21 15:28 ` Richard Cochran
2022-01-21 16:23 ` Vladimir Oltean
2022-01-22 2:08 ` Richard Cochran
2022-01-24 9:28 ` Miroslav Lichvar
2022-01-24 15:37 ` Richard Cochran
2022-01-25 15:37 ` Vladimir Oltean
2022-01-21 11:05 ` Kurt Kanzenbach
2022-01-21 15:31 ` Richard Cochran
2022-01-10 15:46 kernel test robot
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=YkxEIZfA0H8yvrzn@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.