RE: leds-gpio broken with current git?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of David Brownell
> Sent: Thursday, January 15, 2009 9:59 AM
> To: Koen Kooi
> Cc: linux-omap@xxxxxxxxxxxxxxx List
> Subject: Re: leds-gpio broken with current git?
> 
> On Thursday 15 January 2009, Koen Kooi wrote:
> > I've been playing with different kernels on beagleboard lately and
> it
> > seems that somewhere between 2.6.28rc8 and the final release leds-
> gpio
> > got broken for beagleboard:
> >
> > Registered led device: beagleboard::usr0
> > Registered led device: beagleboard::usr1
> > leds-gpio: probe of leds-gpio failed with error -22
> 
> Works for me, no "-EINVAL", on 2.6.28-omap1 and no patches
> that should affect GPIOs or LEDs.  Last patch applied to
> GIT is 15f75b6226c2d3b82062bb721e7cb9a1d6f35efd (musbhsdma).
> 
> OK, I'm just pulling a new batch of objects, I'm guessing
> Tony snuck in RC1 already ... yes, I see he just sent a
> post about that a few minutes ago.  ;)

Perhaps something broke with Tony's RC1 merge?  The LEDs are broken for me as well.

> 
> - Dave
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap"
> in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux