[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5C2kzvT7UYw8Zw8ztr1w6_C=MjcFPgU1Wfgjrag=dVwbQ@mail.gmail.com>
Date: Mon, 24 Jul 2017 09:49:56 -0300
From: Fabio Estevam <festevam@...il.com>
To: Gary Bisson <gary.bisson@...ndarydevices.com>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
Shawn Guo <shawnguo@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/2] ARM: dts: imx6qdl-sabrelite: fix USB PHY reset
Hi Gary,
On Mon, Jul 24, 2017 at 5:50 AM, Gary Bisson
<gary.bisson@...ndarydevices.com> wrote:
> +
> + reg_usb_h1_vbus: regulator@7 {
> + compatible = "regulator-fixed";
> + reg = <7>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_usbh1>;
> + regulator-name = "usb_h1_vbus";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + gpio = <&gpio7 12 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + regulator-always-on;
As this regulator is controlled via GPIO I believe you should remove
the ' regulator-always-on' property.
Same applies to 2/2/
Powered by blists - more mailing lists