Re: Three different LED brightnesses (was Re: PM regression with LED changes in next-20161109)

2016-11-13 Thread Pavel Machek
Hi! > >No, that's just adding more mess on the system. > > > >Here's better proposal: > > > >brightness (write): what we do today. (Mess, but too late to change it) > >(read): -Esomething or what we do today (if someone > >acutally uses it) >

Re: Three different LED brightnesses (was Re: PM regression with LED changes in next-20161109)

2016-11-13 Thread Hans de Goede
Hi, On 13-11-16 10:10, Pavel Machek wrote: On Sat 2016-11-12 09:03:42, Hans de Goede wrote: Hi, On 11-11-16 23:12, Pavel Machek wrote: Hi! Reason #1: Hmm. So userland can read the LED state, and it can get _some_ value back, but it can not know if it is current state or not. That is not

Three different LED brightnesses (was Re: PM regression with LED changes in next-20161109)

2016-11-13 Thread Pavel Machek
On Sat 2016-11-12 09:03:42, Hans de Goede wrote: > Hi, > > On 11-11-16 23:12, Pavel Machek wrote: > >Hi! > > > >Reason #1: > > > Hmm. So userland can read the LED state, and it can get _some_ value > back, but it can not know if it is current state or not. > > That is not correct, the cur