linux-kernel - Re: [PATCH 1/2] dt-bindings: phy-imx8mq-usb: add reset-gpios property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210209200148.GA31636@robh.at.kernel.org>
Date:   Tue, 9 Feb 2021 14:01:48 -0600
From:   Rob Herring <robh@...nel.org>
To:     Adrien Grassein <adrien.grassein@...il.com>
Cc:     kishon@...com, vkoul@...nel.org, shawnguo@...nel.org,
        s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com,
        linux-imx@....com, rikard.falkeborn@...il.com, peter.chen@....com,
        jun.li@....com, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: phy-imx8mq-usb: add reset-gpios property

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@...il.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@...f0040 {
> -- 
> 2.25.1
>