From: Jakub Kicinski <kuba@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Vadim Fedorenko <vfedorenko@novek.ru>,
Vadim Fedorenko <vadfed@fb.com>, Aya Levin <ayal@nvidia.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org
Subject: Re: [RFC PATCH v1 0/3] Create common DPLL/clock configuration API
Date: Fri, 24 Jun 2022 10:55:22 -0700 [thread overview]
Message-ID: <20220624105522.1961b4d3@kernel.org> (raw)
In-Reply-To: <3d2970c7-f785-edf7-2936-807cf21ec65e@gmail.com>
On Fri, 24 Jun 2022 10:20:44 -0700 Florian Fainelli wrote:
> On 6/22/22 17:57, Vadim Fedorenko wrote:
> > Implement common API for clock/DPLL configuration and status reporting.
> > The API utilises netlink interface as transport for commands and event
> > notifications. This API aim to extend current pin configuration and
> > make it flexible and easy to cover special configurations.
>
> Any reasons why you are not copying the Linux common clock framework
> maintainers and not seeking to get your code included under drivers/clk/
> where it would seem like a more natural place for it?
>
> Is netlink really a necessary configuration interface for those devices?
Sorry, likely my fault. Vadim asked me who to CC and I suggested to just
hit linux-arm-kernel assuming it's the best place for chance encounters
with embedded folks. An assumption based on no real data or experience.
Regarding the clock framework I think I brought that suggestion up in
the mega thread when Maciej M proposed the SyncE support and putting
all the PLL info directly in rtnetlink. There wasn't much support,
and perhaps that's fair, clock generation vs runtime DPLL config for
time source purposes are different use cases.
With that longish excuse out of the way, CCing linux-clk now, here's
the lore link to the thread:
https://lore.kernel.org/r/20220623005717.31040-2-vfedorenko@novek.ru/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-06-24 17:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 0:57 [RFC PATCH v1 0/3] Create common DPLL/clock configuration API Vadim Fedorenko
2022-06-23 0:57 ` [RFC PATCH v1 1/3] dpll: Add DPLL framework base functions Vadim Fedorenko
2022-06-23 15:33 ` Kubalewski, Arkadiusz
2022-06-23 22:48 ` Vadim Fedorenko
2022-06-24 17:36 ` Kubalewski, Arkadiusz
2022-06-26 19:39 ` Vadim Fedorenko
2022-06-29 1:46 ` Kubalewski, Arkadiusz
2022-06-29 23:30 ` Vadim Fedorenko
2022-06-30 10:00 ` Kubalewski, Arkadiusz
[not found] ` <20220629192312.45acd2fd@kernel.org>
2022-06-30 15:50 ` Vadim Fedorenko
2022-06-30 18:27 ` Jakub Kicinski
2022-06-23 0:57 ` [RFC PATCH v1 2/3] dpll: add netlink events Vadim Fedorenko
2022-06-23 0:57 ` [RFC PATCH v1 3/3] ptp_ocp: implement DPLL ops Vadim Fedorenko
2022-06-23 18:28 ` Jonathan Lemon
2022-06-23 23:11 ` Vadim Fedorenko
2022-06-23 23:36 ` Jonathan Lemon
2022-06-26 19:28 ` Vadim Fedorenko
2022-06-27 19:27 ` Jonathan Lemon
2022-06-27 22:06 ` Vadim Fedorenko
2022-06-26 19:27 ` Vadim Fedorenko
2022-06-27 19:23 ` Jonathan Lemon
2022-06-27 22:04 ` Vadim Fedorenko
2022-06-24 17:20 ` [RFC PATCH v1 0/3] Create common DPLL/clock configuration API Florian Fainelli
2022-06-24 17:55 ` Jakub Kicinski [this message]
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=20220624105522.1961b4d3@kernel.org \
--to=kuba@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=ayal@nvidia.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadfed@fb.com \
--cc=vfedorenko@novek.ru \
/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;
as well as URLs for NNTP newsgroup(s).