public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>, Maciej Purski <m.purski@samsung.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Regulator regression in next-20180305
Date: Mon, 5 Mar 2018 15:12:46 -0800	[thread overview]
Message-ID: <20180305231246.GB5799@atomide.com> (raw)

Hi Mark and Maciej,

Looks like with next-20180305 there's a regulator regression
where mmc0 won't show any cards or produces errors:

mmcblk0: error -110 requesting status
mmc1: new high speed SDIO card at address 0001
mmcblk0: error -110 requesting status
mmcblk0: recovery failed!
print_req_error: I/O error, dev mmcblk0, sector 0
Buffer I/O error on dev mmcblk0, logical block 0, async page read
mmcblk0: error -110 requesting status
mmcblk0: recovery failed!

I bisected it down to the following commits:

broken		71c33626a802 ("regulator: core: Change voltage setting path")
fails to build	a7348f502ab7 ("regulator: core: Add voltage balancing mechanism")
works		cf6fc8064766 ("regulator: core: Resolve coupled regulators")

Any ideas?

Regards,

Tony

             reply	other threads:[~2018-03-05 23:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 23:12 Tony Lindgren [this message]
2018-03-05 23:22 ` Regulator regression in next-20180305 Fabio Estevam
2018-03-06 16:30   ` Mark Brown
2018-03-06 16:56     ` Fabio Estevam
2018-03-06 17:18       ` Tony Lindgren
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 14:45               ` Mark Brown
2018-03-07 12:57     ` Maciej Purski
2018-03-07 14:10       ` Mark Brown
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=20180305231246.GB5799@atomide.com \
    --to=tony@atomide.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m.purski@samsung.com \
    /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