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.ro...@gmail.com

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to