Thread (10 messages) 10 messages, 4 authors, 2016-02-23

Re: [PATCHv2 3/4] ARM: tegra: use build-in device properties with rfkill_gpio

From: Marc Dietrich <marvin24@gmx.de>
Date: 2016-02-23 10:39:13
Also in: linux-tegra, linux-wireless, lkml

Possibly related (same subject, not in this thread)

Am Dienstag, 23. Februar 2016, 11:31:40 CET schrieb Arnd Bergmann:
On Tuesday 23 February 2016 11:15:31 Arnd Bergmann wrote:
quoted
On Thursday 18 February 2016 21:04:49 Johannes Berg wrote:
quoted
On Tue, 2016-01-26 at 09:42 +0100, Johannes Berg wrote:
Just for my curiosity: what is the difference between a rfkill-gpio
device and a gpio-keys device with a KEY_RFKILL code?

arch/arm/boot/dts/bcm4708-netgear-r6250.dts and others seem to
do the second approach in DT so they don't need to create the
platform device.
I found the answer now (after discussing on IRC): just
for reference: KEY_RFKILL is for sending the event to the kernel
when a user presses the gpio butting, this rfkill-gpio turns
the devices on or off when after an RFKILL event is received.
yes, paz00 has no hw key. rfkill is triggered via software (rfkill) only. The 
problem in the past was how to describe such a device in the device tree. 

Strictly speaking, there is no rfkill device hardware (just an interface). The 
only hardware that exists is in our case is connected to a hard wired usb bus 
(wifi dongle), which makes it complicated to attach a DT property or subdevice 
to it. And a standalone device-tree entry for a non hardware device was 
rejected in the past.

Marc

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help