From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Machnikowski, Maciej" <maciej.machnikowski@intel.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ido Schimmel <idosch@idosch.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"abyagowi@fb.com" <abyagowi@fb.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
Michal Kubecek <mkubecek@suse.cz>,
Saeed Mahameed <saeed@kernel.org>,
Michael Chan <michael.chan@broadcom.com>
Subject: Re: [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status
Date: Thu, 9 Sep 2021 00:59:27 +0200 [thread overview]
Message-ID: <YTlAT+1wkazy3Uge@lunn.ch> (raw)
In-Reply-To: <20210908152027.313d7168@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Wed, Sep 08, 2021 at 03:20:27PM -0700, Jakub Kicinski wrote:
> On Wed, 8 Sep 2021 21:34:37 +0200 Andrew Lunn wrote:
> > Since we are talking about clocks and dividers, and multiplexors,
> > should all this be using the common clock framework, which already
> > supports most of this? Do we actually need something new?
>
> Does the common clock framework expose any user space API?
Ah, good point. No, i don't think it does, apart from debugfs, which
is not really a user space API, and it contains read only descriptions
of the clock tree, current status, mux settings, dividers etc.
So probably anybody implemented the proposed API the Linux way will
use the common clock framework and its internal API, and debug the
implementation via debugfs.
PHY drivers already do use it, e.g. when the PHY is using a clock
provided by the MAC, it uses the API to enable/disable and set ifs
frequency as needed.
Andrew
next prev parent reply other threads:[~2021-09-08 22:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 15:14 [RFC v4 net-next 0/2] Add RTNL interface for SyncE Maciej Machnikowski
2021-09-03 15:14 ` [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status Maciej Machnikowski
2021-09-03 16:18 ` Stephen Hemminger
2021-09-03 22:20 ` Machnikowski, Maciej
2021-09-03 22:14 ` Jakub Kicinski
2021-09-06 18:30 ` Machnikowski, Maciej
2021-09-06 18:39 ` Jakub Kicinski
2021-09-06 19:01 ` Machnikowski, Maciej
2021-09-07 1:01 ` Jakub Kicinski
2021-09-07 8:50 ` Machnikowski, Maciej
2021-09-07 14:55 ` Jakub Kicinski
2021-09-07 15:47 ` Machnikowski, Maciej
2021-09-07 19:47 ` Jakub Kicinski
2021-09-08 8:03 ` Machnikowski, Maciej
2021-09-08 16:21 ` Jakub Kicinski
2021-09-08 17:30 ` Machnikowski, Maciej
2021-09-08 19:34 ` Andrew Lunn
2021-09-08 20:27 ` Machnikowski, Maciej
2021-09-08 22:20 ` Jakub Kicinski
2021-09-08 22:59 ` Andrew Lunn [this message]
2021-09-09 2:09 ` Richard Cochran
2021-09-09 8:18 ` Machnikowski, Maciej
2021-09-10 14:14 ` Richard Cochran
2021-09-08 22:18 ` Jakub Kicinski
2021-09-08 23:14 ` Andrew Lunn
2021-09-08 23:58 ` Jakub Kicinski
2021-09-09 8:26 ` Machnikowski, Maciej
2021-09-09 9:24 ` Machnikowski, Maciej
2021-09-09 10:15 ` David Miller
2021-09-09 8:11 ` Machnikowski, Maciej
2021-09-13 8:50 ` Ido Schimmel
2021-09-21 13:36 ` Ido Schimmel
2021-09-21 13:15 ` Ido Schimmel
2021-09-21 13:37 ` Machnikowski, Maciej
2021-09-21 14:58 ` Ido Schimmel
2021-09-21 21:14 ` Jakub Kicinski
2021-09-22 6:22 ` Ido Schimmel
2021-09-03 15:14 ` [PATCH net-next 2/2] ice: add support for reading SyncE DPLL state Maciej Machnikowski
2021-09-03 22:06 ` Jakub Kicinski
2021-09-21 13:25 ` Ido Schimmel
-- strict thread matches above, loose matches on Subject: below --
2021-08-31 11:52 [PATCH net-next 0/2] Add RTNL interface for SyncE EEC state Maciej Machnikowski
2021-08-31 11:52 ` [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status Maciej Machnikowski
2021-08-31 13:44 ` Jakub Kicinski
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=YTlAT+1wkazy3Uge@lunn.ch \
--to=andrew@lunn.ch \
--cc=abyagowi@fb.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=idosch@idosch.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.machnikowski@intel.com \
--cc=michael.chan@broadcom.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=saeed@kernel.org \
/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