From: Jiri Kosina <jikos@kernel.org>
To: Aditya Garg <gargaditya08@live.com>
Cc: "benjamin.tissoires@redhat.com" <benjamin.tissoires@redhat.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"orlandoch.dev@gmail.com" <orlandoch.dev@gmail.com>,
"ronald@innovation.ch" <ronald@innovation.ch>
Subject: Re: [PATCH v3] HID: Recognize sensors with application collections
Date: Wed, 18 Jan 2023 09:54:46 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2301180953340.1734@cbobk.fhfr.pm> (raw)
In-Reply-To: <9E66CF6F-99A0-4CC5-9FA0-3A9DCFCA0388@live.com>
On Wed, 11 Jan 2023, Aditya Garg wrote:
> From: Ronald Tschalär <ronald@innovation.ch>
>
> According to HUTRR39 logical sensor devices may be nested inside
> physical collections or may be specified in multiple top-level
> application collections (see page 59, strategies 1 and 2). However,
> the current code was only recognizing those with physical collections.
>
> This issue turned up in the T2 MacBook Pros which define the ALS in
> a top-level application collection.
>
> Signed-off-by: Ronald Tschalär <ronald@innovation.ch>
> Signed-off-by: Aditya Garg <gargaditya08@live.com>
Makes sense. Queued in for-6.3/hid-core. Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2023-01-18 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 7:26 [PATCH] HID: Recognize sensors with application collections too Aditya Garg
2023-01-10 8:55 ` [PATCH RESEND] " Aditya Garg
2023-01-10 8:57 ` [PATCH v2] " Aditya Garg
2023-01-10 22:16 ` srinivas pandruvada
2023-01-11 10:06 ` Aditya Garg
2023-01-11 10:07 ` [PATCH v3] HID: Recognize sensors with application collections Aditya Garg
2023-01-11 16:59 ` srinivas pandruvada
2023-01-18 8:54 ` Jiri Kosina [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=nycvar.YFH.7.76.2301180953340.1734@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=gargaditya08@live.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orlandoch.dev@gmail.com \
--cc=ronald@innovation.ch \
--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 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.