From: Chen-Yu Tsai <wens@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Per Larsson <per@palvencia.se>
Subject: Re: [PATCH 1/2] arm64: dts: allwinner: a523: Add missing SPDIF pin
Date: Tue, 28 Jul 2026 22:40:57 +0800 [thread overview]
Message-ID: <178524965743.668575.17658013610158209404.b4-ty@kernel.org> (raw)
In-Reply-To: <20260720174253.7686-1-per@palvencia.se>
On Mon, 20 Jul 2026 19:42:42 +0200, Per Larsson wrote:
> When spdif support was added for the Allwinner A523 family of SoCs, only
> two of the three possible pins were added to the dtsi, since the third
> would clash with the first ethernet port (emac0)
> However, some devices don't use emac0 and instead use emac1 for the only
> available ethernet port, leaving the pin free to use for spdif.
>
> Add the missing pin to the dtsi so such devices can (later) use it
>
> [...]
Applied to sunxi/dt-for-7.3 in sunxi, thanks!
[1/2] arm64: dts: allwinner: a523: Add missing SPDIF pin
https://git.kernel.org/sunxi/linux/c/3683d4f690b8
[2/2] arm64: dts: allwinner: a523: Add SPDIF to x96qpro+ device
https://git.kernel.org/sunxi/linux/c/35ab38054011
Best regards,
--
Chen-Yu Tsai <wens@kernel.org>
prev parent reply other threads:[~2026-07-28 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 17:42 Per Larsson
2026-07-20 17:42 ` [PATCH 2/2] arm64: dts: allwinner: a523: Add SPDIF to x96qpro+ device Per Larsson
2026-07-20 20:24 ` [PATCH 1/2] arm64: dts: allwinner: a523: Add missing SPDIF pin Andre Przywara
2026-07-28 14:40 ` Chen-Yu Tsai [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=178524965743.668575.17658013610158209404.b4-ty@kernel.org \
--to=wens@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=per@palvencia.se \
--cc=robh@kernel.org \
--cc=samuel@sholland.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
all inboxes | Powered by JetHome®