[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CK=c+=y2BgsYRKVujgn3yRWYjOXkz0EwzBEVXDVpq0Gg@mail.gmail.com>
Date: Wed, 10 Sep 2014 14:06:11 -0300
From: Fabio Estevam <festevam@...il.com>
To: Stefan Wahren <wahrenst@....net>
Cc: Mark Rutland <mark.rutland@....com>,
"lgirdwood@...il.com" <lgirdwood@...il.com>,
"broonie@...nel.org" <broonie@...nel.org>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Pawel Moll <Pawel.Moll@....com>,
"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
"galak@...eaurora.org" <galak@...eaurora.org>,
"stefan.wahren@...e.com" <stefan.wahren@...e.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RFC 2/3] ARM: regulator: add Freescale MXS regulator driver
On Wed, Sep 10, 2014 at 2:24 PM, Stefan Wahren <wahrenst@....net> wrote:
> sorry i don't have a clue. In the original code there isn't a comment about
> the reason. Currently there is no init of the vddio regulator by the kernel
> and everything works fine.
>
> @Fabio: Do you have any doubts?
I would say, just use and report whatever value comes from the
bootloader. No need to force a particular regulator output.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists