Devicetree
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: Joy Zou <joy.zou@nxp.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
	Ye Li <ye.li@nxp.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: dma: fsl-edma: add dma-channel-mask property description
Date: Fri, 5 Jun 2026 11:32:14 -0400	[thread overview]
Message-ID: <aiLr_gi7X8ROoCFq@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <cf7b4c03-e1f4-4439-8077-2f8677bb2cea@gmail.com>

On Fri, Jun 05, 2026 at 03:44:23AM -0700, Laurentiu Mihalcea wrote:
>
>
> On 2/11/2026 1:28 AM, Joy Zou wrote:
> > Add documentation for the dma-channel-mask property in the fsl-edma
> > binding. This property uses an inverted bit definition: bit value 0
> > indicates the channel is available, while bit value 1 indicates
> > unavailable.
> >
> > That was already used widely for i.MX8, i.MX9. Correcting the definition
> > will break backward compatibility. This reversal only impacts the eDMA
> > dts node and driver, and doesn't impact DMA consumer. Therefore,
> > keep the inverted definition.
> >
> > Also add a note at the top of the binding to highlight this inverted
> > definition to prevent confusion.
> >
> > Signed-off-by: Joy Zou <joy.zou@nxp.com>
> Hi,
>
> I believe this patch hasn't been picked up yet even though it's been ACK'd by one of the
> DT binding maintainers.
>
> Frank Li, can you please take it into your tree?

I ping vnod in irc yesterday, let wait for few days, if he don't pick, I
will pick it.

Frank
>
>
> Thanks,
> Laurentiu

  reply	other threads:[~2026-06-05 15:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  9:28 [PATCH v4 0/3] Reserve eDMA channels 0-1 for V2X Joy Zou
2026-02-11  9:28 ` [PATCH v4 1/3] dt-bindings: dma: fsl-edma: add dma-channel-mask property description Joy Zou
2026-02-11 15:34   ` Frank Li
2026-02-11 22:06   ` Rob Herring (Arm)
2026-06-05 10:44   ` Laurentiu Mihalcea
2026-06-05 15:32     ` Frank Li [this message]
2026-02-11  9:28 ` [PATCH v4 2/3] arm64: dts: imx95: Reserve eDMA channels 0-1 for V2X Joy Zou
2026-02-11  9:28 ` [PATCH v4 3/3] arm64: dts: imx95-evk: update the dma-channel-mask property Joy Zou
2026-02-24 20:32 ` (subset) [PATCH v4 0/3] Reserve eDMA channels 0-1 for V2X Frank Li
2026-06-10 19:08 ` Frank.Li
2026-06-11 15:01   ` Frank Li
2026-06-11  5:51 ` Vinod Koul

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=aiLr_gi7X8ROoCFq@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=joy.zou@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=laurentiumihalcea111@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=ye.li@nxp.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