devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ChiYuan Huang <cy_huang@richtek.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056 family
Date: Thu, 28 Dec 2023 11:19:29 +0800	[thread overview]
Message-ID: <20231228031929.GA32046@linuxcarl2.richtek.com> (raw)
In-Reply-To: <0f1f0991-9ad9-4216-afc8-8340eddb1ad9@linaro.org>

On Tue, Dec 26, 2023 at 01:12:50PM +0100, Krzysztof Kozlowski wrote:
> On 26/12/2023 12:19, ChiYuan Huang wrote:
> > On Tue, Dec 26, 2023 at 10:18:47AM +0100, Krzysztof Kozlowski wrote:
> >> On 26/12/2023 04:47, cy_huang@richtek.com wrote:
> >>> From: ChiYuan Huang <cy_huang@richtek.com>
> >>>
> >>> Add compatible support for RTQ6053 and RTQ6059.
> >>>
> >>> Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> >>> ---
> >>>  .../devicetree/bindings/iio/adc/richtek,rtq6056.yaml         | 5 ++++-
> >>>  1 file changed, 4 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/Documentation/devicetree/bindings/iio/adc/richtek,rtq6056.yaml b/Documentation/devicetree/bindings/iio/adc/richtek,rtq6056.yaml
> >>> index 88e008629ea8..d1e1f36d1972 100644
> >>> --- a/Documentation/devicetree/bindings/iio/adc/richtek,rtq6056.yaml
> >>> +++ b/Documentation/devicetree/bindings/iio/adc/richtek,rtq6056.yaml
> >>> @@ -25,7 +25,10 @@ description: |
> >>>  
> >>>  properties:
> >>>    compatible:
> >>> -    const: richtek,rtq6056
> >>> +    enum:
> >>> +      - richtek,rtq6053
> >>> +      - richtek,rtq6056
> >>
> >> Aren't these devices compatible? Your driver change says they are, so
> >> express compatibility with list here (and oneOf).
> >>
> > Thanks, I try to take other binding as the reference. One more question.
> > If rtq6053 is compatible with rtq6056, there's only chip package type difference.
> > Do I need to seperate it into a dedicated enum element?
> > Or just put it into one item and said this part number is compatible with rtq6056? 
> 
> See example-schema. You need enum and items, both in oneOf:.
>
After reading the 'example-schema', I Still cannot understand what the special case items
means.

But in my case, is the below change correct?
[Diff]
properties:
   compatible:
-    enum:
-      - richtek,rtq6053
-      - richtek,rtq6056
-      - richtek,rtq6059
+    oneOf:
+      - items:
+          - enum:
+              - richtek,rtq6053
+              - richtek,rtq6056
+              - richtek,rtq6059
 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2023-12-28  3:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1703562468-29052-1-git-send-email-cy_huang@richtek.com>
     [not found] ` <1703562468-29052-2-git-send-email-cy_huang@richtek.com>
2023-12-26  9:18   ` [PATCH 1/2] dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056 family Krzysztof Kozlowski
2023-12-26 11:19     ` ChiYuan Huang
2023-12-26 12:12       ` Krzysztof Kozlowski
2023-12-28  3:19         ` ChiYuan Huang [this message]
2023-12-28  7:09           ` Krzysztof Kozlowski
2023-12-28  7:58             ` ChiYuan Huang
2023-12-28  8:06               ` Krzysztof Kozlowski
2023-12-28  8:44                 ` ChiYuan Huang
2023-12-26 16:24     ` Jonathan Cameron
2023-12-28  3:26       ` ChiYuan Huang
2023-12-28  3:37         ` ChiYuan Huang
2023-12-28  3:51 [PATCH 0/2] RTQ6056: Add compatible for the same chip family cy_huang
2023-12-28  3:51 ` [PATCH 1/2] dt-bindings: iio: adc: rtq6056: add support for the whole RTQ6056 family cy_huang
2023-12-28  7:15   ` Krzysztof Kozlowski

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=20231228031929.GA32046@linuxcarl2.richtek.com \
    --to=cy_huang@richtek.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).