On Tue 2016-02-23 21:55:14, Johannes Berg wrote:
> On Tue, 2016-02-23 at 21:45 +0100, Pavel Machek wrote:
>
> > So... you add LED trigger to display the state of the airplane
> > mode. Ok, why not.
>
> Yes. However, consider that "the airplane mode" isn't a well-defined
> concept; some systems
On Tue, 2016-02-23 at 21:45 +0100, Pavel Machek wrote:
> So... you add LED trigger to display the state of the airplane
> mode. Ok, why not.
Yes. However, consider that "the airplane mode" isn't a well-defined
concept; some systems may want to light up that LED even when wifi is
still enabled,
On Tuesday 23 February 2016 01:43 AM, Alban wrote:
On Mon, 22 Feb 2016 19:37:59 +0530
Laxman Dewangan wrote:
Use devm_gpiochip_add_data() for GPIO registration.
Signed-off-by: Laxman Dewangan
Cc: Alban Bedel
---
Hi Jon,
The patch was based on linux-next ( next-20160222 ).
Masanari
On Mon, Feb 22, 2016 at 10:22 PM, Jonathan Corbet wrote:
> On Mon, 22 Feb 2016 20:41:54 +0900
> Masanari Iida wrote:
>
>> -use the memory controllers RCW, thought non-MX controlers
On 02/22/2016 03:07 PM, Laxman Dewangan wrote:
Use devm_gpiochip_add_data() for GPIO registration and remove the
call for gpiochip_remove() from remove callback.
Signed-off-by: Laxman Dewangan
Acked-by: Michael Hennerich
Cc: Michael
On Monday 22 February 2016 08:14 PM, Linus Walleij wrote:
On Mon, Feb 22, 2016 at 3:07 PM, Laxman Dewangan wrote:
Add resource management APIs for gpiochip_add_data() and
gpiochip_remove() and use these APIs from different HW drivers.
This is based on discussion on