All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Parshuram Thombare <pthombar@cadence.com>,
	devicetree@vger.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 3/3] spi: cadence-xspi: add ACMD mode support
Date: Fri, 30 Oct 2026 18:40:29 +0000	[thread overview]
Message-ID: <20261030-register-coauthor-4de5eb324954@spud> (raw)
In-Reply-To: <auS-tFYUCIvMg-hH@nsa>

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

On Fri, Oct 30, 2026 at 04:00:46PM +0000, Nuno Sá wrote:
> On Fri, Oct 30, 2026 at 11:03:07AM +0000, Mark Brown wrote:
> > On Fri, Oct 30, 2026 at 10:16:00AM +0000, Nuno Sá wrote:
> > > On Thu, Oct 29, 2026 at 04:51:32PM +0000, Mark Brown wrote:
> > 
> > > > We need some suspend/resume handling to invalidate the configuration
> > > > when the IP power goes so we set everything up again.  I'm not seeing
> > > > anything here.
> > 
> > > Yeah, I did saw sashiko complain (and my local LLM also raised it
> > > actually) but I do wonder how can that happen? So we need to assume that
> > > in suspend we might lose power (maybe because it's regulator powers down)
> > > and need to do redo all the important initialization bits?
> > 
> > Yes, might not even be regulators - some SoCs have good internal power
> > domains and can gate parts of themselves very effectively.
> > 
> > > > > +	if (cdns_xspi_acmd_can_read(cdns_xspi, op))
> > > > > +		return 0;
> > 
> > > > That function has a minimum size but not a maximum size...
> > 
> > > > > +
> > > > >  	op->data.nbytes = clamp_val(op->data.nbytes, 0, cdns_xspi->sdmasize);
> > 
> > > > ...which we have here?
> > 
> > > For ACMD, in theory we can just configure UINT32_MAX on the register so
> > > not sure if it makes sense to clamp to that?
> > 
> > No, if that really is the limit it's fine.
> > 
> > > Conor is pushing against the new bindings and that it should be inferred
> > > from the compatible. I tested this on [1] which is not an upstream
> > > platform so I wonder if it's ok to add support for the complete
> > > integration even if the SoC is not upstream?
> > 
> > So long as it's an actual SoC that exists rather than some random FPGA
> > configuration or whatever upstreaming just the SPI driver is totally
> > fine, that's one less piece that needs doing whenever the rest of it is
> > handled.
> 
> Nice! Then v2 will bring the work for the SoC integration! Yes, real
> SoC with two A55 cores and a shark DSP.

You gotta start somewhere, often that is clock drivers and that kind of
thing because that's what's needed for bare minimum bootable systems,
but if it's spi, that's fine too.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-10-30 18:40 UTC|newest]

Thread overview: 13+ 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á
2026-10-30 18:45       ` Conor Dooley
2026-10-29 16:03 ` [PATCH 3/3] spi: cadence-xspi: add ACMD mode support Nuno Sá
2026-10-29 16:19   ` sashiko-bot
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á
2026-10-30 18:40           ` Conor Dooley [this message]

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=20261030-register-coauthor-4de5eb324954@spud \
    --to=conor@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@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=nuno.sa@analog.com \
    --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 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.