From: Conor Dooley <conor@kernel.org>
To: Alexey Charkov <alchark@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF
Date: Tue, 21 Jan 2025 17:37:57 +0000 [thread overview]
Message-ID: <20250121-spruce-lushness-28295dd0c1ed@spud> (raw)
In-Reply-To: <20250120-rk3588-spdif-v1-1-1415f5871dc7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
On Mon, Jan 20, 2025 at 01:01:27PM +0400, Alexey Charkov wrote:
> Add a compatible string for SPDIF on RK3588, which is similar to the
> one on RK3568.
>
> Signed-off-by: Alexey Charkov <alchark@gmail.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-21 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 9:01 [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588 Alexey Charkov
2025-01-20 9:01 ` [PATCH 1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF Alexey Charkov
2025-01-21 17:37 ` Conor Dooley [this message]
2025-02-09 21:10 ` Heiko Stübner
2025-02-10 13:20 ` Mark Brown
2025-02-10 14:04 ` Heiko Stübner
2025-02-10 14:28 ` Mark Brown
2025-01-20 9:01 ` [PATCH 2/3] arm64: dts: rockchip: Add SPDIF nodes to RK3588(s) device trees Alexey Charkov
2025-01-20 9:01 ` [PATCH 3/3] arm64: dts: rockchip: Enable SPDIF output on H96 Max V58 Alexey Charkov
2025-02-10 18:06 ` (subset) [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588 Mark Brown
2025-02-11 9:28 ` Heiko Stuebner
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=20250121-spruce-lushness-28295dd0c1ed@spud \
--to=conor@kernel.org \
--cc=alchark@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox