From: "Barnabás Czémán" <trabarni@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Barnabás Czémán" <trabarni@gmail.com>
Subject: [PATCH 0/3] Add support for more stk3311 variant
Date: Tue, 21 May 2024 17:34:50 +0200 [thread overview]
Message-ID: <20240521-stk3311-v1-0-07a4966b355a@gmail.com> (raw)
This patch series remove probe failing when a compatible variant's chip id is not
defined in the driver like stk3311-a and make chip id additions easier.
It adds stk3311-a and stk3311-s34 chip ids.
I have tested stk3311-a in Xiaomi Redmi S2 (ysl) and Xiaom Redmi 5
(rosy),
it has 0x15 as chip id.
stk3311-s34 chip id comes from this thread it should be compatible with
this driver:
https://lore.kernel.org/linux-iio/20200703194406.110855-1-megous@megous.com/
Signed-off-by: Barnabás Czémán <trabarni@gmail.com>
---
Barnabás Czémán (3):
iio: light: stk3310: relax failure to match id
iio: light: stk3310: make chip id check expandable
iio: light: stk3310: support more stk3311 variants
drivers/iio/light/stk3310.c | 31 ++++++++++++++++++++++++-------
1 file changed, 24 insertions(+), 7 deletions(-)
---
base-commit: 124cfbcd6d185d4f50be02d5f5afe61578916773
change-id: 20240521-stk3311-2ee6ddafb970
Best regards,
--
Barnabás Czémán <trabarni@gmail.com>
next reply other threads:[~2024-05-21 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:34 Barnabás Czémán [this message]
2024-05-21 15:34 ` [PATCH 1/3] iio: light: stk3310: relax failure to match id Barnabás Czémán
2024-05-21 15:34 ` [PATCH 2/3] iio: light: stk3310: make chip id check expandable Barnabás Czémán
2024-05-21 15:34 ` [PATCH 3/3] iio: light: stk3310: support more stk3311 variants Barnabás Czémán
2024-05-25 16:50 ` [PATCH 0/3] Add support for more stk3311 variant Jonathan Cameron
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=20240521-stk3311-v1-0-07a4966b355a@gmail.com \
--to=trabarni@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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