devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Antoniu Miclaus <antoniu.miclaus@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dragos Bogdan <dragos.bogdan@analog.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adf4377: add adf4378 support
Date: Sat, 27 Jul 2024 13:30:24 +0100	[thread overview]
Message-ID: <20240727133024.4cf167ef@jic23-huawei> (raw)
In-Reply-To: <20240722-legibly-senator-db5651fb279b@spud>

On Mon, 22 Jul 2024 17:26:37 +0100
Conor Dooley <conor@kernel.org> wrote:

> On Mon, Jul 22, 2024 at 04:45:05PM +0300, Antoniu Miclaus wrote:
> > Add porperty conditions for the adf4378.

property

> > Add product link for the adf4378.  
> 
> I can see this from the diff. You need to explain /why/ this gpio is not
> valid for use on this device.
> 
> > 
> > Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> > ---
> > changes in v2:
> >  - use property conditions for clk2 gpio
> > Note: the compatible is already available from the firs iteration of the driver
> > where these particularities weren't available for adf4378
> >  .../devicetree/bindings/iio/frequency/adi,adf4377.yaml | 10 ++++++++++
> >  1 file changed, 10 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml b/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> > index aa6a3193b4e0..5f950ee9aec7 100644
> > --- a/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> > +++ b/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> > @@ -17,6 +17,7 @@ description: |
> >     applications.
> >  
> >     https://www.analog.com/en/products/adf4377.html
> > +   https://www.analog.com/en/products/adf4378.html
> >  
> >  properties:
> >    compatible:
> > @@ -73,6 +74,15 @@ required:
> >  
> >  allOf:
> >    - $ref: /schemas/spi/spi-peripheral-props.yaml#
> > +  - if:
> > +      properties:
> > +        compatible:
> > +          contains:
> > +            enum:
> > +              - adi,adf4378
> > +    then:
> > +      properties:
> > +        clk2-enable-gpios: false
> >  
> >  unevaluatedProperties: false
> >  
> > -- 
> > 2.45.2
> >   


      reply	other threads:[~2024-07-27 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22 13:45 [PATCH v2 1/2] dt-bindings: iio: adf4377: add adf4378 support Antoniu Miclaus
2024-07-22 13:45 ` [PATCH v2 2/2] iio: frequency: " Antoniu Miclaus
2024-07-27 12:33   ` Jonathan Cameron
2024-07-22 16:26 ` [PATCH v2 1/2] dt-bindings: iio: " Conor Dooley
2024-07-27 12:30   ` Jonathan Cameron [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=20240727133024.4cf167ef@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dragos.bogdan@analog.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).