From: Vinod Koul <vkoul@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: phy: renesas,usb2-phy: Document RZ/V2L phy bindings
Date: Wed, 2 Mar 2022 19:53:42 +0530 [thread overview]
Message-ID: <Yh997pOE3Mx9fdF2@matsya> (raw)
In-Reply-To: <20220301124255.16836-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 01-03-22, 12:42, Lad Prabhakar wrote:
> Document USB phy bindings for RZ/V2L SoC. RZ/V2L USB phy is identical to
> one found on the RZ/G2L SoC. No driver changes are required as generic
> compatible string "renesas,rzg2l-usb2-phy" will be used as a fallback.
>
> While at it, drop the comment "RZ/G2L family" for "renesas,rzg2l-usb2-phy"
> compatible string as this will avoid changing the line for every new SoC
> addition.
Applied, thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: phy: renesas,usb2-phy: Document RZ/V2L phy bindings
Date: Wed, 2 Mar 2022 19:53:42 +0530 [thread overview]
Message-ID: <Yh997pOE3Mx9fdF2@matsya> (raw)
In-Reply-To: <20220301124255.16836-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 01-03-22, 12:42, Lad Prabhakar wrote:
> Document USB phy bindings for RZ/V2L SoC. RZ/V2L USB phy is identical to
> one found on the RZ/G2L SoC. No driver changes are required as generic
> compatible string "renesas,rzg2l-usb2-phy" will be used as a fallback.
>
> While at it, drop the comment "RZ/G2L family" for "renesas,rzg2l-usb2-phy"
> compatible string as this will avoid changing the line for every new SoC
> addition.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2022-03-02 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:42 [PATCH v2] dt-bindings: phy: renesas, usb2-phy: Document RZ/V2L phy bindings Lad Prabhakar
2022-03-01 12:42 ` [PATCH v2] dt-bindings: phy: renesas,usb2-phy: " Lad Prabhakar
2022-03-02 14:23 ` Vinod Koul [this message]
2022-03-02 14:23 ` 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=Yh997pOE3Mx9fdF2@matsya \
--to=vkoul@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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 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.