[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5720C750.3050104@phytec.de>
Date: Wed, 27 Apr 2016 16:06:08 +0200
From: Wadim Egorov <w.egorov@...tec.de>
To: Mark Brown <broonie@...nel.org>
Cc: Heiko Stübner <heiko@...ech.de>,
linux-rockchip@...ts.infradead.org, mark.rutland@....com,
devicetree@...r.kernel.org, a.zummo@...ertech.it,
pawel.moll@....com, rtc-linux@...glegroups.com,
ijc+devicetree@...lion.org.uk, mturquette@...libre.com,
sboyd@...eaurora.org, linux-kernel@...r.kernel.org,
robh+dt@...nel.org, lgirdwood@...il.com,
alexandre.belloni@...e-electrons.com, dianders@...omium.org,
galak@...eaurora.org, zyw@...k-chips.com, lee.jones@...aro.org,
linux-clk@...r.kernel.org
Subject: Re: Applied "regulator: rk808: remove linear range definitions with a
single range" to the regulator tree
On 27.04.2016 15:50, Mark Brown wrote:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
>> On 26.04.2016 21:33, Heiko Stübner wrote:
>>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
>>> rk3288-veyron devices with the bug below. Reverting this one patch
>>> results in the system booting again:
>> This is because I missed to add the correct ops for LDO_REG3 in this patch.
> Any ETA on a fix or should I revert?
this patch
http://lists.infradead.org/pipermail/linux-rockchip/2016-April/008674.html
will fix the issue.
The regulator patches from v4 are based on top of
commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808_reg_ops_ranges")
Powered by blists - more mailing lists