From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko =?ISO-8859-1?Q?St=FCbner?= Subject: Re: Applied "regulator: rk808: remove linear range definitions with a single range" to the regulator tree Date: Wed, 27 Apr 2016 15:56:56 +0200 Message-ID: <13413437.Ipf2eOczfj@diego> References: <57205DC2.7070506@phytec.de> <20160427135048.GQ3217@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20160427135048.GQ3217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Mark Brown Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org, a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org, dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, pawel.moll-5wv7dgnIgG8@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org, ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org, sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org, galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org, Wadim Egorov , lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org 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=FCbner 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 a= bove = but I haven't had time to test it yet. [0] https://patchwork.kernel.org/patch/8939741/