[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180306171819.GF5796@atomide.com>
Date: Tue, 6 Mar 2018 09:18:19 -0800
From: Tony Lindgren <tony@...mide.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Maciej Purski <m.purski@...sung.com>,
linux-omap@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Regulator regression in next-20180305
* Fabio Estevam <festevam@...il.com> [180306 16:57]:
> Hi Mark,
>
> On Tue, Mar 6, 2018 at 1:30 PM, Mark Brown <broonie@...nel.org> wrote:
>
> > diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> > index e685f8b94acf..2c5b20a97f51 100644
> > --- a/drivers/regulator/core.c
> > +++ b/drivers/regulator/core.c
> > @@ -159,7 +159,7 @@ static void regulator_lock_supply(struct regulator_dev *rdev)
> > {
> > int i;
> >
> > - for (i = 0; rdev; rdev = rdev_get_supply(rdev), i++)
> > + for (i = 1000; rdev; rdev = rdev_get_supply(rdev), i++)
> > mutex_lock_nested(&rdev->mutex, i);
>
> With this change the log is a bit different, but still get a kernel hang:
> https://pastebin.com/eF08TnuT
That patch does not seem to change anything for me. The errors
I posted yesterday for mmc0 only happen on duovero, other omap
variants just fail silently with no cards showing.
Regards,
Tony
Powered by blists - more mailing lists