From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Eric Piel <eric.piel@tremplin-utc.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: Driver lis3lv02d_i2c not working on Nokia RX-51
Date: Sun, 24 Mar 2013 15:50:42 +0100 [thread overview]
Message-ID: <201303241550.42801@pali> (raw)
In-Reply-To: <20130217181756.GE1583@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: Text/Plain, Size: 1429 bytes --]
On Sunday 17 February 2013 19:17:59 Mark Brown wrote:
> On Sun, Feb 17, 2013 at 05:40:41PM +0100, Pali Rohár wrote:
> > $ dmesg | grep lis3
> > [ 110.454345] lis3lv02d_i2c 3-001d: Failed to get supply
> > 'Vdd': -517 [ 110.457397] i2c 3-001d: Driver lis3lv02d_i2c
> > requests probe deferral [ 111.507415] lis3lv02d_i2c
> > 3-001d: Failed to get supply 'Vdd': -517 [ 111.510528] i2c
> > 3-001d: Driver lis3lv02d_i2c requests probe deferral [
> > 126.720458] lis3lv02d_i2c 3-001d: Failed to get supply
> > 'Vdd': -517 [ 126.728149] i2c 3-001d: Driver lis3lv02d_i2c
> > requests probe deferral [ 135.842803] lis3lv02d_i2c
> > 3-001d: Failed to get supply 'Vdd': -517 [ 135.856292] i2c
> > 3-001d: Driver lis3lv02d_i2c requests probe deferral
>
> This just looks like a basic error in the board hookup - the
> supplies are not mapped for the device. Add the supply
> mappings and you should be fine. This should have been done
> when the device was added, the commit doing that looks like
> it was never tested in mainline as the driver problem was
> fixed in October 2011 but the RX51 didn't start using the
> device until May 2012.
There is no regulator 'Vdd' supply in board rx51 files. Can you
look at code how it can be fixed?
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/mach-omap2/board-rx51-peripherals.c#n86
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-03-24 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 23:46 Driver lis3lv02d_i2c not working on Nokia RX-51 Pali Rohár
2013-02-17 16:25 ` Mark Brown
2013-02-17 16:40 ` Pali Rohár
2013-02-17 18:17 ` Mark Brown
2013-03-24 14:50 ` Pali Rohár [this message]
2013-03-24 21:21 ` Mark Brown
2013-03-24 21:27 ` Pali Rohár
2013-03-24 22:14 ` Mark Brown
2013-03-24 22:44 ` Pali Rohár
2013-03-24 23:04 ` Mark Brown
2013-03-26 15:02 ` Pali Rohár
2013-03-26 15:44 ` Mark Brown
2013-03-26 16:08 ` Linus Torvalds
2013-03-26 17:08 ` Mark Brown
2013-03-26 20:53 ` Aaro Koskinen
2013-03-26 21:19 ` Mark Brown
2013-03-28 14:11 ` Pali Rohár
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=201303241550.42801@pali \
--to=pali.rohar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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