From: Alan Stern <stern@rowland.harvard.edu>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"Filipe Laíns" <lains@riseup.net>,
"Nestor Lopez Casado" <nlopezcasad@logitech.com>
Subject: Re: [PATCH v3 4/6] USB: core: Add wireless_status sysfs attribute
Date: Thu, 2 Mar 2023 10:27:38 -0500 [thread overview]
Message-ID: <ZADAamF1S7OrwRIO@rowland.harvard.edu> (raw)
In-Reply-To: <20230302105555.51417-4-hadess@hadess.net>
On Thu, Mar 02, 2023 at 11:55:53AM +0100, Bastien Nocera wrote:
> Add a wireless_status sysfs attribute to USB devices to keep track of
> whether a USB device that's comprised of a receiver dongle and an emitter
> device over a, most of the time proprietary, wireless link has its emitter
> connected or disconnected.
>
> This will be used by user-space OS components to determine whether the
> battery-powered part of the device is wirelessly connected or not,
> allowing, for example:
> - upower to hide the battery for devices where the device is turned off
> but the receiver plugged in, rather than showing 0%, or other values
> that could be confusing to users
> - Pipewire to hide a headset from the list of possible inputs or outputs
> or route audio appropriately if the headset is suddenly turned off, or
> turned on
> - libinput to determine whether a keyboard or mouse is present when its
> receiver is plugged in.
>
> This is done at the USB interface level as:
> - the interface on which the wireless status is detected is sometimes
> not the same as where it could be consumed (eg. the audio interface
> on a headset dongle will still appear even if the headset is turned
> off), and we cannot have synchronisation of status across subsystems.
> - this behaviour is not specific to HID devices, even if the protocols
> used to determine whether or not the remote device is connected can
> be HID.
>
> This is not an attribute that is meant to replace protocol specific
> APIs, such as the ones available for WWAN, WLAN/Wi-Fi, or Bluetooth
> or any other sort of networking, but solely for wireless devices with
> an ad-hoc “lose it and your device is e-waste” receiver dongle.
>
> The USB interface will only be exporting the wireless_status sysfs
> attribute if it gets set through the API exported in the next commit.
>
> Signed-off-by: Bastien Nocera <hadess@hadess.net>
> ---
For parts 4 and 5:
Acked-by: Alan Stern <stern@rowland.harvard.edu>
next prev parent reply other threads:[~2023-03-02 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 10:55 [PATCH v3 1/6] HID: logitech-hidpp: Simplify array length check Bastien Nocera
2023-03-02 10:55 ` [PATCH v3 2/6] HID: logitech-hidpp: Add support for ADC measurement feature Bastien Nocera
2023-03-02 10:55 ` [PATCH v3 3/6] HID: logitech-hidpp: Add Logitech G935 headset Bastien Nocera
2023-03-02 10:55 ` [PATCH v3 4/6] USB: core: Add wireless_status sysfs attribute Bastien Nocera
2023-03-02 15:27 ` Alan Stern [this message]
2023-03-09 14:17 ` Greg Kroah-Hartman
2023-03-02 10:55 ` [PATCH v3 5/6] USB: core: Add API to change the wireless_status Bastien Nocera
2023-03-09 14:17 ` Greg Kroah-Hartman
2023-03-02 10:55 ` [PATCH v3 6/6] HID: logitech-hidpp: Set wireless_status for G935 receiver Bastien Nocera
2023-03-09 14:18 ` [PATCH v3 1/6] HID: logitech-hidpp: Simplify array length check Greg Kroah-Hartman
2023-04-03 13:33 ` Benjamin Tissoires
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=ZADAamF1S7OrwRIO@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nlopezcasad@logitech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.