From: Tony Lindgren <tony@atomide.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
linux-mmc@vger.kernel.org
Subject: Re: 4.3-rc1 omap3 mmc boot warning + errors
Date: Mon, 14 Sep 2015 13:29:03 -0700 [thread overview]
Message-ID: <20150914202903.GB10928@atomide.com> (raw)
In-Reply-To: <CAAfyv355JBGRv7V7cdV=pxrodm--e2+d0sLw6kW2vnp2vmgG8Q@mail.gmail.com>
* Belisko Marek <marek.belisko@gmail.com> [150914 13:25]:
> On Mon, Sep 14, 2015 at 10:15 PM, Belisko Marek <marek.belisko@gmail.com> wrote:
> >
> > after upgrading to 4.3-rc gta04 board during boot print following warning:
...
> >
> > after reverting mmc: host: omap_hsmmc: enable/disable vmmc_aux
> > regulator based on previous state
> > (3f77f702389b7fbc955ec95721ce3861e40697fc) warning is gone and rootfs
> > is mounted properly:
> Sorry wrong reference. Correct should be: mmc: host: omap_hsmmc: use
> regulator_is_enabled to find pbias status
> (c55d7a0553643a7e8f120688b82b594471084d3c)
...
> >
> > Any idea what could cause this problems? On 4.2 it works fine. Many thanks.
Yeh a known issue :( We're waiting for several fixes to get merged:
In the arm-soc tree:
fe8291e82b5d ("ARM: OMAP2+: omap-device: fix race deferred probe of
omap_hsmmc vs omap_device_late_init")
In Linux next via regulator tree:
b9c93646fd5c ("regulator: pbias: program pbias register offset in
pbias driver")
About to get queued by me:
8b1bf295273d ("ARM: dts: Use ti,pbias compatible string for pbias")
And when when the above hits mainline, I still need to queue
the "fix address translation for pbias" patch as it depends on
the regulator.c changes.
So it will be few more days, sorry.
Regards,
Tony
prev parent reply other threads:[~2015-09-14 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 20:15 4.3-rc1 omap3 mmc boot warning + errors Belisko Marek
2015-09-14 20:21 ` Belisko Marek
2015-09-14 20:29 ` Tony Lindgren [this message]
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=20150914202903.GB10928@atomide.com \
--to=tony@atomide.com \
--cc=hns@goldelico.com \
--cc=kishon@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=ulf.hansson@linaro.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).