From: Andre Przywara <andre.przywara@arm.com>
To: Justin Suess <utilityemal77@gmail.com>,
Sean Young <sean@mess.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Ripard <mripard@kernel.org>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH 3/4] arm64: dts: allwinner: a523: add IR receiver node
Date: Mon, 6 Jul 2026 11:21:29 +0200 [thread overview]
Message-ID: <97a674a3-4833-4aa6-a9a2-3ab5472ee4b3@arm.com> (raw)
In-Reply-To: <20260702214750.3428694-4-utilityemal77@gmail.com>
Hi Justin,
I checked the numbers below against the manual, they match up: MMIO base
address, interrupt number, clocks and resets.
One thing I figured is that the A523/T527 contains another CIR-RX
instance, in the "CPUX" domain. That's used for instance on the
Avaota-A1. So we need another node describing this instance.
Some more below...
On 7/2/26 23:47, Justin Suess wrote:
> The A523 has a CIR receiver in the RTC power domain, clocked from the
> R-CCU, with its RX signal available on PL11.
>
> Clock the module directly from the 24 MHz host oscillator; the driver
> selects a /256 sample divider on this SoC, giving a sample period
> close to the legacy 8 MHz / 64 configuration of older SoCs.
>
> Keep the node disabled by default; boards with an IR receiver can
> enable it.
>
> Signed-off-by: Justin Suess <utilityemal77@gmail.com>
> ---
> .../arm64/boot/dts/allwinner/sun55i-a523.dtsi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi b/arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi
> index ca6a16807049..5e46c4b1ee61 100644
> --- a/arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun55i-a523.dtsi
> @@ -927,6 +927,25 @@ r_i2c_pins: r-i2c-pins {
> allwinner,pinmux = <2>;
> function = "r_i2c0";
> };
> +
> + r_ir_rx_pin: r-ir-rx-pin {
> + pins = "PL11";
> + allwinner,pinmux = <2>;
> + function = "s_cir";
> + };
> + };
> +
> + r_ir: ir@7040000 {
> + compatible = "allwinner,sun55i-a523-ir";
As mentioned in the other email, I think we can use the fallback
compatible, so add this here.
> + reg = <0x07040000 0x400>;
> + interrupts = <GIC_SPI 167 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&r_ccu CLK_BUS_R_IR_RX>, <&r_ccu CLK_R_IR_RX>;
> + clock-names = "apb", "ir";
> + clock-frequency = <24000000>;
As said in the other email, I think this property is misnamed and
misleading, just drop it, and let the driver select the sample rate.
> + resets = <&r_ccu RST_BUS_R_IR_RX>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&r_ir_rx_pin>;
There is another pin which carries the R-IR-RX signal, on pin PM8. In
those cases we do not add the pinctrl properties to the .dtsi DT node,
but let each board add it, right next to where they enable the IP.
So please drop those two lines from here.
Cheers,
Andre
> + status = "disabled";
> };
>
> pck600: power-controller@7060000 {
next prev parent reply other threads:[~2026-07-06 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 21:47 [PATCH 0/4] media: rc: sunxi-cir: support the A523/H728/T527 IR receiver Justin Suess
2026-07-02 21:47 ` [PATCH 1/4] media: dt-bindings: allwinner,sun4i-a10-ir: add A523 compatible Justin Suess
2026-07-03 10:56 ` Krzysztof Kozlowski
2026-07-03 19:50 ` Justin Suess
2026-07-05 9:22 ` Krzysztof Kozlowski
2026-07-02 21:47 ` [PATCH 2/4] media: rc: sunxi-cir: add support for the A523 Justin Suess
2026-07-03 9:11 ` Andre Przywara
2026-07-03 19:47 ` Justin Suess
2026-07-06 9:23 ` Andre Przywara
2026-07-02 21:47 ` [PATCH 3/4] arm64: dts: allwinner: a523: add IR receiver node Justin Suess
2026-07-06 9:21 ` Andre Przywara [this message]
2026-07-02 21:47 ` [PATCH 4/4] arm64: dts: allwinner: a523: enable IR receiver on the X96Q Pro+ Justin Suess
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=97a674a3-4833-4aa6-a9a2-3ab5472ee4b3@arm.com \
--to=andre.przywara@arm.com \
--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-media@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=sashiko-bot@kernel.org \
--cc=sean@mess.org \
--cc=utilityemal77@gmail.com \
--cc=wens@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