From: Marek Vasut <marex@denx.de>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-power <linux-power@rohmsemiconductoreurope.onmicrosoft.com>
Subject: Re: [PATCH 2/3] clk: Introduce 'critical-clocks' property
Date: Thu, 17 Feb 2022 14:43:32 +0100 [thread overview]
Message-ID: <8b179fe1-55e4-e811-1ac2-46ac726c22d9@denx.de> (raw)
In-Reply-To: <88ee0a11-359e-60a5-4d96-54fef6514e69@fi.rohmeurope.com>
[...]
>>> Anyways, seeing you added a dummy bd71837_match_clkspec in a follow-up
>>> patch for BD71837 - which has only single clock - I wonder if there is a
>>> way to omit that dummy callback in controllers which really provide only
>>> one clock?
>>
>> Yes, I think we can omit the match_clkspec call for clock controllers
>> with clock-cells == 0 altogether.
>
> That would mean you could probably drop the bd718x7 driver patch, right?
Yes
I'm just waiting for feedback from Stephen on 2/3, then I'll send V2.
next prev parent reply other threads:[~2022-02-17 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:44 [PATCH 1/3] dt-bindings: clk: Introduce 'critical-clocks' property Marek Vasut
2022-02-15 8:44 ` [PATCH 2/3] " Marek Vasut
2022-02-15 11:23 ` kernel test robot
2022-02-15 13:57 ` kernel test robot
2022-02-16 12:06 ` Vaittinen, Matti
2022-02-16 16:52 ` Marek Vasut
2022-02-17 5:01 ` Vaittinen, Matti
2022-02-17 13:43 ` Marek Vasut [this message]
2022-02-17 22:23 ` Stephen Boyd
2022-02-21 0:58 ` Marek Vasut
2022-03-09 20:54 ` Marek Vasut
2022-03-12 5:04 ` Stephen Boyd
2022-03-12 10:26 ` Marek Vasut
2022-03-15 23:52 ` Stephen Boyd
2022-03-16 11:30 ` Marek Vasut
2022-05-03 19:17 ` Marek Vasut
2022-02-15 8:44 ` [PATCH 3/3] clk: bd718xx: Implement basic .match_clkspec Marek Vasut
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=8b179fe1-55e4-e811-1ac2-46ac726c22d9@denx.de \
--to=marex@denx.de \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-power@rohmsemiconductoreurope.onmicrosoft.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).