Eric Lee / smarc-fsl-linux-kernel

24 Jan, 2017

1 commit

  • 1331b62c9   rfkill: remove rfkill-regulator ... Browse Code »

    There are no users of this ("vrfkill") in the tree, so it's just
    dead code - remove it.

    This also isn't really how rfkill is supposed to be used - it's
    intended as a signalling mechanism to/from the device, which the
    driver (and partially cfg80211) will handle - having a separate
    rfkill instance for a regulator is confusing, the driver should
    use the regulator instead to turn off the device when requested.

    Signed-off-by: Johannes Berg

    Johannes Berg
     

24 Feb, 2016

1 commit

13 Aug, 2015

1 commit

  • 36890997b   rfkill: Allow compile test of GPIO consumers if !GPIOLIB ... Browse Code »

    The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
    not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
    functionality only, can still be compiled if GPIOLIB is not enabled.

    Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
    appropriate.

    Signed-off-by: Geert Uytterhoeven
    Acked-by: Linus Walleij
    Signed-off-by: Johannes Berg

    Geert Uytterhoeven
     

28 Oct, 2013

1 commit

20 May, 2011

1 commit

  • 7176ba23f   net: rfkill: add generic gpio rfkill driver ... Browse Code »

    This adds a new generic gpio rfkill driver to support rfkill switches
    which are controlled by gpios. The driver also supports passing in
    data about the clock for the radio, so that when rfkill is blocking,
    it can disable the clock.

    This driver assumes platform data is passed from the board files to
    configure it for specific devices.

    Original-patch-by: Anantha Idapalapati
    Signed-off-by: Rhyland Klein
    Signed-off-by: John W. Linville

    Rhyland Klein
     

20 Apr, 2011

1 commit

  • cbc6a6ed0   rfkill: Regulator consumer driver for rfkill ... Browse Code »

    Add a regulator consumer driver for rfkill to enable controlling radio
    transmitters connected to voltage regulators using the regulator
    framework.

    A new "vrfkill" virtual supply is provided to use in platform code.

    Signed-off-by: Guiming Zhuo
    Signed-off-by: Antonio Ospite
    Reviewed-by: Johannes Berg
    Signed-off-by: John W. Linville

    Antonio Ospite
     

21 Jan, 2011

1 commit

  • 6a108a14f   kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT ... Browse Code »

    The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
    is used to configure any non-standard kernel with a much larger scope than
    only small devices.

    This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
    references to the option throughout the kernel. A new CONFIG_EMBEDDED
    option is added that automatically selects CONFIG_EXPERT when enabled and
    can be used in the future to isolate options that should only be
    considered for embedded systems (RISC architectures, SLOB, etc).

    Calling the option "EXPERT" more accurately represents its intention: only
    expert users who understand the impact of the configuration changes they
    are making should enable it.

    Reviewed-by: Ingo Molnar
    Acked-by: David Woodhouse
    Signed-off-by: David Rientjes
    Cc: Greg KH
    Cc: "David S. Miller"
    Cc: Jens Axboe
    Cc: Arnd Bergmann
    Cc: Robin Holt
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Rientjes
     

11 Jun, 2009

1 commit

  • b91d0e364   rfkill: remove input Kconfig ... Browse Code »

    Now that we added the ioctl, there's no need to ask
    the user to configure this. We will keep it enabled
    for now, and eventually swap the default to n. Also
    let embedded users select it only if they need it.

    Signed-off-by: Johannes Berg
    Signed-off-by: John W. Linville

    Johannes Berg
     

04 Jun, 2009

2 commits

  • c64fb0162   rfkill: create useful userspace interface ... Browse Code »

    The new code added by this patch will make rfkill create
    a misc character device /dev/rfkill that userspace can use
    to control rfkill soft blocks and get status of devices as
    well as events when the status changes.

    Using it is very simple -- when you open it you can read
    a number of times to get the initial state, and every
    further read blocks (you can poll) on getting the next
    event from the kernel. The same structure you read is
    also used when writing to it to change the soft block of
    a given device, all devices of a given type, or all
    devices.

    This also makes CONFIG_RFKILL_INPUT selectable again in
    order to be able to test without it present since its
    functionality can now be replaced by userspace entirely
    and distros and users may not want the input part of
    rfkill interfering with their userspace code. We will
    also write a userspace daemon to handle all that and
    consequently add the input code to the feature removal
    schedule.

    In order to have rfkilld support both kernels with and
    without CONFIG_RFKILL_INPUT (or new kernels after its
    eventual removal) we also add an ioctl (that only exists
    if rfkill-input is present) to disable rfkill-input.
    It is not very efficient, but at least gives the correct
    behaviour in all cases.

    Signed-off-by: Johannes Berg
    Acked-by: Marcel Holtmann
    Signed-off-by: John W. Linville

    Johannes Berg
     
  • 19d337dff   rfkill: rewrite ... Browse Code »

    This patch completely rewrites the rfkill core to address
    the following deficiencies:

    * all rfkill drivers need to implement polling where necessary
    rather than having one central implementation

    * updating the rfkill state cannot be done from arbitrary
    contexts, forcing drivers to use schedule_work and requiring
    lots of code

    * rfkill drivers need to keep track of soft/hard blocked
    internally -- the core should do this

    * the rfkill API has many unexpected quirks, for example being
    asymmetric wrt. alloc/free and register/unregister

    * rfkill can call back into a driver from within a function the
    driver called -- this is prone to deadlocks and generally
    should be avoided

    * rfkill-input pointlessly is a separate module

    * drivers need to #ifdef rfkill functions (unless they want to
    depend on or select RFKILL) -- rfkill should provide inlines
    that do nothing if it isn't compiled in

    * the rfkill structure is not opaque -- drivers need to initialise
    it correctly (lots of sanity checking code required) -- instead
    force drivers to pass the right variables to rfkill_alloc()

    * the documentation is hard to read because it always assumes the
    reader is completely clueless and contains way TOO MANY CAPS

    * the rfkill code needlessly uses a lot of locks and atomic
    operations in locked sections

    * fix LED trigger to actually change the LED when the radio state
    changes -- this wasn't done before

    Tested-by: Alan Jenkins
    Signed-off-by: Henrique de Moraes Holschuh [thinkpad]
    Signed-off-by: Johannes Berg
    Signed-off-by: John W. Linville

    Johannes Berg
     

11 Oct, 2007

2 commits

  • 135900c18   [RFKILL]: Add support for an rfkill LED. ... Browse Code »

    This adds a LED trigger.

    Signed-off-by: Michael Buesch
    Acked-by: Ivo van Doorn
    Signed-off-by: John W. Linville
    Signed-off-by: David S. Miller

    Michael Buesch
     
  • 234a0ca6f   [RFKILL]: Remove IRDA ... Browse Code »

    As Dmitry pointed out earlier, rfkill-input.c
    doesn't support irda because there are no users
    and we shouldn't add unrequired KEY_ defines.

    However, RFKILL_TYPE_IRDA was defined in the
    rfkill.h header file and would confuse people
    about whether it is implemented or not.

    This patch removes IRDA support completely,
    so it can be added whenever a driver wants the
    feature.

    Signed-off-by: Ivo van Doorn
    Signed-off-by: David S. Miller

    Ivo van Doorn
     

07 May, 2007

1 commit