From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Zijlstra <peterz@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: quirks: ignore non-functional sensor in HP 5MP Camera
Date: Wed, 15 Jan 2025 05:15:07 -0800 [thread overview]
Message-ID: <3135248fcbf284e19a2ffd3ab01767709e322980.camel@linux.intel.com> (raw)
In-Reply-To: <20250115070020.2777721-1-acelan.kao@canonical.com>
One minor comment:
"HID: quirks: ignore non-functional sensor in HP 5MP Camera"
For this
The format is not same as other commits in this file. There is no
"quirks". But not sure if Jiri cares.
On Wed, 2025-01-15 at 15:00 +0800, Chia-Lin Kao (AceLan) wrote:
> The HP 5MP Camera (USB ID 0408:5473)
> reports a HID sensor interface that
> is not actually implemented. Attempting to access this non-functional
> sensor via iio_info causes system hangs as runtime PM tries to wake
> up
> an unresponsive sensor.
>
> [453] hid-sensor-hub 0003:0408:5473.0003: Report latency
> attributes: ffffffff:ffffffff
> [453] hid-sensor-hub 0003:0408:5473.0003: common attributes: 5:1,
> 2:1, 3:1 ffffffff:ffffffff
>
> Add this device to the HID ignore list since the sensor interface is
> non-functional by design and should not be exposed to userspace.
>
> Signed-off-by: Chia-Lin Kao (AceLan) <acelan.kao@canonical.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/hid/hid-ids.h | 1 +
> drivers/hid/hid-quirks.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> index 1f47fda809b9..c5b57e857e77 100644
> --- a/drivers/hid/hid-ids.h
> +++ b/drivers/hid/hid-ids.h
> @@ -1094,6 +1094,7 @@
> #define
> USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3001 0x3001
> #define
> USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3003 0x3003
> #define
> USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3008 0x3008
> +#define
> USB_DEVICE_ID_QUANTA_HP_5MP_CAMERA_5473 0x5473
>
> #define I2C_VENDOR_ID_RAYDIUM 0x2386
> #define I2C_PRODUCT_ID_RAYDIUM_4B33 0x4b33
> diff --git a/drivers/hid/hid-quirks.c b/drivers/hid/hid-quirks.c
> index e0bbf0c6345d..5d7a418ccdbe 100644
> --- a/drivers/hid/hid-quirks.c
> +++ b/drivers/hid/hid-quirks.c
> @@ -891,6 +891,7 @@ static const struct hid_device_id
> hid_ignore_list[] = {
> { HID_USB_DEVICE(USB_VENDOR_ID_SYNAPTICS,
> USB_DEVICE_ID_SYNAPTICS_DPAD) },
> #endif
> { HID_USB_DEVICE(USB_VENDOR_ID_YEALINK,
> USB_DEVICE_ID_YEALINK_P1K_P4K_B2K) },
> + { HID_USB_DEVICE(USB_VENDOR_ID_QUANTA,
> USB_DEVICE_ID_QUANTA_HP_5MP_CAMERA_5473) },
> { }
> };
>
next prev parent reply other threads:[~2025-01-15 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:00 [PATCH] HID: quirks: ignore non-functional sensor in HP 5MP Camera Chia-Lin Kao (AceLan)
2025-01-15 13:15 ` srinivas pandruvada [this message]
2025-02-03 10:16 ` Jiri Kosina
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=3135248fcbf284e19a2ffd3ab01767709e322980.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=acelan.kao@canonical.com \
--cc=bentiss@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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