From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 1/7] dt-bindings: clk: r9a07g044-cpg: Update clock definitions
Date: Tue, 22 Jun 2021 16:56:44 +0200 [thread overview]
Message-ID: <CAMuHMdWQK_k3ePJpx2CF-X9TNgPYzzP8AW9N2rDjXSOAP2wNxQ@mail.gmail.com> (raw)
In-Reply-To: <OS0PR01MB5922B821B3893BAD08D2573A86099@OS0PR01MB5922.jpnprd01.prod.outlook.com>
Hi Biju,
On Tue, Jun 22, 2021 at 11:26 AM Biju Das <biju.das.jz@bp.renesas.com> wrote:
> > Subject: Re: [PATCH 1/7] dt-bindings: clk: r9a07g044-cpg: Update clock
> > definitions
> > On Fri, Jun 18, 2021 at 11:58 AM Biju Das <biju.das.jz@bp.renesas.com>
> > wrote:
> > > Update clock definitions as per the RZG2L_clock_list(Rev.02) manual.
> > >
> > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > Thanks for your patch!
> >
> > > --- a/include/dt-bindings/clock/r9a07g044-cpg.h
> > > +++ b/include/dt-bindings/clock/r9a07g044-cpg.h
> > I do think we need a separate list of definitions for resets. While
> > simple modules like SCIF and I2C have a one-to-one mapping from clock bits
> > to reset bits for, this is not the case for all modules.
> > E.g. SDHI has 4 clocks per instance, but only a single reset signal per
> > instance, while CANFD has a single clock, but two reset signals.
>
> OK, Agreed. We will list separate definitions for resets like,
>
> #define R9A07G044_RST_SDHI0 X1
> #define R9A07G044_RST_SDHI1 X2
> #define R9A07G044_RST_CAN X3
Please use names that match the documentation, like
R9A07G044_SDHI0_IXRST and R9A07G044_SDHI0_CANFD_RSTP_N.
> Clk definitions
>
> DEF_MOD("sdhi0_imclk", R9A07G044_SDHI0_IMCLK,
> CLK_SD0_DIV4,
> 0x554, BIT(0)),
> DEF_MOD("sdhi0_imclk2", R9A07G044_SDHI0_IMCLK2,
> CLK_SD0_DIV4,
> 0x554, BIT(1)),
> DEF_MOD("sdhi0_clk_hs", R9A07G044_SDHI0_CLK_HS,
> R9A07G044_CLK_SD0,
> 0x554, BIT(2),
> DEF_MOD("sdhi0_aclk", R9A07G044_SDHI0_ACLK,
> R9A07G044_CLK_P1,
> 0x554, BIT(3)),
As each clock now corresponds to a single bit, you can store the bit
number (e.g. "0") instead of the bitmask ("BIT(0)"). This also works
for bits > 8, without needing to enlarge rzg2l_mod_clk.onoff ;-)
> Reset definitions
> --------------------
> DEF_RST("sdhi0_RST", R9A07G044_RST_SDHI0,
> 0x854, BIT(0)),
Same here.
Note that you do not need names for resets, unlike clocks.
> And DTS instantiate both reset and clock entries.
What do you mean by "instantiate"?
The "clocks" and "resets" properties?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2021-06-22 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210618095823.19885-1-biju.das.jz@bp.renesas.com>
2021-06-18 9:58 ` [PATCH 1/7] dt-bindings: clk: r9a07g044-cpg: Update clock definitions Biju Das
2021-06-21 15:49 ` Geert Uytterhoeven
2021-06-22 9:26 ` Biju Das
2021-06-22 14:56 ` Geert Uytterhoeven [this message]
2021-06-23 11:11 ` Biju Das
2021-06-23 11:59 ` Geert Uytterhoeven
2021-06-23 12:33 ` Biju Das
2021-06-18 9:58 ` [PATCH 4/7] arm64: dts: renesas: r9a07g044: Update SCIF0 clock Biju Das
2021-06-18 9:58 ` [PATCH 7/7] arm64: dts: renesas: r9a07g044: Add I2C nodes Biju Das
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=CAMuHMdWQK_k3ePJpx2CF-X9TNgPYzzP8AW9N2rDjXSOAP2wNxQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@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).