From: Joy Zou <joy.zou@nxp.com>
To: frank.li@nxp.com, peng.fan@nxp.com, vkoul@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: imx@lists.linux.dev, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v4 2/2] dt-bindings: fsl-dma: fsl-edma: clean up unused "fsl,imx8qm-adma" compatible string
Date: Wed, 17 Apr 2024 11:26:42 +0800 [thread overview]
Message-ID: <20240417032642.3178669-3-joy.zou@nxp.com> (raw)
In-Reply-To: <20240417032642.3178669-1-joy.zou@nxp.com>
The eDMA hardware issue only exist imx8QM A0. A0 never mass production.
The compatible string "fsl,imx8qm-adma" is unused. So remove the
workaround safely.
Signed-off-by: Joy Zou <joy.zou@nxp.com>
---
Changes for v4:
1. adjust the subject to keep consistent with existing patches.
Changes for v3:
1. modify the commit message.
2. remove the unused compatible string "fsl,imx8qm-adma" from allOf property.
---
Documentation/devicetree/bindings/dma/fsl,edma.yaml | 2 --
1 file changed, 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
index 825f4715499e..cf97ea86a7a2 100644
--- a/Documentation/devicetree/bindings/dma/fsl,edma.yaml
+++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
@@ -21,7 +21,6 @@ properties:
- enum:
- fsl,vf610-edma
- fsl,imx7ulp-edma
- - fsl,imx8qm-adma
- fsl,imx8qm-edma
- fsl,imx8ulp-edma
- fsl,imx93-edma3
@@ -92,7 +91,6 @@ allOf:
compatible:
contains:
enum:
- - fsl,imx8qm-adma
- fsl,imx8qm-edma
- fsl,imx93-edma3
- fsl,imx93-edma4
--
2.37.1
next prev parent reply other threads:[~2024-04-17 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 3:26 [PATCH v4 0/2] clean up unused "fsl,imx8qm-adma" compatible string Joy Zou
2024-04-17 3:26 ` [PATCH v4 1/2] dmaengine: fsl-edma: " Joy Zou
2024-04-17 14:40 ` Frank Li
2024-04-18 1:38 ` Joy Zou
2024-04-17 3:26 ` Joy Zou [this message]
2024-04-17 14:45 ` [PATCH v4 2/2] dt-bindings: fsl-dma: " Frank Li
2024-04-18 1:40 ` Joy Zou
2024-04-17 18:53 ` Rob Herring
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=20240417032642.3178669-3-joy.zou@nxp.com \
--to=joy.zou@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox