From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Rob Herring <robh@kernel.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<nicolas.ferre@microchip.com>, <kavyasree.kotagiri@microchip.com>,
<eugen.hristev@microchip.com>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] dt-bindings: clock: lan966x: Extend for clock gate support
Date: Fri, 29 Oct 2021 14:06:31 +0200 [thread overview]
Message-ID: <20211029120631.a7p6d6hurefz4emt@soft-dev3-1.localhost> (raw)
In-Reply-To: <YXjCufT1WyLEriY2@robh.at.kernel.org>
The 10/26/2021 22:08, Rob Herring wrote:
Hi Rob,
>
> On Tue, Oct 19, 2021 at 10:44:47AM +0200, Horatiu Vultur wrote:
> > It is required to add a new resource to be able to access the clock gate
> > registers. Now that we have 2 resources, add also reg-names property to
> > make more clear.
>
> It is an ABI breakage to require 2 reg entries. If that's okay for this
> binding, you need to explain why. The binding requiring 2 so that DT
> files get updated, but the driver allowing for 1 is okay.
I will make the resource optional not to break any ABI.
>
> >
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> > ---
> > .../bindings/clock/microchip,lan966x-gck.yaml | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> > index fca83bd68e26..047c77e049f1 100644
> > --- a/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> > +++ b/Documentation/devicetree/bindings/clock/microchip,lan966x-gck.yaml
> > @@ -19,7 +19,14 @@ properties:
> > const: microchip,lan966x-gck
> >
> > reg:
> > - maxItems: 1
> > + items:
> > + - description: core registers
> > + - description: gate registers
> > +
> > + reg-names:
> > + items:
> > + - const: core
> > + - const: gate
> >
> > clocks:
> > items:
> > @@ -39,6 +46,7 @@ properties:
> > required:
> > - compatible
> > - reg
> > + - reg-names
> > - clocks
> > - clock-names
> > - '#clock-cells'
> > @@ -52,6 +60,7 @@ examples:
> > #clock-cells = <1>;
> > clocks = <&cpu_clk>, <&ddr_clk>, <&sys_clk>;
> > clock-names = "cpu", "ddr", "sys";
> > - reg = <0xe00c00a8 0x38>;
> > + reg = <0xe00c00a8 0x38>, <0xe00c02cc 0x4>;
> > + reg-names = "core", "gate";
> > };
> > ...
> > --
> > 2.33.0
> >
> >
--
/Horatiu
next prev parent reply other threads:[~2021-10-29 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 8:44 [RFC PATCH 0/3] Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-19 8:44 ` [RFC PATCH 1/3] dt-bindings: clock: lan966x: Extend for clock gate support Horatiu Vultur
2021-10-27 3:08 ` Rob Herring
2021-10-29 12:06 ` Horatiu Vultur [this message]
2021-10-19 8:44 ` [RFC PATCH 2/3] dt-bindings: clock: lan966x: Extend includes with clock gates Horatiu Vultur
2021-10-27 3:09 ` Rob Herring
2021-10-19 8:44 ` [RFC PATCH 3/3] clk: lan966x: Extend lan966x clock driver for clock gating support Horatiu Vultur
2021-10-29 6:41 ` Stephen Boyd
2021-10-29 9:35 ` Horatiu Vultur
2021-10-29 23:32 ` Stephen Boyd
2021-10-31 9:03 ` Horatiu Vultur
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=20211029120631.a7p6d6hurefz4emt@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh@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).