All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
	linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ulf Hansson <ulfh@kernel.org>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ste_dma40: Use power domain for LCLA SRAM
Date: Wed, 18 Nov 2026 20:57:32 -0600	[thread overview]
Message-ID: <av5kXd5Kp0e24FER@SMW015318> (raw)
In-Reply-To: <CAD++jL=ZFJFTV6zY=SA+aHMQyjw4MQ8zFgWmUUBEoH6vKDLTsA@mail.gmail.com>

On Wed, Nov 18, 2026 at 09:19:20PM +0100, Linus Walleij wrote:
> On Wed, Nov 18, 2026 at 8:53 PM Frank Li <Frank.li@oss.nxp.com> wrote:
>
> > On Sun, Nov 15, 2026 at 10:26:27PM +0100, Linus Walleij wrote:
>
> > > Replace the LCLA ESRAM regulator with runtime PM of the SRAM device
> > > owning the ESRAM34 power domain.
> (...)
> > > -     /* If lcla has to be located in ESRAM we don't need to allocate */
> > > -     if (base->plat_data->use_esram_lcla) {
> >
> > Does it break old dts's back compatiblity?
>
> It would if they were using LCLA SRAM but there are no
> DTS:es that actually define the LCLA SRAM, so we are fine,

Please add such information at commit message.

Frank

> all existing deployments put the linked lists in common RAM.
> It was an oversight or "fix later", "technical debt" that was
> introduced 15 years ago.
>
> After this is fixed properly with power domains I want to turn it on.
>
> Yours,
> Linus Walleij

      reply	other threads:[~2026-11-19  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 21:26 [PATCH] dmaengine: ste_dma40: Use power domain for LCLA SRAM Linus Walleij
2026-11-15 21:41 ` sashiko-bot
2026-11-15 22:42   ` Linus Walleij
2026-11-18 19:53 ` Frank Li
2026-11-18 20:19   ` Linus Walleij
2026-11-19  2:57     ` Frank Li [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=av5kXd5Kp0e24FER@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ulfh@kernel.org \
    --cc=vkoul@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.