From: Benjamin Tissoires <bentiss@kernel.org>
To: linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
Yauhen Kharuzhy <jekhor@gmail.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
linux-kernel@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH] HID: sensor-hub: Enable hid core report processing for all devices
Date: Fri, 22 Dec 2023 19:27:43 +0100 [thread overview]
Message-ID: <170326966337.2018208.16515231674277786077.b4-ty@kernel.org> (raw)
In-Reply-To: <20231219231503.1506801-1-jekhor@gmail.com>
On Wed, 20 Dec 2023 01:15:03 +0200, Yauhen Kharuzhy wrote:
> After the commit 666cf30a589a ("HID: sensor-hub: Allow multi-function
> sensor devices") hub devices are claimed by hidraw driver in hid_connect().
> This causes stoppping of processing HID reports by hid core due to
> optimization.
>
> In such case, the hid-sensor-custom driver cannot match a known custom
> sensor in hid_sensor_custom_get_known() because it try to check custom
> properties which weren't filled from the report because hid core didn't
> parsed it.
>
> [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git (for-6.8/sensor-hub), thanks!
[1/1] HID: sensor-hub: Enable hid core report processing for all devices
https://git.kernel.org/hid/hid/c/8e2f79f41a5d
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
prev parent reply other threads:[~2023-12-22 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 23:15 Yauhen Kharuzhy
2023-12-20 14:52 ` Jonathan Cameron
2023-12-20 15:04 ` Yauhen Kharuzhy
2023-12-22 12:43 ` srinivas pandruvada
2023-12-22 13:28 ` Benjamin Tissoires
2023-12-22 14:24 ` srinivas pandruvada
2023-12-22 17:16 ` Daniel Thompson
2023-12-22 18:27 ` Benjamin Tissoires [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=170326966337.2018208.16515231674277786077.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=daniel.thompson@linaro.org \
--cc=jekhor@gmail.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®