From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Regulator regression in next-20180305
Date: Tue, 6 Mar 2018 09:18:19 -0800 [thread overview]
Message-ID: <20180306171819.GF5796@atomide.com> (raw)
In-Reply-To: <CAOMZO5DL_a8DOKgyZ4j2-bcPZLeUtQ9ekc74yVwtKYofbpOafg@mail.gmail.com>
* Fabio Estevam <festevam@gmail.com> [180306 16:57]:
> Hi Mark,
>
> On Tue, Mar 6, 2018 at 1:30 PM, Mark Brown <broonie@kernel.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
next prev parent reply other threads:[~2018-03-06 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 23:12 Regulator regression in next-20180305 Tony Lindgren
2018-03-05 23:22 ` Fabio Estevam
2018-03-06 16:30 ` Mark Brown
2018-03-06 16:56 ` Fabio Estevam
2018-03-06 17:18 ` Tony Lindgren [this message]
2018-03-06 19:12 ` Mark Brown
2018-03-06 20:06 ` Fabio Estevam
2018-03-06 21:33 ` Mark Brown
2018-03-06 22:10 ` Fabio Estevam
2018-03-07 12:57 ` Maciej Purski
[not found] ` <20180307141027.GD7290@sirena.org.uk>
2018-03-07 14:37 ` Maciej Purski
2018-03-07 15:17 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180306171819.GF5796@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).