[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <12F88867-EF9E-4BCA-9209-6879A39F3DEA@collabora.co.uk>
Date: Thu, 28 Aug 2014 11:59:16 +0200
From: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To: Mark Brown <broonie@...nel.org>
Cc: Javier Martinez Canillas <javier@...hile0.org>,
Tomasz Figa <tomasz.figa@...il.com>,
Doug Anderson <dianders@...omium.org>,
Olof Johansson <olof@...om.net>,
Yuvaraj Kumar C D <yuvaraj.cd@...il.com>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] regulator: max77802: set opmode to normal if off is read from hw
Hello Mark,
> On 28/08/2014, at 10:28, Mark Brown <broonie@...nel.org> wrote:
>> Yes, AFAIK the bootloader (none of them because Chromebooks use two
>> chained U-boots) change the regulators default opmode so once is set
>> to OFF on .disable, that value is preserved on warm reboot. This made
>> sense with the Chrome OS kernel since the kernel always set the opmode
>> defined in the "regulator-op-mode" DT property and did not relied on
>> the bootloader to set the most efficient default opmode.
>
> I'm sorry but this is just really unclear. Does the bootloader change
> the mode or does it not change the mode?
I meant that the boot loader *does not* change the mode and is Linux who change it, sorry for the confusion.
Best regards,
Javier--
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