[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210910141423.GA21865@hoboy.vegasvil.org>
Date: Fri, 10 Sep 2021 07:14:23 -0700
From: Richard Cochran <richardcochran@...il.com>
To: "Machnikowski, Maciej" <maciej.machnikowski@...el.com>
Cc: Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Ido Schimmel <idosch@...sch.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"abyagowi@...com" <abyagowi@...com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
Michal Kubecek <mkubecek@...e.cz>,
Saeed Mahameed <saeed@...nel.org>,
Michael Chan <michael.chan@...adcom.com>
Subject: Re: [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message
to get SyncE status
On Thu, Sep 09, 2021 at 08:18:10AM +0000, Machnikowski, Maciej wrote:
> Controlling the clock that actually drives any components (PHY/MAC) in
> runtime can be a good way to brick the part.
I didn't say that.
> I feel that, while the reuse
> of structures may be a good idea, the userspace API for clocks is not.
> They are usually set up once at the board init level and stay like that "forever".
>
> The outputs we need to control are only a subset of all of them and they
> rather fall in the PTP pins level of details, rather than clock ones.
clk-gate.c
clk-mux.c
Making that available for user space to twiddle is a better way that
tacking on to the PTP stuff.
You can model your device as having a multiplexer in front of it.
Thanks,
Richard
Powered by blists - more mailing lists