devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Gregory CLEMENT <gregory.clement@bootlin.com>,
	Paul Burton <paulburton@kernel.org>,
	Quentin Schulz <quentin.schulz@bootlin.com>,
	Antoine Tenart <atenart@kernel.org>,
	Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	"David S . Miller" <davem@davemloft.net>,
	UNGLinuxDriver@microchip.com, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v1 8/8] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format
Date: Sun, 13 Mar 2022 17:36:36 +0100	[thread overview]
Message-ID: <b5a33a3441f829638740204e0c4dc938@walle.cc> (raw)
In-Reply-To: <869d4fda-e943-1817-17cd-df7b323a1fef@kernel.org>

Hi,

wow, you're fast!

Am 2022-03-13 16:55, schrieb Krzysztof Kozlowski:

>> +  reg: true
> 
> maxItems

There are up to two address ranges. The second one is only needed for
particular controllers (the sparx5 and the lan966x).

Is the following snippet the correct form?

   reg:
     items:
       - description: Base address
       - description: Extended pin configuration registers
     minItems: 1

-michael

  reply	other threads:[~2022-03-13 16:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 15:29 [PATCH v1 0/8] pinctrl: ocelot: convert to YAML format Michael Walle
2022-03-13 15:29 ` [PATCH v1 1/8] MIPS: mscc: jaguar2: fix pinctrl nodes Michael Walle
2022-03-13 15:29 ` [PATCH v1 2/8] MIPS: mscc: ocelot: fix MIIM1 pinctrl node name Michael Walle
2022-03-13 15:29 ` [PATCH v1 3/8] MIPS: mscc: ocelot: fix PHY interrupt " Michael Walle
2022-03-13 15:29 ` [PATCH v1 4/8] MIPS: mscc: ocelot: fix load/save GPIO pinctrl name Michael Walle
2022-03-13 15:29 ` [PATCH v1 5/8] MIPS: mscc: serval: fix pinctrl node names Michael Walle
2022-03-13 15:29 ` [PATCH v1 6/8] arm64: dts: sparx5: " Michael Walle
2022-03-13 15:29 ` [PATCH v1 7/8] ARM: dts: lan9662-pcb8291: fix pinctrl node name Michael Walle
2022-03-13 15:29 ` [PATCH v1 8/8] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format Michael Walle
2022-03-13 15:55   ` Krzysztof Kozlowski
2022-03-13 16:36     ` Michael Walle [this message]
2022-03-13 17:54       ` 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=b5a33a3441f829638740204e0c4dc938@walle.cc \
    --to=michael@walle.cc \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=krzk@kernel.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=paulburton@kernel.org \
    --cc=quentin.schulz@bootlin.com \
    --cc=robh+dt@kernel.org \
    --cc=tsbogend@alpha.franken.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).