From: Mark Brown <broonie@kernel.org>
To: xianwei.zhao@amlogic.com
Cc: Sunny Luo <sunny.luo@amlogic.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-amlogic@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] spi: dt-bindings: amlogic: spisg: Document A9-specific properties
Date: Thu, 30 Jul 2026 14:22:28 +0100 [thread overview]
Message-ID: <db111663-27a2-4299-a692-6154f1f842ca@sirena.org.uk> (raw)
In-Reply-To: <20260723-a9-spisg-v2-1-9fc39106b7e2@amlogic.com>
[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]
On Thu, Jul 23, 2026 at 06:43:42AM +0000, Xianwei Zhao via B4 Relay wrote:
> From: Xianwei Zhao <xianwei.zhao@amlogic.com>
> Document the Amlogic A9 SPISG controller and its additional
> Device Tree properties.
> Add the "amlogic,a9-spisg" compatible string and define the
> A9-specific "amlogic,mo-idle-output" and "amlogic,word-gap"
> properties, which configure the MOSI idle output level and
> the inter-word gap, respectively.
> @@ -35,6 +34,23 @@ properties:
> resets:
> maxItems: 1
>
> + amlogic,mo-idle-output:
> + description: |
> + Controls the MOSI output level when the controller is idle.
> + 0 - Drive MOSI low
> + 1 - Drive MOSI high
> + 2 - Follow the last transmitted bit
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1, 2]
> + default: 0
> +
> + amlogic,word-gap:
> + description: |
> + Number of idle clock cycles inserted between consecutive SPI words.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1, 2, 3]
> + default: 1
I'd expect these to be per-device properties, not per controller. The
word_gap sounds a lot like the existing word_delay feature we have - if
it's different it'd be good to be clear why.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-07-30 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 6:43 [PATCH v2 0/4] spi: add support for Amlogic A9 Xianwei Zhao via B4 Relay
2026-07-23 6:43 ` [PATCH v2 1/4] spi: dt-bindings: amlogic: spisg: Document A9-specific properties Xianwei Zhao via B4 Relay
2026-07-23 6:51 ` sashiko-bot
2026-07-24 8:33 ` Krzysztof Kozlowski
2026-07-30 13:22 ` Mark Brown [this message]
2026-07-31 3:15 ` Xianwei Zhao
2026-07-23 6:43 ` [PATCH v2 2/4] spi: amlogic: spisg: Fix transfer size limit and timeout handling Xianwei Zhao via B4 Relay
2026-07-23 7:02 ` sashiko-bot
2026-07-23 6:43 ` [PATCH v2 3/4] spi: amlogic: spisg: Fix the incorrect keep_ss of the last descriptor Xianwei Zhao via B4 Relay
2026-07-23 6:54 ` sashiko-bot
2026-07-23 6:43 ` [PATCH v2 4/4] spi: amlogic: spisg: Add support for A9 controller features Xianwei Zhao via B4 Relay
2026-07-23 6:56 ` sashiko-bot
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=db111663-27a2-4299-a692-6154f1f842ca@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sunny.luo@amlogic.com \
--cc=xianwei.zhao@amlogic.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®