From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Biju Das <biju.das.jz@bp.renesas.com>, Rob Herring <robh+dt@kernel.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 v6 3/3] arm64: dts: renesas: r9a07g044: Add USB2.0 device support
Date: Tue, 17 Aug 2021 19:41:41 +0300 [thread overview]
Message-ID: <05bdd9e8-e68f-c8b4-a7d9-a83f2ca97a58@omp.ru> (raw)
In-Reply-To: <OS0PR01MB5922205202921BA8EC12C26686FE9@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 8/17/21 2:12 PM, Biju Das wrote:
[...]
>>>> Add USB2.0 device support to RZ/G2L SoC DT.
>>>>
>>>> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
>>>> Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>>>> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>>> [...]
>>>> diff --git a/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
>>> b/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
>>>> index de78c921af22..2f313c2a81c7 100644
>>>> --- a/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
>>>> +++ b/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
>>>> @@ -391,6 +391,25 @@
>>>> power-domains = <&cpg>;
>>>> status = "disabled";
>>>> };
>>>> +
>>>> + hsusb: usb@11c60000 {
>>>> + compatible = "renesas,usbhs-r9a07g044",
>>>> + "renesas,rza2-usbhs";
>>>> + reg = <0 0x11c60000 0 0x10000>;
>>>> + interrupts = <GIC_SPI 100 IRQ_TYPE_EDGE_RISING>,
>>>> + <GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>,
>>>> + <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>,
>>>> + <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>;
>>>
>>> Don't we need to specify "interrupt-names" when there a more than 1
>>> interrupts?
>>
>> This dtsi changes, as per binding documentation [1]. As you see,
>> "interrupt-names" is optional.
>
> For now I will go with current dt changes.
>
> Later I will create incremental patches for dt-binding with optional "interrupt-names",
> "clock-names" and "reset names" for all the SoC's supported by this binding doc.
>
> After that, will send an incremental patch with adding optional properties in all SoC dtsi.
>
> Does it make sense?
I had the impression that the "*-names" prop was mandatory for a "*" prop having 2 values or mores.
If it's now allowed to be optional, don't bother with that at all.
> Regards,
> Biju
MBR, Sergei
next prev parent reply other threads:[~2021-08-17 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 15:18 [PATCH v6 0/3] Add USB2.0 support Biju Das
2021-08-12 15:18 ` [PATCH v6 2/3] arm64: dts: renesas: r9a07g044: Add USB2.0 phy and host support Biju Das
2021-08-12 15:18 ` [PATCH v6 3/3] arm64: dts: renesas: r9a07g044: Add USB2.0 device support Biju Das
2021-08-12 15:56 ` Sergei Shtylyov
2021-08-12 16:46 ` Biju Das
2021-08-17 11:12 ` Biju Das
2021-08-17 16:41 ` Sergey Shtylyov [this message]
2021-08-23 9:22 ` Geert Uytterhoeven
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=05bdd9e8-e68f-c8b4-a7d9-a83f2ca97a58@omp.ru \
--to=s.shtylyov@omp.ru \
--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=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 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).