From: Krzysztof Kozlowski <krzk@kernel.org>
To: Meiker Gao <ot_meiker.gao@mediatek.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Bayi Cheng <bayi.cheng@mediatek.com>,
Chuanhong Guo <gch981213@gmail.com>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
sirius.wang@mediatek.com, vince-wl.liu@mediatek.com,
jh.hsu@mediatek.com
Subject: Re: [PATCH] spi: dt-bindings: mediatek,spi-mtk-nor: Add clock bindings for mt8189
Date: Wed, 11 Mar 2026 07:09:18 +0100 [thread overview]
Message-ID: <8bfdcc26-a640-47ba-81ff-ba8e8aa0ae9d@kernel.org> (raw)
In-Reply-To: <20260311053335.785292-1-ot_meiker.gao@mediatek.com>
On 11/03/2026 06:33, Meiker Gao wrote:
> Update mediatek,spi-mtk-nor.yaml to add conditional clock and
> clock-names bindings for the mt8189-nor platform. The mt8189-nor
> controller requires five specific clocks and corresponding clock-names
> ("spi", "sf", "axi_f", "axi_h", "axi_p"). This change enforces these
> requirements in the device tree binding schema.
>
> For other platforms, the minimum number of clocks and clock-names
> remains unchanged. The patch also adds an example for mt8189-nor,
> illustrating the new clock configuration.
>
> This update ensures correct hardware description and validation for
> mt8189-nor, improving compatibility and reducing configuration errors.
>
> Signed-off-by: Meiker Gao <ot_meiker.gao@mediatek.com>
> (cherry picked from commit c3180d35e52b5213764a89403e71f9a34d7bb842)
Clean your patches before sending them.
> ---
> .../bindings/spi/mediatek,spi-mtk-nor.yaml | 45 ++++++++++++++-----
> 1 file changed, 33 insertions(+), 12 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml b/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml
> index a453996c13f2..bd6f43a0c399 100644
> --- a/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml
> +++ b/Documentation/devicetree/bindings/spi/mediatek,spi-mtk-nor.yaml
> @@ -17,9 +17,6 @@ description: |
> for devices other than SPI NOR flash due to limited transfer
> capability of this controller.
>
> -allOf:
> - - $ref: /schemas/spi/spi-controller.yaml#
> -
> properties:
> compatible:
> oneOf:
> @@ -27,6 +24,7 @@ properties:
> - mediatek,mt8173-nor
> - mediatek,mt8186-nor
> - mediatek,mt8192-nor
> + - mediatek,mt8189-nor
> - items:
> - enum:
> - mediatek,mt2701-nor
> @@ -39,6 +37,7 @@ properties:
> - items:
> - enum:
> - mediatek,mt8188-nor
> + - mediatek,mt8189-nor
> - const: mediatek,mt8186-nor
>
> reg:
> @@ -56,14 +55,8 @@ properties:
> design, so this is optional.
> - description: clock used for controller axi slave bus.
> this depends on hardware design, so it is optional.
> -
> - clock-names:
You cannot remove properties.
> - minItems: 2
> - items:
> - - const: spi
> - - const: sf
> - - const: axi
> - - const: axi_s
> + - description: clock used for controller axi_f, axi_h, and
> + axi_p to support the new platform.
>
> required:
> - compatible
> @@ -71,6 +64,34 @@ required:
> - clocks
> - clock-names
>
> +allOf:
> + - $ref: /schemas/spi/spi-controller.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: mediatek,mt8189-nor
> + then:
> + properties:
> + clocks:
minItems
> + maxItems: 5
> + clock-names:
> + items:
> + - const: spi
> + - const: sf
> + - const: axi_f
That's just axi, no? Thus keep the list in top-level.
> + - const: axi_h
And that's axi_s
> + - const: axi_p
And what does p stand for? Do you understand these are names of clock
inputs, not names of clocks?
> + else:
> + properties:
> + clocks:
Missing minItems
> + maxItems: 4
> + clock-names:
> + items:
> + - const: spi
> + - const: sf
> + - const: axi
And that's ABI change, NAK.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-11 6:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 5:33 [PATCH] spi: dt-bindings: mediatek,spi-mtk-nor: Add clock bindings for mt8189 Meiker Gao
2026-03-11 6:09 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 16:59 kernel test robot
2026-03-11 10:34 kernel test robot
2026-03-11 3:43 Meiker Gao
2026-03-11 4:23 ` Rob Herring (Arm)
2026-03-13 13:15 ` Krzysztof Kozlowski
2026-03-11 1:51 Meiker Gao
2026-03-11 3:23 ` Rob Herring (Arm)
2026-03-07 12:23 kernel test robot
2026-03-06 12:49 kernel test robot
2026-03-05 11:04 kernel test robot
2026-03-05 7:15 Meiker Gao
2026-03-05 8:48 ` Krzysztof Kozlowski
2026-03-05 13:45 ` Rob Herring (Arm)
2026-03-05 2:27 Meiker Gao
2026-03-05 3:37 ` Rob Herring (Arm)
2026-03-05 8:47 ` Krzysztof Kozlowski
2026-03-05 8:47 ` 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=8bfdcc26-a640-47ba-81ff-ba8e8aa0ae9d@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bayi.cheng@mediatek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gch981213@gmail.com \
--cc=jh.hsu@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ot_meiker.gao@mediatek.com \
--cc=robh@kernel.org \
--cc=sirius.wang@mediatek.com \
--cc=vince-wl.liu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.