Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Justin Suess <utilityemal77@gmail.com>
Cc: 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>,
	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 v2 3/3] arm64: dts: allwinner: a523: enable IR receiver on the X96Q Pro+
Date: Wed, 22 Jul 2026 23:59:25 +0200	[thread overview]
Message-ID: <20260722235925.42c3466b@ryzen.lan> (raw)
In-Reply-To: <20260722201717.2205609-4-utilityemal77@gmail.com>

On Wed, 22 Jul 2026 16:17:17 -0400
Justin Suess <utilityemal77@gmail.com> wrote:

Hi,

> The X96Q Pro+ TV box has an IR receiver window on the front panel,
> wired to the SoC CIR input on PL11.
> 
> Enable the CIR receiver in the RTC power domain and mux its RX
> signal to PL11.
> 
> Tested on an X96 Pro+ with ir-keytable and nec keybindings with
> the remote that it came with in the box.
> 
> Signed-off-by: Justin Suess <utilityemal77@gmail.com>

Confirmed with evtest and some random TV remote.

Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Andre Przywara <andre.przywara@arm.com>

Cheers,
Andre

> ---
>  arch/arm64/boot/dts/allwinner/sun55i-h728-x96qpro+.dts | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/allwinner/sun55i-h728-x96qpro+.dts b/arch/arm64/boot/dts/allwinner/sun55i-h728-x96qpro+.dts
> index a96927fbdadd..1eaee20acaab 100644
> --- a/arch/arm64/boot/dts/allwinner/sun55i-h728-x96qpro+.dts
> +++ b/arch/arm64/boot/dts/allwinner/sun55i-h728-x96qpro+.dts
> @@ -266,6 +266,12 @@ reg_dcdc3_323: dcdc3 {
>  	};
>  };
>  
> +&r_ir {
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&r_ir_rx_pin>;
> +	status = "okay";
> +};
> +
>  &r_pio {
>  /*
>   * Specifying the supply would create a circular dependency.



  reply	other threads:[~2026-07-22 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 20:17 [PATCH v2 0/3] media: rc: sunxi-cir: support the A523/H728/T527 IR receiver Justin Suess
2026-07-22 20:17 ` [PATCH v2 1/3] media: dt-bindings: allwinner,sun4i-a10-ir: add A523 compatible Justin Suess
2026-07-22 20:17 ` [PATCH v2 2/3] arm64: dts: allwinner: a523: add IR receiver nodes Justin Suess
2026-07-22 21:56   ` Andre Przywara
2026-07-22 20:17 ` [PATCH v2 3/3] arm64: dts: allwinner: a523: enable IR receiver on the X96Q Pro+ Justin Suess
2026-07-22 21:59   ` Andre Przywara [this message]
2026-07-22 22:31 ` [PATCH v2 0/3] media: rc: sunxi-cir: support the A523/H728/T527 IR receiver Andre Przywara

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=20260722235925.42c3466b@ryzen.lan \
    --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