From: Rob Herring <robh@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: kishon@ti.com, vkoul@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
rikard.falkeborn@gmail.com, peter.chen@nxp.com, jun.li@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: phy-imx8mq-usb: add reset-gpios property
Date: Tue, 9 Feb 2021 14:01:48 -0600 [thread overview]
Message-ID: <20210209200148.GA31636@robh.at.kernel.org> (raw)
In-Reply-To: <20210128221255.2673992-1-adrien.grassein@gmail.com>
On Thu, Jan 28, 2021 at 11:12:54PM +0100, Adrien Grassein wrote:
> Add an optional GPIO in the dtb description that will
> be used to reset the connected hub (if any).
>
> Signed-off-by: Adrien Grassein <adrien.grassein@gmail.com>
> ---
> Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.txt b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.txt
> index 7c70f2ad9942..6ee2b42e0f22 100644
> --- a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.txt
> +++ b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.txt
> @@ -9,6 +9,7 @@ Required properties:
>
> Optional properties:
> - vbus-supply: A phandle to the regulator for USB VBUS.
> +- reset-gpios: A phandle to the reset signal of the connected hub (if any).
This should go in a hub node (or whatever device has a reset line).
>
> Example:
> usb3_phy0: phy@381f0040 {
> --
> 2.25.1
>
prev parent reply other threads:[~2021-02-09 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 22:12 [PATCH 1/2] dt-bindings: phy-imx8mq-usb: add reset-gpios property Adrien Grassein
2021-01-28 22:12 ` [PATCH 2/2] phy: fsl-imx8mq-usb: handle resettable hubs Adrien Grassein
2021-02-02 2:01 ` Jun Li
2021-02-09 20:01 ` Rob Herring [this message]
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=20210209200148.GA31636@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=rikard.falkeborn@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).