From: Mark Brown <broonie@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>,
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
Lee Jones <lee.jones@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Tegra boots failing due to as3722 I/O errors
Date: Tue, 29 Mar 2016 12:03:19 -0700 [thread overview]
Message-ID: <20160329190319.GE2350@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Hi,
Currently the Jetson TK1 is failing to get regulators for MMC with at
least my regulator tree and probably -next also due to:
[ 1.665750] as3722 4-0040: AS3722 with revision 0x1 found
[ 1.682945] +VDDIO_SDMMC3: failed to get the current voltage(-22)
[ 1.689135] as3722-regulator as3722-regulator: regulator 13 register failed -22
[ 1.697593] as3722-regulator: probe of as3722-regulator failed with error -22
The get voltage operation here is just a simple mapping of a bitfield in
the regmap which suggests that the underlying problem is somewhere
further down the stack like the MFD or I2C drivers. The error is
-EINVAL which suggests something like the register not being marked as
readable but the _VOLTAGE_REG registers appear to be marked as readable
in the MFD.
Full log for one boot at:
https://storage.kernelci.org/broonie-regulator/v4.6-rc1-24-ga7e614dd1f91/arm-multi_v7_defconfig+CONFIG_SMP=n/lab-mhart/boot-tegra124-jetson-tk1.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-03-29 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 19:03 Mark Brown [this message]
2016-03-30 11:31 ` Jon Hunter
2016-03-30 13:15 ` Jon Hunter
2016-03-30 16:46 ` Mark Brown
2016-03-31 14:45 ` Jon Hunter
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=20160329190319.GE2350@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gnurou@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®