lkml.org 
[lkml]   [2013]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v3 1/6] ARM: tegra: add gpiod_lookup table for paz00
    On Thu, Nov 28, 2013 at 01:54:10PM +0100, Marc Dietrich wrote:
    [...]
    > Yes, rfkill is just an interface for userspace to able to control the gpio.
    > E.g. backlight of medcom-wide seems to be related to the pwm controller, but
    > is not a subnode of it. Instead it is a device of its own without parent.
    > Hence, we may include rfkill in a similar, "free-standing" node. But this
    > approch was rejected in the past. Maybe this changed now.

    Indeed. I think we really do need ways to represent this kind of device.
    If we can't then how are we supposed to get rid of board files?

    > Thinking a bit more about it, rfkill is neither a hw block nor a function of
    > the wifi driver, so I guess it cannot be added to the usb controller (or a usb
    > device).

    I guess it depends a bit. Some rfkill-type devices may control more than
    just WiFi (bluetooth, NFC, ...). If it really only controls WiFi, I
    think it would still be reasonable to represent it as a child of the
    WiFi device. It is, after all, a mechanism to control the WiFi hardware.

    Alternatively I suppose we wouldn't really need to have an explicit
    node. The WiFi driver could simply instantiate an rfkill device based on
    its own properties.

    Thierry
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2013-11-29 12:21    [W:2.266 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site