public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Ariana.Lazar@microchip.com, robh@kernel.org
Cc: Conor.Dooley@microchip.com, nuno.sa@analog.com,
	Jonathan.Cameron@huawei.com, devicetree@vger.kernel.org,
	jic23@kernel.org, krzk+dt@kernel.org, andy@kernel.org,
	linux-iio@vger.kernel.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: iio: dac: mcp47feb02: Fix maxItems value for reg property
Date: Tue, 21 Apr 2026 09:19:44 -0500	[thread overview]
Message-ID: <60e5cb91-e82a-47be-a7a0-c89f5f1b04ee@baylibre.com> (raw)
In-Reply-To: <8a57341539af3a96ad42004be2389370b76a1a56.camel@microchip.com>

On 4/21/26 9:11 AM, Ariana.Lazar@microchip.com wrote:
> Hello Rob,
> 
>>> @@ -161,8 +161,7 @@ patternProperties:
>>>      properties:
>>>        reg:
>>>          description: The channel number.
>>> -        minItems: 1
>>> -        maxItems: 8
>>> +        maxItems: 1
>>
>> Perhaps there are 8 channels and 'maximum: 8' is what was intended?
> 
> 
> 
> Thank you for the review.
> 
> Indeed, I mistakenly set maxItems to the maximum number of channels,
> rather than to a single entry for the reg property (reg value is
> between 0 and max 7 based on the part number).
> 

> If preferred, I can also add minimum: 0 and maximum: 7 to specify the
> valid range for the channel number.
> 

Yes, that sounds like the right idea.

      reply	other threads:[~2026-04-21 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 13:38 [PATCH v2] dt-bindings: iio: dac: mcp47feb02: Fix maxItems value for reg property Ariana Lazar
2026-04-17 15:26 ` David Lechner
2026-04-17 16:08   ` Conor Dooley
2026-04-20 15:01 ` Rob Herring
2026-04-21 14:11   ` Ariana.Lazar
2026-04-21 14:19     ` David Lechner [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=60e5cb91-e82a-47be-a7a0-c89f5f1b04ee@baylibre.com \
    --to=dlechner@baylibre.com \
    --cc=Ariana.Lazar@microchip.com \
    --cc=Conor.Dooley@microchip.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --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