From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Witold Sadowski <wsadowski@marvell.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org
Cc: broonie@kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
pthombar@cadence.com
Subject: Re: [PATCH v4 2/5] dt-bindings: spi: cadence: Add MRVL overlay bindings documentation for Cadence XSPI
Date: Tue, 21 May 2024 12:29:13 +0200 [thread overview]
Message-ID: <70863d5c-65f8-4baa-99ce-8739ce47fac3@linaro.org> (raw)
In-Reply-To: <20240509010523.3152264-3-wsadowski@marvell.com>
On 09/05/2024 03:05, Witold Sadowski wrote:
> Add new bindings for v2 Marvell xSPI overlay:
> mrvl,xspi-nor compatible string
Where?
Why double space?
subject prefix: spi goes first
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
> New compatible string to distinguish between orginal and modified xSPI
> block
>
> PHY configuration registers
> Allow to change orginal xSPI PHY configuration values. If not set, and
> Marvell overlay is enabled, safe defaults will be written into xSPI PHY
>
> Optional base for xfer register set
> Additional reg field to allocate xSPI Marvell overlay XFER block
I have troubles reading this. Is this some sort of one long sentence or
a list?
>
> Signed-off-by: Witold Sadowski <wsadowski@marvell.com>
> ---
> .../devicetree/bindings/spi/cdns,xspi.yaml | 78 +++++++++++++++----
> 1 file changed, 65 insertions(+), 13 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/cdns,xspi.yaml b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> index eb0f92468185..094f8b7ffc49 100644
> --- a/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> +++ b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> @@ -17,22 +17,43 @@ description: |
>
> allOf:
> - $ref: spi-controller.yaml#
> + - if:
Move the allOf after required block.
> + properties:
> + compatible:
> + contains:
> + const: marvell,cn10-xspi-nor
> + then:
> + properties:
> + reg-names:
> + items:
> + - const: io
> + - const: sdma
> + - const: aux
> + - const: xferbase
> + reg:
> + items:
> + - description: address and length of the controller register set
> + - description: address and length of the Slave DMA data port
> + - description: address and length of the auxiliary registers
> + - description: address and length of the xfer registers
> + else:
> + properties:
> + reg-names:
> + items:
> + - const: io
> + - const: sdma
> + - const: aux
> + reg:
> + items:
> + - description: address and length of the controller register set
> + - description: address and length of the Slave DMA data port
> + - description: address and length of the auxiliary registers
>
> properties:
> compatible:
> - const: cdns,xspi-nor
> -
> - reg:
> - items:
> - - description: address and length of the controller register set
> - - description: address and length of the Slave DMA data port
> - - description: address and length of the auxiliary registers
Widest constraints stay here.
> -
> - reg-names:
> - items:
> - - const: io
> - - const: sdma
> - - const: aux
Widest constraints stay here.
> + enum:
> + - cdns,xspi-nor
> + - marvell,cn10-xspi-nor
>
> interrupts:
> maxItems: 1
> @@ -68,6 +89,37 @@ examples:
> reg = <0>;
> };
>
> + flash@1 {
> + compatible = "jedec,spi-nor";
> + spi-max-frequency = <75000000>;
> + reg = <1>;
> + };
> + };
> + };
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + bus {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + spi@d0010000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "marvell,cn10-xspi-nor";
> + reg = <0x0 0xa0010000 0x0 0x1040>,
> + <0x0 0xb0000000 0x0 0x1000>,
> + <0x0 0xa0020000 0x0 0x100>,
> + <0x0 0xa0090000 0x0 0x100>;
No need for new example for difference in one property.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-21 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 1:05 [PATCH v4 0/5] Marvell HW overlay support for Cadence xSPI Witold Sadowski
2024-05-09 1:05 ` [PATCH v4 1/5] spi: cadence: Ensure data lines set to low during dummy-cycle period Witold Sadowski
2024-05-09 1:05 ` [PATCH v4 2/5] dt-bindings: spi: cadence: Add MRVL overlay bindings documentation for Cadence XSPI Witold Sadowski
2024-05-09 17:22 ` Conor Dooley
2024-05-27 8:26 ` [EXTERNAL] " Witold Sadowski
2024-05-21 10:29 ` Krzysztof Kozlowski [this message]
2024-05-27 8:25 ` Witold Sadowski
2024-05-09 1:05 ` [PATCH v4 3/5] spi: cadence: Add Marvell xSPI IP overlay changes Witold Sadowski
2024-05-21 10:32 ` Krzysztof Kozlowski
2024-05-27 8:22 ` [EXTERNAL] " Witold Sadowski
2024-05-09 1:05 ` [PATCH v4 4/5] spi: cadence: Allow to read basic xSPI configuration from ACPI Witold Sadowski
2024-05-09 1:05 ` [PATCH v4 5/5] spi: cadence: Add MRVL overlay xfer operation support Witold Sadowski
2024-05-21 10:33 ` Krzysztof Kozlowski
2024-05-27 8:20 ` [EXTERNAL] " Witold Sadowski
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=70863d5c-65f8-4baa-99ce-8739ce47fac3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=pthombar@cadence.com \
--cc=robh@kernel.org \
--cc=wsadowski@marvell.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