From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: andrew@codeconstruct.com.au, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
openbmc@lists.ozlabs.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
avifishman70@gmail.com, tali.perry1@gmail.com,
venture@google.com, yuenn@google.com, benjaminfair@google.com
Subject: Re: [PATCH v2 2/2] spi: dt-bindings: nuvoton,npcm-fiu: Convert to DT schema
Date: Tue, 9 Jun 2026 09:16:43 +0200 [thread overview]
Message-ID: <20260609-rebel-advanced-dragonfly-efdafe@quoll> (raw)
In-Reply-To: <20260608175418.1936892-3-tmaimon77@gmail.com>
On Mon, Jun 08, 2026 at 08:54:18PM +0300, Tomer Maimon wrote:
> Convert the Nuvoton NPCM FIU binding to DT schema format.
You should explain here why second 'reg' is optional. It wasn't in
original binding, so you made a change to the binding during conversion.
...
> -
> diff --git a/Documentation/devicetree/bindings/spi/nuvoton,npcm-fiu.yaml b/Documentation/devicetree/bindings/spi/nuvoton,npcm-fiu.yaml
> new file mode 100644
> index 000000000000..0f95def01910
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/nuvoton,npcm-fiu.yaml
Filename: nuvoton,npcm750-fiu.yaml
> @@ -0,0 +1,91 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/spi/nuvoton,npcm-fiu.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Nuvoton NPCM Flash Interface Unit (FIU) SPI Controller
> +
> +maintainers:
> + - Tomer Maimon <tmaimon77@gmail.com>
> +
> +allOf:
> + - $ref: spi-controller.yaml#
> +
> +description: |
> + NPCM FIU supports single, dual and quad communication interface.
> +
> + The NPCM7XX supports three FIU modules:
> + FIU0 and FIUx support two chip selects
> + FIU3 supports four chip selects.
> +
> + The NPCM8XX supports four FIU modules:
> + FIU0 and FIUx support two chip selects
> + FIU1 and FIU3 support four chip selects.
> +
> + Alias convention:
> + The '/aliases' node should define:
> + For NPCM7xx: fiu0=&fiu0; fiu1=&fiu3; fiu2=&fiux;
> + For NPCM8xx: fiu0=&fiu0; fiu1=&fiu3; fiu2=&fiux; fiu3=&fiu1;
> +
> +properties:
> + compatible:
> + enum:
> + - nuvoton,npcm750-fiu # Poleg NPCM7XX
> + - nuvoton,npcm845-fiu # Arbel NPCM8XX
> +
> + reg:
> + minItems: 1
> + items:
> + - description: FIU registers
> + - description: Memory-mapped flash contents (optional)
> +
> + reg-names:
> + minItems: 1
> + items:
> + - const: control
> + - const: memory
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - enum:
> + - clk_spi0
> + - clk_spi1
> + - clk_spi3
> + - clk_spix
This wasn't in the original binding. Nothing explains why it was added.
> +
> + nuvoton,spix-mode:
> + type: boolean
> + description: Enable SPIX mode for an expansion bus to an ASIC or CPLD.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - clocks
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/nuvoton,npcm7xx-clock.h>
> + spi@fb000000 {
> + compatible = "nuvoton,npcm750-fiu";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0xfb000000 0x1000>, <0x80000000 0x10000000>;
> + reg-names = "control", "memory";
reg and reg-names follow compatible.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-09 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 17:54 [PATCH v2 0/2] Nuvoton NPCM FIU DTS fixes and binding conversion Tomer Maimon
2026-06-08 17:54 ` [PATCH v2 1/2] arm: dts: nuvoton: npcm7xx: Drop bogus FIU memory reg-names Tomer Maimon
2026-06-09 7:13 ` Krzysztof Kozlowski
2026-06-08 17:54 ` [PATCH v2 2/2] spi: dt-bindings: nuvoton,npcm-fiu: Convert to DT schema Tomer Maimon
2026-06-09 7:16 ` Krzysztof Kozlowski [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=20260609-rebel-advanced-dragonfly-efdafe@quoll \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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
all inboxes | Powered by JetHome®