[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1453234505.23600.6.camel@sipsolutions.net>
Date: Tue, 19 Jan 2016 21:15:05 +0100
From: Johannes Berg <johannes@...solutions.net>
To: João Paulo Rechi Vita <jprvita@...il.com>
Cc: marcel@...tmann.org, linux-wireless@...r.kernel.org,
davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, jprvita@...lessm.com,
linux@...lessm.com
Subject: Re: [PATCH 5/8] rfkill: Remove obsolete "state" sysfs interface
On Tue, 2016-01-19 at 10:42 -0500, João Paulo Rechi Vita wrote:
> This was schedule to be removed in 2014 by:
> -For details to this subsystem look at Documentation/rfkill.txt.
> -
> -What: /sys/class/rfkill/rfkill[0-9]+/state
> -Date: 09-Jul-2007
> -KernelVersion v2.6.22
> -Contact: linux-wireless@...r.kernel.org
> -Description: Current state of the transmitter.
> - This file is deprecated and scheduled to be removed
> in 2014,
> - because its not possible to express the 'soft and
> hard block'
> - state of the rfkill driver.
> -Values: A numeric value.
> - 0: RFKILL_STATE_SOFT_BLOCKED
> - transmitter is turned off by software
> - 1: RFKILL_STATE_UNBLOCKED
> - transmitter is (potentially) active
> - 2: RFKILL_STATE_HARD_BLOCKED
> - transmitter is forced off by something
> outside of
> - the driver's control.
I suspect that nevertheless, we can't just remove it - Googling around
shows quite a bit of (e.g. Android) code using it.
johannes
Powered by blists - more mailing lists