From: Conor Dooley <conor@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: light: stk33xx: add compatible for stk3013
Date: Wed, 26 Jun 2024 17:06:48 +0100 [thread overview]
Message-ID: <20240626-junior-tag-cd3e27c4b140@spud> (raw)
In-Reply-To: <20240625165122.231182-2-kauschluss@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Tue, Jun 25, 2024 at 10:21:06PM +0530, Kaustabh Chakraborty wrote:
> Add the compatible string of stk3013 to the existing list.
>
> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
> ---
> Documentation/devicetree/bindings/iio/light/stk33xx.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> index f6e22dc9814a..6003da66a7e6 100644
> --- a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> +++ b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
> @@ -19,6 +19,7 @@ allOf:
> properties:
> compatible:
> enum:
> + - sensortek,stk3013
The driver change suggests that this device is compatible with the
existing sensors.
Jonathan, could we relax the warning during init
ret = stk3310_check_chip_id(chipid);
if (ret < 0)
dev_warn(&client->dev, "unknown chip id: 0x%x\n", chipid);
and allow fallback compatibles here please?
> - sensortek,stk3310
> - sensortek,stk3311
> - sensortek,stk3335
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-26 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 16:51 [PATCH 1/2] iio: light: stk3310: add support for stk3013 Kaustabh Chakraborty
2024-06-25 16:51 ` [PATCH 2/2] dt-bindings: iio: light: stk33xx: add compatible " Kaustabh Chakraborty
2024-06-26 16:06 ` Conor Dooley [this message]
2024-06-29 18:08 ` Jonathan Cameron
2024-07-03 18:31 ` Kaustabh Chakraborty
2024-07-03 19:30 ` Conor Dooley
2024-07-04 7:16 ` Kaustabh Chakraborty
2024-07-07 16:49 ` Jonathan Cameron
2024-07-08 18:56 ` Kaustabh Chakraborty
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=20240626-junior-tag-cd3e27c4b140@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kauschluss@disroot.org \
--cc=linux-iio@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).