From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mark Pearson <markpearson@lenovo.com>,
Bastien Nocera <hadess@hadess.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, Mark Pearson <mpearson@lenovo.com>
Subject: Re: [PATCH v2 1/2] iio: documentation: Document proximity sensor label use
Date: Thu, 18 Feb 2021 13:31:09 +0000 [thread overview]
Message-ID: <20210218133109.608b4ee7@archlinux> (raw)
In-Reply-To: <20210215191003.698888-1-hdegoede@redhat.com>
On Mon, 15 Feb 2021 20:10:02 +0100
Hans de Goede <hdegoede@redhat.com> wrote:
> Add an entry to Documentation/ABI/testing/sysfs-bus-iio for
> the new device label sysfs-attribute support.
>
> And document the standardized labels which may be used with proximity
> sensors to hint userspace about the intended use of the sensor.
>
> Using labels to differentiate between the multiple proximity sensors
> which a modern laptop/tablet may have was discussed in this thread:
> https://lore.kernel.org/linux-iio/9f9b0ff6-3bf1-63c4-eb36-901cecd7c4d9@redhat.com/
>
> As mentioned there the "proximity-wifi*" labels are already being used
> in this manner on some chromebooks, see e.g.:
> arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
> arch/arm64/boot/dts/qcom/sc7180-trogdor-lte-sku.dtsi
>
> And the "proximity-palmrest" and "proximity-lap" labels are intended
> to be used with the lap and palmrest sensors found in recent Lenovo
> ThinkPad models.
>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Mark Pearson <mpearson@lenovo.com>
> Cc: Bastien Nocera <hadess@hadess.net>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Great thanks.
Series applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to ignore.
Jonathan
> ---
> Changes in v2:
> - Drop the too generic:
> What: /sys/bus/iio/devices/iio:deviceX/in_*_label
> What: /sys/bus/iio/devices/iio:deviceX/out_*_label
> lines from the newly added documentation, if/when we start
> using channel-labels with proximity sensors then those should
> get a separate in_proximityX_label documentation.
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 39 +++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 35289d47d6cb..364f842350ab 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -33,6 +33,45 @@ Description:
> Description of the physical chip / device for device X.
> Typically a part number.
>
> +What: /sys/bus/iio/devices/iio:deviceX/label
> +KernelVersion: 5.8
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Optional symbolic label for a device.
> + This is useful for userspace to be able to better identify an
> + individual device.
> +
> + The contents of the label are free-form, but there are some
> + standardized uses:
> +
> + For proximity sensors which give the proximity (of a person) to
> + a certain wlan or wwan antenna the following standardized labels
> + are used:
> +
> + * "proximity-wifi"
> + * "proximity-lte"
> + * "proximity-wifi-lte"
> + * "proximity-wifi-left"
> + * "proximity-wifi-right"
> +
> + These are used to indicate to userspace that these proximity
> + sensors may be used to tune transmit power to ensure that
> + Specific Absorption Rate (SAR) limits are honored.
> + The "-left" and "-right" labels are for devices with multiple
> + antennas.
> +
> + In some laptops/tablets the standardized proximity sensor labels
> + instead indicate proximity to a specific part of the device:
> +
> + * "proximity-palmrest" indicates proximity to the keyboard's palmrest
> + * "proximity-palmrest-left" indicates proximity to the left part of the palmrest
> + * "proximity-palmrest-right" indicates proximity to the right part of the palmrest
> + * "proximity-lap" indicates the device is being used on someone's lap
> +
> + Note "proximity-lap" is special in that its value may be
> + calculated by firmware from other sensor readings, rather then
> + being a raw sensor reading.
> +
> What: /sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
> KernelVersion: 4.5
> Contact: linux-iio@vger.kernel.org
prev parent reply other threads:[~2021-02-18 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:10 [PATCH v2 1/2] iio: documentation: Document proximity sensor label use Hans de Goede
2021-02-15 19:10 ` [PATCH v2 2/2] iio: documentation: Document accelerometer " Hans de Goede
2021-02-18 13:31 ` Jonathan Cameron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210218133109.608b4ee7@archlinux \
--to=jic23@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=markpearson@lenovo.com \
--cc=mpearson@lenovo.com \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).