From: Andre Przywara <andre.przywara@arm.com>
To: "J. Neuschäfer via B4 Relay" <devnull+j.ne.posteo.net@kernel.org>
Cc: j.ne@posteo.net, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Maxime Ripard <mripard@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Initial Amediatech X96Q support based on Allwinner H313
Date: Fri, 12 Sep 2025 11:02:22 +0100 [thread overview]
Message-ID: <20250912110222.5e4153ec@donnerap> (raw)
In-Reply-To: <20250912-x96q-v1-0-8471daaf39db@posteo.net>
On Fri, 12 Sep 2025 01:52:08 +0200
J. Neuschäfer via B4 Relay <devnull+j.ne.posteo.net@kernel.org> wrote:
Hi,
> This patchset adds an initial devicetree for the X96Q set-top box.
> WiFi, Ethernet, and HDMI depend on drivers that are currently not
> available in mainline Linux, and I didn't enable them in the devicetree.
> The builtin infrared receiver produces IRQs when a nearby remote sends
> events, but I have not checked whether the events are decoded correctly.
You can either do a simple "cat /dev/input/event<x>", then check whether
keypresses generate (unreadable) output, or you use the "evtest" tool to
decode some information:
https://cgit.freedesktop.org/evtest/
But I guess if you see interrupts consistent with remote keypresses, it's
a good enough indication it should work.
Cheers,
Andre
>
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> J. Neuschäfer (2):
> dt-bindings: arm: sunxi: Add Amediatech X96Q
> arm64: dts: allwinner: h313: Add Amediatech X96Q
>
> Documentation/devicetree/bindings/arm/sunxi.yaml | 5 +
> arch/arm64/boot/dts/allwinner/Makefile | 1 +
> arch/arm64/boot/dts/allwinner/sun50i-h313-x96q.dts | 235 +++++++++++++++++++++
> 3 files changed, 241 insertions(+)
> ---
> base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> change-id: 20250911-x96q-57e63380804e
>
> Best regards,
next prev parent reply other threads:[~2025-09-12 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 23:52 [PATCH 0/2] Initial Amediatech X96Q support based on Allwinner H313 J. Neuschäfer
2025-09-11 23:52 ` J. Neuschäfer via B4 Relay
2025-09-11 23:52 ` [PATCH 1/2] dt-bindings: arm: sunxi: Add Amediatech X96Q J. Neuschäfer
2025-09-11 23:52 ` J. Neuschäfer via B4 Relay
2025-09-12 10:04 ` Andre Przywara
2025-09-15 21:01 ` Rob Herring (Arm)
2025-09-11 23:52 ` [PATCH 2/2] arm64: dts: allwinner: h313: " J. Neuschäfer
2025-09-11 23:52 ` J. Neuschäfer via B4 Relay
2025-09-12 8:54 ` J. Neuschäfer
2025-09-12 8:56 ` Chen-Yu Tsai
2025-09-15 11:16 ` J. Neuschäfer
2025-09-12 9:54 ` Andre Przywara
2025-09-13 9:36 ` Chen-Yu Tsai
2025-09-15 18:36 ` J. Neuschäfer
2025-09-15 13:40 ` J. Neuschäfer
2025-09-15 14:09 ` Andre Przywara
2025-09-12 10:02 ` Andre Przywara [this message]
2025-09-15 19:00 ` [PATCH 0/2] Initial Amediatech X96Q support based on Allwinner H313 J. Neuschäfer
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=20250912110222.5e4153ec@donnerap \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+j.ne.posteo.net@kernel.org \
--cc=j.ne@posteo.net \
--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=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.