From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-usb@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 02/12] dt-bindings: usb: renesas,usb3-peri: Update reset, clock-name and interrupts properties
Date: Fri, 13 Jan 2023 14:49:06 -0600 [thread overview]
Message-ID: <167364294568.2895791.15384252515090224293.robh@kernel.org> (raw)
In-Reply-To: <20230112215906.494394-3-biju.das.jz@bp.renesas.com>
On Thu, 12 Jan 2023 21:58:56 +0000, Biju Das wrote:
> On RZ/V2M, USB3DRD module manages the drd_reset. Moreover, the interrupts
> drd, gpi and bc are part of USB3DRD block. This patch removes
> drd_reset and the interrupts drd, bc and gpi from usb3_peri bindings.
> After this, there is only one reset and interrupts and therefore
> removing reset-names and interrupt-names as well.
>
> Whilst, Update the clock-name "aclk"->"axi" to make it consistent with
> DRD and host blocks.
>
> There is any harm in making such a change as, no users of
> renesas,r9a09g011-usb3-peri yet in kernel release.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v1->v2:
> * Moved DRD interrupts to DRD bindings
> * Updated interrupts and dropped interrupt-names
> * Renamed aclk->axi
> ---
> .../bindings/usb/renesas,usb3-peri.yaml | 39 ++-----------------
> 1 file changed, 3 insertions(+), 36 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-01-13 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 21:58 [PATCH v2 00/12] ADD USB3.1 HOST, Peri and DRD support Biju Das
2023-01-12 21:58 ` [PATCH v2 01/12] dt-bindings: usb: renesas,usb-xhci: Document RZ/V2M support Biju Das
2023-01-12 21:58 ` [PATCH v2 02/12] dt-bindings: usb: renesas,usb3-peri: Update reset, clock-name and interrupts properties Biju Das
2023-01-13 20:49 ` Rob Herring [this message]
2023-01-12 21:58 ` [PATCH v2 03/12] dt-bindings: usb: renesas,usb3-peri: Document RZ/V2MA bindings Biju Das
2023-01-13 20:49 ` Rob Herring
2023-01-12 21:58 ` [PATCH v2 04/12] dt-bindings: usb: Add RZ/V2M USB3DRD binding Biju Das
2023-01-13 20:50 ` Rob Herring
2023-01-12 21:59 ` [PATCH v2 10/12] arm64: dts: renesas: r9a09g011: Add USB3 DRD, device and host nodes Biju Das
2023-01-12 21:59 ` [PATCH v2 11/12] arm64: dts: renesas: rzv2mevk2: Enable USB3 DRD, Peripheral and Host Biju Das
2023-01-12 21:59 ` [PATCH v2 12/12] arm64: dts: renesas: rzv2mevk2: Enable USB3 role switch Biju Das
2023-01-19 13:10 ` [PATCH v2 00/12] ADD USB3.1 HOST, Peri and DRD support Greg Kroah-Hartman
2023-01-21 9:59 ` Biju Das
2023-01-21 10:06 ` Greg Kroah-Hartman
2023-01-21 10:54 ` 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=167364294568.2895791.15384252515090224293.robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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