From: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
To: Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: RE: [PATCH v6 2/6] dt-bindings: dma: rz-dmac: Document RZ/V2H(P) family of SoCs
Date: Wed, 23 Apr 2025 14:05:11 +0000 [thread overview]
Message-ID: <TYCSPRMB000972FF9EEBCF75D03FF919C2BA2@TYCSPRMB0009.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYCSPRMB0009EAE305A3BC54E74D4A5EC2BA2@TYCSPRMB0009.jpnprd01.prod.outlook.com>
Hi Geert,
> From: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> Sent: 23 April 2025 14:27
> Subject: RE: [PATCH v6 2/6] dt-bindings: dma: rz-dmac: Document RZ/V2H(P) family of SoCs
>
> Hi Geert,
>
> Thanks for your feedback!
>
> > From: Geert Uytterhoeven <geert@linux-m68k.org>
> > Sent: 23 April 2025 12:37
> > Subject: Re: [PATCH v6 2/6] dt-bindings: dma: rz-dmac: Document RZ/V2H(P) family of SoCs
> >
> > Hi Fabrizio,
> >
> > On Tue, 22 Apr 2025 at 19:40, Fabrizio Castro
> > <fabrizio.castro.jz@renesas.com> wrote:
> > > Document the Renesas RZ/V2H(P) family of SoCs DMAC block.
> > > The Renesas RZ/V2H(P) DMAC is very similar to the one found on the
> > > Renesas RZ/G2L family of SoCs, but there are some differences:
> > > * It only uses one register area
> > > * It only uses one clock
> > > * It only uses one reset
> > > * Instead of using MID/IRD it uses REQ No
> > > * It is connected to the Interrupt Control Unit (ICU)
> > >
> > > Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
> > > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > > Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > > ---
> > > v5->v6:
> > > * Reworked the description of `#dma-cells`.
> > > * Reworked `renesas,icu` related descriptions.
> > > * Added `reg:`->`minItems: 2` for `renesas,r7s72100-dmac`.
> > > * Since the structure of the document remains the same, I have kept
> > > the tags I have received. Please let me know if that's not okay.
> >
> > Thanks for the update!
> >
> > Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > > --- a/Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml
> > > +++ b/Documentation/devicetree/bindings/dma/renesas,rz-dmac.yaml
> > > @@ -80,12 +85,26 @@ properties:
> > > items:
> > > - description: Reset for DMA ARESETN reset terminal
> > > - description: Reset for DMA RST_ASYNC reset terminal
> > > + minItems: 1
> > >
> > > reset-names:
> > > items:
> > > - const: arst
> > > - const: rst_async
> > >
> > > + renesas,icu:
> > > + description:
> > > + It must contain the phandle to the ICU, and the index of the DMAC as seen
> > > + from the ICU (e.g. parameter k from register ICU_DMkSELy).
> >
> > Doesn't really hurt, but this description is identical to the formal
> > description of the items below.
>
> Okay, I'll drop this description, and I'll keep the description for the item below.
Actually, I cannot take this out:
'description' is a dependency of '$ref'
'/schemas/types.yaml#/definitions/phandle-array' does not match '^#/(definitions|\\$defs)/'
hint: A vendor property can have a $ref to a a $defs schema
hint: Vendor specific properties must have a type and description unless they have a defined, common suffix.
I'll rephrase the description to:
It must contain the phandle to the ICU and the DMAC index as seen from the ICU.
Thanks!
Cheers,
Fab
>
> >
> > > + $ref: /schemas/types.yaml#/definitions/phandle-array
> > > + items:
> > > + - items:
> > > + - description: phandle to the ICU node.
> >
> > Phandle
>
> And I'll amend accordingly.
>
> I'll send a new version shortly.
>
> Thanks!
>
> Cheers,
> Fab
>
> >
> > > + - description:
> > > + The number of the DMAC as seen from the ICU, i.e. parameter k from
> > > + register ICU_DMkSELy. This may differ from the actual DMAC instance
> > > + number.
> > > +
> > > required:
> > > - compatible
> > > - reg
> >
> > 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:[~2025-04-23 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 17:39 [PATCH v6 0/6] Add DMAC support to the RZ/V2H(P) Fabrizio Castro
2025-04-22 17:39 ` [PATCH v6 1/6] dt-bindings: dma: rz-dmac: Restrict properties for RZ/A1H Fabrizio Castro
2025-04-22 17:39 ` [PATCH v6 2/6] dt-bindings: dma: rz-dmac: Document RZ/V2H(P) family of SoCs Fabrizio Castro
2025-04-23 11:37 ` Geert Uytterhoeven
2025-04-23 13:26 ` Fabrizio Castro
2025-04-23 14:05 ` Fabrizio Castro [this message]
2025-04-23 12:13 ` Rob Herring (Arm)
2025-04-22 17:39 ` [PATCH v6 3/6] irqchip/renesas-rzv2h: Add rzv2h_icu_register_dma_req() Fabrizio Castro
2025-04-22 17:39 ` [PATCH v6 4/6] dmaengine: sh: rz-dmac: Allow for multiple DMACs Fabrizio Castro
2025-04-22 17:39 ` [PATCH v6 5/6] dmaengine: sh: rz-dmac: Add RZ/V2H(P) support Fabrizio Castro
2025-04-23 13:13 ` Vinod Koul
2025-04-23 13:46 ` Fabrizio Castro
2025-04-22 17:39 ` [PATCH v6 6/6] arm64: dts: renesas: r9a09g057: Add DMAC nodes Fabrizio Castro
2025-05-14 15:02 ` (subset) [PATCH v6 0/6] Add DMAC support to the RZ/V2H(P) Vinod Koul
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=TYCSPRMB000972FF9EEBCF75D03FF919C2BA2@TYCSPRMB0009.jpnprd01.prod.outlook.com \
--to=fabrizio.castro.jz@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®