From: Sebastian Reichel <sre@kernel.org>
To: Sebastian Reichel <sre@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
imx@lists.linux.dev
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Dong Aisheng <aisheng.dong@nxp.com>,
Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Yackavage <michaely@ips-yes.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v5 5/6] dt-bindings: fsl-imx-sdma: fix HDMI audio index
Date: Mon, 26 Feb 2024 22:26:27 +0100 [thread overview]
Message-ID: <20240226212740.2019837-6-sre@kernel.org> (raw)
In-Reply-To: <20240226212740.2019837-1-sre@kernel.org>
HDMI Audio has been added to the DT binding documentation with an
incorrect index. DT and the driver use index 26. This happened,
because the binding is missing MULTI_SAI type, which is using
index 25.
Reported-by: Michael Yackavage <michaely@ips-yes.com>
Fixes: 7bdbd87d4008 ("dt-bindings: fsl-imx-sdma: Convert imx sdma to DT schema")
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Sebastian Reichel <sre@kernel.org>
---
Documentation/devicetree/bindings/dma/fsl,imx-sdma.yaml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/dma/fsl,imx-sdma.yaml b/Documentation/devicetree/bindings/dma/fsl,imx-sdma.yaml
index b95dd8db5a30..37135fa024f9 100644
--- a/Documentation/devicetree/bindings/dma/fsl,imx-sdma.yaml
+++ b/Documentation/devicetree/bindings/dma/fsl,imx-sdma.yaml
@@ -92,7 +92,8 @@ properties:
description: needs firmware more than ver 2
- Shared ASRC: 23
- SAI: 24
- - HDMI Audio: 25
+ - Multi SAI: 25
+ - HDMI Audio: 26
The third cell: transfer priority ID
enum:
--
2.43.0
next prev parent reply other threads:[~2024-02-26 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 21:26 [PATCH v5 0/6] UNI-T UTi260B support Sebastian Reichel
2024-02-26 21:26 ` [PATCH v5 1/6] dt-bindings: pinctrl: fsl,imx6ul-pinctrl: convert to YAML Sebastian Reichel
2024-02-26 21:26 ` [PATCH v5 2/6] dt-bindings: input: touchscreen: fsl,imx6ul-tsc " Sebastian Reichel
2024-03-05 17:30 ` Dmitry Torokhov
2024-02-26 21:26 ` [PATCH v5 3/6] dt-bindings: soc: imx: fsl,imx-anatop: add binding Sebastian Reichel
2024-02-26 21:26 ` [PATCH v5 4/6] dt-bindings: soc: imx: fsl,imx-iomuxc-gpr: add imx6 Sebastian Reichel
2024-02-26 21:26 ` Sebastian Reichel [this message]
2024-02-26 21:26 ` [PATCH v5 6/6] ARM: dts: imx: Add UNI-T UTi260B thermal camera board Sebastian Reichel
2024-03-28 13:54 ` Shawn Guo
2024-03-05 17:34 ` [PATCH v5 0/6] UNI-T UTi260B support 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=20240226212740.2019837-6-sre@kernel.org \
--to=sre@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michaely@ips-yes.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).