Re: best way to handle LEDs

[Pavel Machek <pavel@suse.cz>]

Hi!

> > > > yellow off: 	not charging
> > > > yellow on:	charging
> > > > yellow fast blink: charge error
> > > > 
> > > > I think even slow blinking was used somewhere. I have some code from
> > > > John Lenz (attached); it uses sysfs interface, exports led collor, and
> > > > allows setting different frequencies.
> > > > 
> > > > Is that acceptable, or should some other interface be used?
> > > 
> > > IMHO reducing digital outputs to LEDs goes not far enough. All System-
> > > on-Chip CPUs have General Purpose I/O pins today, which can act as
> > > inputs or outputs and may be used for LEDs, matrix keyboard lines,
> > 
> > We have some leds that are *not* on GPIO pins (like driven by
> > ACPI). We'd like to support those, too.
> 
> I though ACPI was software? These LEDs have to be driven by some hardware,
> right?

Right, but you don't know by *which* hardware. Only ACPI AML code knows.
So from linux POW, they are handled by ACPI.

It may even trap to SMM BIOS.
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/