Linux SPI subsystem development
 help / color / mirror / Atom feed
From: "Nuno Sá" <nuno.sa@analog.com>
To: Conor Dooley <conor@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Parshuram Thombare <pthombar@cadence.com>,
	devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jisheng Zhang <jszhang@kernel.org>,
	Fei Xie <fei.xie@horizon.auto>
Subject: Re: [PATCH 2/3] spi: dt-bindings: cdns,xspi: add ACMD and internal DMA properties
Date: Fri, 30 Oct 2026 09:57:36 +0000	[thread overview]
Message-ID: <auRpD5u6JQgwQM4f@nsa> (raw)
In-Reply-To: <20261029-tag-scrutiny-b9ef1299e88c@spud>

On Thu, Oct 29, 2026 at 06:31:00PM +0000, Conor Dooley wrote:
> On Thu, Oct 29, 2026 at 04:03:17PM +0000, Nuno Sá wrote:
> > The Cadence xSPI controller supports an auto command (ACMD) mode where
> > high level sequences (read, program, erase) are handled by the
> > controller and data can be moved by its internal DMA. Whether ACMD can
> > be used, and whether the internal DMA bus requester interface is wired,
> > depends on how the IP is integrated (e.g. external SRAM, interconnect
> > wiring) and cannot be discovered from the controller.
> > 
> > Add the cdns,has-acmd and cdns,has-internal-dma boolean properties to
> > describe that. The internal DMA is only used by ACMD, so properly
> > reflect that.
> 
> Why would these properties be needed? What the controller support surely
> can be determined from the specific compatible for the SoC integration?

Alright, I'm more used to describe peripherals than this kind of IPs but
I imagined that these being properties of the IP that would make sense
to describe them in binding. Ok, but I sees this leaves the door
open to just add properties in integrations that would not make sense
and if we're going to have any compatible conditional kind of handling,
I guess it makes them pointless.

- Nuno Sá

> 
> > 
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > ---
> >  Documentation/devicetree/bindings/spi/cdns,xspi.yaml | 18 ++++++++++++++++++
> >  1 file changed, 18 insertions(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/spi/cdns,xspi.yaml b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> > index 38a5795589de..9708ede79730 100644
> > --- a/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> > +++ b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> > @@ -40,11 +40,29 @@ properties:
> >    interrupts:
> >      maxItems: 1
> >  
> > +  cdns,has-acmd:
> > +    type: boolean
> > +    description:
> > +      The controller supports the auto command (ACMD) mode. The IP may need
> > +      external hardware (like SRAM) at SoC integration to fully leverage
> > +      ACMD.
> > +
> > +  cdns,has-internal-dma:
> > +    type: boolean
> > +    description:
> > +      The controller internal DMA bus requester interface is wired at SoC
> > +      integration, so the controller can move ACMD data to and from memory
> > +      on its own.
> > +
> >  required:
> >    - compatible
> >    - reg
> >    - interrupts
> >  
> > +dependencies:
> > +  cdns,has-internal-dma:
> > +    - cdns,has-acmd
> > +
> >  allOf:
> >    - $ref: spi-controller.yaml#
> >    - if:
> > 
> > -- 
> > 2.56.0
> > 



  reply	other threads:[~2026-10-30  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 16:03 [PATCH 0/3] spi: cadence-xspi: add ACMD mode support Nuno Sá
2026-10-29 16:03 ` [PATCH 1/3] spi: cadence-xspi: rename sdma_error to xfer_error Nuno Sá
2026-10-29 16:03 ` [PATCH 2/3] spi: dt-bindings: cdns,xspi: add ACMD and internal DMA properties Nuno Sá
2026-10-29 18:31   ` Conor Dooley
2026-10-30  9:57     ` Nuno Sá [this message]
2026-10-29 16:03 ` [PATCH 3/3] spi: cadence-xspi: add ACMD mode support Nuno Sá
2026-10-29 16:51   ` Mark Brown
2026-10-30 10:16     ` Nuno Sá
2026-10-30 11:03       ` Mark Brown
2026-10-30 16:00         ` Nuno Sá

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=auRpD5u6JQgwQM4f@nsa \
    --to=nuno.sa@analog.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fei.xie@horizon.auto \
    --cc=jszhang@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=pthombar@cadence.com \
    --cc=robh@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