From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH 1/9] dt-bindings: spi: Add STM32 OSPI controller
Date: Fri, 24 Jan 2025 16:53:04 +0100 [thread overview]
Message-ID: <2d712420-c8ed-4bf9-83ec-348f71aa1ce9@foss.st.com> (raw)
In-Reply-To: <ea4ca423-c75d-468c-b5b2-673cd58e42c9@kernel.org>
On 1/22/25 16:18, Krzysztof Kozlowski wrote:
> On 22/01/2025 15:10, patrice.chotard@foss.st.com wrote:
>> ---
>> .../bindings/spi/st,stm32-ospi.yaml | 109 ++++++++++++++++++
>> 1 file changed, 109 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/spi/st,stm32-ospi.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/spi/st,stm32-ospi.yaml b/Documentation/devicetree/bindings/spi/st,stm32-ospi.yaml
>> new file mode 100644
>> index 000000000000..bf16252f85fa
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/spi/st,stm32-ospi.yaml
>
>
> Use compatible as filename.
Ok
>
>> @@ -0,0 +1,109 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/spi/st,stm32-ospi.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: STMicroelectronics STM32 Octal Serial Peripheral Interface (OSPI)
>> +
>> +maintainers:
>> + - Patrice Chotard <patrice.chotard@foss.st.com>
>> +
>> +allOf:
>> + - $ref: spi-controller.yaml#
>> +
>> +properties:
>> + compatible:
>> + const: st,stm32mp25-ospi
>> +
>> + reg:
>> + description: registers
>
> That's not helping. Please take a look how other bindings do it.
> maxItems instead or you need to list the items with meaningful description.
ok, will use maxItems
>
>> +
>> + "#address-cells":
>> + const: 1
>> +
>> + "#size-cells":
>> + const: 0
>
> Drop *cells.
ok
>> +
>> + memory-region:
>> + maxItems: 1
>> + description: Phandle to a node describing memory-map region to be used
>
> Drop description, redundant. Say something useful - the purpose - or
> just maxItems if purpose is obvious.
ok, i will add
- description: phandle to OSPI block reset
- description: phandle to delay block reset
>
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + resets:
>> + maxItems: 2
>
> You need to list and describe the items.
ok
>
>> +
>> + dmas:
>> + items:
>> + - description: tx DMA channel
>> + - description: rx DMA channel
>
> maxItems: 2 is enough, because names define what these are
ok
>
>> +
>> + dma-names:
>> + items:
>> + - const: tx
>> + - const: rx
>> +
>> + st,syscfg-dlyb:
>> + description: |
>> + Use to set the OSPI delay block within SYSCFG to:
>
> Phandles to what? Describe also the destination device.
>
>> + Tune the phase of the RX sampling clock (or DQS) in order
>
> Unneeded indentation.
>
>> + to sample the data in their valid window.
>> + Tune the phase of the TX launch clock in order to meet setup
>> + and hold constraints of TX signals versus the memory clock.
>> + $ref: /schemas/types.yaml#/definitions/phandle-array
>> + items:
>> + minItems: 2
>> + maxItems: 2
>
> Your example has only one item, so probably you wanted one more items
> with description. Now you miss one of matrix constraints.
My fault, only one item is required.
>
> git grep -C 8 phandle-array
> (e.g. some sram or syscon examples)
>
>
>
>> +
>> + access-controllers:
>> + minItems: 1
>> + maxItems: 2
>
> List the items.
i will update as following:
access-controllers:
- description: phandle to the rifsc device to check access right.
- description: phandle to the rcc device for secure clock control
minItems: 1
maxItems: 2
>
>> +
>> + power-domains:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - "#address-cells"
>> + - "#size-cells"
>
> Drop cells
ok
>
>> + - clocks
>> + - interrupts
>> + - st,syscfg-dlyb
>> +
>> +unevaluatedProperties: false
>> +
>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-01-24 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 14:10 [PATCH 0/9] Add STM32MP25 SPI NOR support patrice.chotard
2025-01-22 14:10 ` [PATCH 1/9] dt-bindings: spi: Add STM32 OSPI controller patrice.chotard
2025-01-22 15:18 ` Krzysztof Kozlowski
2025-01-24 15:53 ` Patrice CHOTARD [this message]
2025-01-22 14:10 ` [PATCH 2/9] spi: stm32: Add OSPI driver patrice.chotard
2025-01-22 14:10 ` [PATCH 3/9] dt-bindings: misc: Add STM32 Octo Memory Manager controller patrice.chotard
2025-01-22 15:22 ` Krzysztof Kozlowski
2025-01-24 15:53 ` Patrice CHOTARD
2025-01-22 14:10 ` [PATCH 4/9] misc: Add STM32 Octo Memory Manager driver patrice.chotard
2025-01-22 14:10 ` [PATCH 5/9] arm64: dts: st: Add OMM node on stm32mp251 patrice.chotard
2025-01-22 14:10 ` [PATCH 6/9] arm64: dts: st: Add ospi port1 pinctrl entries in stm32mp25-pinctrl.dtsi patrice.chotard
2025-01-22 14:10 ` [PATCH 7/9] arm64: dts: st: Add SPI NOR flash support on stm32mp257f-ev1 board patrice.chotard
2025-01-22 14:10 ` [PATCH 8/9] arm64: defconfig: Enable STM32 Octo Memory Manager driver patrice.chotard
2025-01-22 15:23 ` Krzysztof Kozlowski
2025-01-24 15:53 ` Patrice CHOTARD
2025-01-22 14:10 ` [PATCH 9/9] arm64: defconfig: Enable STM32 OctoSPI driver patrice.chotard
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=2d712420-c8ed-4bf9-83ec-348f71aa1ce9@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.kerello@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=will@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).