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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 27 Apr 2018 01:37:19 +0000
From:   Anson Huang <anson.huang@....com>
To:     Fabio Estevam <festevam@...il.com>
CC:     Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <kernel@...gutronix.de>,
        Fabio Estevam <fabio.estevam@....com>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        dl-linux-imx <linux-imx@....com>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Andy Duan <fugang.duan@....com>
Subject: RE: [PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support



Anson Huang
Best Regards!


> -----Original Message-----
> From: Fabio Estevam [mailto:festevam@...il.com]
> Sent: Friday, April 27, 2018 1:29 AM
> To: Anson Huang <anson.huang@....com>
> Cc: Shawn Guo <shawnguo@...nel.org>; Sascha Hauer
> <kernel@...gutronix.de>; Fabio Estevam <fabio.estevam@....com>; Rob
> Herring <robh+dt@...nel.org>; Mark Rutland <mark.rutland@....com>;
> dl-linux-imx <linux-imx@....com>; moderated list:ARM/FREESCALE IMX / MXC
> ARM ARCHITECTURE <linux-arm-kernel@...ts.infradead.org>; open list:OPEN
> FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
> <devicetree@...r.kernel.org>; linux-kernel <linux-kernel@...r.kernel.org>;
> Andy Duan <fugang.duan@....com>
> Subject: Re: [PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support
> 
> On Thu, Apr 26, 2018 at 3:57 AM, Anson Huang <anson.huang@....com>
> wrote:
> 
> > The 'phy-supply' is for enabling/disabling phy regulator, but here the
> > MAX7322 IO0 is NOT for enabling/disabling PHY regulator, it is for IO
> > voltage switch between 1.5V and 1.8V, our ENET IO can work with both 1.5V
> and 1.8V, so any config is OK for ENET function.
> 
> Thanks for the clarification.
> 
> > The 1.5V/1.8V selection is a one time setting thing, that means we
> > only need to config it once during boot up, most of i.MX platforms
> > does NOT provide such voltage switch function for ENET IO, on this 6SX
> > sabre auto board, it is more like a backup or validation purpose. With default
> settings, ENET's function is NOT impacted at all.
> >
> > I think we can add a gpio regulator for it and let the regulator
> > initialization set the GPIO Level for fec, such below, with "
> > enable-active-high " present, GPIO will be at LOW and voltage is 1.5V, without
> this property, GPIO will be HIGH and voltage will be 1.8V.
> > +               reg_fec: fec_io_supply {
> > +                       compatible = "regulator-gpio";
> > +                       regulator-name = "1.8V_1.5V_FEC";
> > +                       regulator-min-microvolt = <1500000>;
> > +                       regulator-max-microvolt = <1800000>;
> > +                       states = <1500000 0x0 1800000 0x1>;
> > +                       enable-gpio = <&max7322 0
> GPIO_ACTIVE_HIGH>;
> > +                       vin-supply = <&sw2_reg>;
> > +                       enable-active-high;
> 
> If there is no consumer for this regulator, the regulator API will disable it.
> 
> It seems you need a 'regulator-always-on;'.

GPIO regulator is slight different when regulator framework try to disable
those unused regulator in late phase, in _regulator_do_disable, the GPIO
regulator only got disabled when it is explicitly enabled before (ena_gpio_state
is set when regulator is enabled), but this reg_fec is NOT getting enabled, since
it only has voltage switch function. But I agree that we can anyway add 'regulator-always-on'
to avoid any confusion, will send out new patch, thanks!
 
         if (rdev->ena_pin) {
                 if (rdev->ena_gpio_state) {
                         ret = regulator_ena_gpio_ctrl(rdev, false);


Anson.

> 
> 
> > +               };
> > +
> >
> > Anson.
> >

Powered by blists - more mailing lists