From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 1/2] arm64: dts: renesas: r9a07g044: Fix external clk node names
Date: Mon, 25 Apr 2022 18:30:04 +0200 [thread overview]
Message-ID: <d3fbb3cf-19e2-a2ad-1976-f9687150a866@linaro.org> (raw)
In-Reply-To: <OS0PR01MB5922AB6D16AB716FECAA140786F89@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 25/04/2022 18:26, Biju Das wrote:
>>
>> What do you mean "ok"? I said "clk-[0-9]", so "clk-0", "clk-1", "clk-2"
>> and so on. No specific prefix.
>
> Ah ok.
>
> As you mentioned above "generic part is "clk". You add specific audio/audio-X prefix
> or suffix"
>
> So based on that, I thought "clk" is generic part and "-1-audio" as suffix, "clk-1-audio"
> should be acceptable.
>
> For eg:- If I plan to match the label name with the hardware manual(audio_clk1),
Labels are not restricted (except using [a-z0-9_], no dashes), so it is
perfectly fine.
>
> then, as per the discussion we have, the node names should be
>
> either
>
> "audio_clk1: clk-0"
>
> or
>
> "audio_clk1: clk-1"
>
> Or
>
> "audio_clk1: audio1-clk"
>
> Correct?
Yes, correct.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-25 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 14:06 [PATCH 1/2] arm64: dts: renesas: r9a07g044: Fix external clk node names Biju Das
2022-04-23 14:06 ` [PATCH 2/2] arm64: dts: renesas: r9a07g054: " Biju Das
2022-04-23 19:34 ` [PATCH 1/2] arm64: dts: renesas: r9a07g044: " Krzysztof Kozlowski
2022-04-24 6:45 ` Biju Das
2022-04-24 7:50 ` Biju Das
2022-04-24 10:04 ` Krzysztof Kozlowski
2022-04-24 10:22 ` Biju Das
2022-04-24 14:39 ` Krzysztof Kozlowski
2022-04-25 15:28 ` Biju Das
2022-04-25 15:50 ` Krzysztof Kozlowski
2022-04-25 16:26 ` Biju Das
2022-04-25 16:30 ` Krzysztof Kozlowski [this message]
2022-04-25 16:52 ` 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=d3fbb3cf-19e2-a2ad-1976-f9687150a866@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.