[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13413437.Ipf2eOczfj@diego>
Date: Wed, 27 Apr 2016 15:56:56 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Mark Brown <broonie@...nel.org>
Cc: Wadim Egorov <w.egorov@...tec.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
Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:
> 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?
I guess
[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3
from yesterday [0] might be the fix? At least it fits Wadim's description above
but I haven't had time to test it yet.
[0] https://patchwork.kernel.org/patch/8939741/
Powered by blists - more mailing lists