From: Szymon Janc <szymon.janc@codecoup.pl>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] input/hog: Remove HID device after HoG device disconnects
Date: Mon, 15 Jul 2019 14:51:44 +0200 [thread overview]
Message-ID: <1623552.bYGA88Ch3a@ix> (raw)
In-Reply-To: <20190614153125.2605-1-hadess@hadess.net>
Hi,
On Friday, 14 June 2019 17:31:25 CEST Bastien Nocera wrote:
> From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>
> When the Bluetooth LE device disconnects, make sure to also destroy the
> uHID device so that we don't have a lingering HID device accessible from
> user-space.
>
> This also fixes the input subsystem never seeing the device reattaching,
> causing settings that should be applied on connection not to be applied.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=202909
>
> Tested-by: Bastien Nocera <hadess@hadess.net>
> ---
> profiles/input/hog.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/profiles/input/hog.c b/profiles/input/hog.c
> index 23c9c1529..83c017dcb 100644
> --- a/profiles/input/hog.c
> +++ b/profiles/input/hog.c
> @@ -199,6 +199,8 @@ static int hog_disconnect(struct btd_service *service)
> struct hog_device *dev = btd_service_get_user_data(service);
>
> bt_hog_detach(dev->hog);
> + bt_hog_unref(dev->hog);
> + dev->hog = NULL;
>
> btd_service_disconnecting_complete(service, 0);
I've tested this with device I have and introduced delay is acceptable imho.
Since this fix end-user usabiblity for some of the devices on the market I
think the trade-off is justified.
Patch is now applied.
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2019-07-15 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 15:31 [PATCH] input/hog: Remove HID device after HoG device disconnects Bastien Nocera
2019-07-15 12:51 ` Szymon Janc [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=1623552.bYGA88Ch3a@ix \
--to=szymon.janc@codecoup.pl \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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).