From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>, linux-clk@vger.kernel.org
Subject: Re: [PATCH v1] clk: Move struct clk_core to use struct fwnode_handle
Date: Thu, 11 Feb 2021 12:37:52 +0200 [thread overview]
Message-ID: <YCUJAGKKkP0AI5fX@smile.fi.intel.com> (raw)
In-Reply-To: <161301033161.1254594.5999850767233898633@swboyd.mtv.corp.google.com>
On Wed, Feb 10, 2021 at 06:25:31PM -0800, Stephen Boyd wrote:
> Quoting Andy Shevchenko (2021-02-10 03:01:53)
> > On Tue, Feb 09, 2021 at 03:59:05PM -0800, Stephen Boyd wrote:
> > > Quoting Andy Shevchenko (2021-02-09 09:09:52)
> > > > fwnode is an abstraction on the different types of firmware nodes.
> > > > In order to allow clocks to be linked with any type of such node,
> > > > start a conversion to the struct fwnode_handle instead of being
> > > > stuck with struct device_node.
> > >
> > > Is ACPI going to support clk hardware? We're "stuck" with device nodes
> > > mostly because there isn't a clk framework for ACPI.
> >
> > Here I'm not talking about ACPI vs. DT vs. anything, the pure motivation is to
> > make less divergence of standalone OF vs. fwnode (see IRQ domain APIs, for
> > example, which allows to use them in regmap IRQ APIs).
> >
>
> I thought the fwnode changes in IRQ domain APIs was to work across both
> ACPI and DT. Please tell me more!
I wish I could dig this out from the commit
f110711a6053 ("irqdomain: Convert irqdomain-%3Eof_node to fwnode")
but it kept silent what the motivation of doing that.
For me the fwnode API brings an agnostic interface which is good thing to have
and makes it easier to be used by other providers (you know that we have swnode
besides ACPI and DT, right?).
I would like to re-use clk-gpio in ACPI based environment and I found it quite
difficult without changing a lot of things in clk framework which is tighten to
OF by nails. This is not good from design perspective and makes my journey
miserable. Of course if clk is against this, I would live with copy'n'paste
approach — no hard feelings. Just let me know.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-02-11 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 17:09 [PATCH v1] clk: Move struct clk_core to use struct fwnode_handle Andy Shevchenko
2021-02-09 23:59 ` Stephen Boyd
2021-02-10 11:01 ` Andy Shevchenko
2021-02-11 2:25 ` Stephen Boyd
2021-02-11 10:37 ` Andy Shevchenko [this message]
2021-02-11 19:09 ` Stephen Boyd
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=YCUJAGKKkP0AI5fX@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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