devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible for stk3013
Date: Tue, 16 Jul 2024 17:43:28 +0100	[thread overview]
Message-ID: <20240716174328.15c250a9@jic23-huawei> (raw)
In-Reply-To: <be34b0b571ddc33351e9eb123410a210@disroot.org>

On Mon, 15 Jul 2024 20:02:57 +0000
Kaustabh Chakraborty <kauschluss@disroot.org> wrote:

> On 2024-07-13 12:06, Jonathan Cameron wrote:
> > On Fri, 12 Jul 2024 20:54:02 +0530
> > Kaustabh Chakraborty <kauschluss@disroot.org> wrote:
> >   
> >> Add the compatible string of stk3013 to the existing list.  
> > 
> > Should include how this differs from existing devices such that it doesn't
> > make sense to use a fallback compatible.  
> 
> STK3013 is a proximity sensor by Sensortek, bearing chipid of 0x31. Despite
> being marketed as a proximity sensor, it also appears to have ambient
> light sensing capabilities.
> 
> Add the compatible string of stk3013 to the existing list, as a part not
> compatible with other devices.

That would be fine, but I'm not seeing any driver code changes, so when
you say not compatible, in what way? If it's register changes in features
we don't support yet or something like that, just add some examples.

A different whoami register value isn't sufficient as after the fix
you have as patch 1 that will only result in a message print.

Obviously doesn't help much for this addition as you are adding the
bypass of the whoami and the new ID in the same series, but we want
to set a precedence for future devices to use fallback compatibles
now that path works.

Jonathan

> 
> I hope this is good enough. I couldn't find anything more convincing.
> 
> >   
> >> 
> >> 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
> >>        - sensortek,stk3310
> >>        - sensortek,stk3311
> >>        - sensortek,stk3335  


  reply	other threads:[~2024-07-16 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 15:24 [PATCH 1/3] iio: light: stk3310: relax chipid check warning Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 2/3] iio: light: stk3310: add support for stk3013 Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible " Kaustabh Chakraborty
2024-07-13 12:06   ` Jonathan Cameron
2024-07-15 20:02     ` Kaustabh Chakraborty
2024-07-16 16:43       ` Jonathan Cameron [this message]
2024-07-17 15:58         ` Kaustabh Chakraborty
2024-07-20 12:45           ` Jonathan Cameron
2024-07-13 12:06 ` [PATCH 1/3] iio: light: stk3310: relax chipid check warning Jonathan Cameron
2024-07-14  8:51   ` 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=20240716174328.15c250a9@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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).