public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Chen-Yu Tsai <wens@csie.org>,
	Samuel Holland <samuel@sholland.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Andre Przywara <andre.przywara@arm.com>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
	Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
Subject: Re: [PATCH v2 0/2] arm64: dts: allwinner: Add Tanix TX1 support
Date: Sun, 21 Apr 2024 22:11:13 +0200	[thread overview]
Message-ID: <13495191.uLZWGnKmhe@jernej-laptop> (raw)
In-Reply-To: <20240418104942.1556914-1-andre.przywara@arm.com>

Dne četrtek, 18. april 2024 ob 12:49:40 GMT +2 je Andre Przywara napisal(a):
> v2 just removes the premature OPP header inclusion, and adds tags,
> otherwise it's the same as the previous post. Based on sunxi/for-next.
> 
> ==================
> Tanix TX1 is a tiny TV box (60% of a credit card) with an Allwinner
> H313 SoC. This seems to be the same as the H616, just the "bad bin"
> version, limited to 1.3 GHz.
> The box has no Ethernet or SD card slot, which makes booting from it
> somewhat interesting: Pressing the hidden FEL button and using a USB-A
> to USB-A cable to upload code from a host PC is one way to run mainline.
> The box features a minimal set of peripherals: one USB port, 8 or 16GB
> of eMMC, an HDMI port and an (unsupported) SCI S9082H WiFi chip.
> 
> Patch 1 adds the DT binding for the board compatible, I refrained from
> using the H313 name here, since it seems to be functionally identical to
> the H616.
> Patch 2 adds the devicetree.
> 
> There is a blue and a red LED, both connected to the same GPIO pin, but
> with different polarities, so it's only either one of them enabled.
> I did not find a way to describe this in DT, so I omitted the red LED.
> 
> Please have a look!

Applied, thanks!

Best regards,
Jernej

> 
> Cheers,
> Andre
> 
> Changelog v1 .. v2:
> - add tags
> - remove premature opp.dtsi inclusion
> 
> Andre Przywara (2):
>   dt-bindings: arm: sunxi: document Tanix TX1 name
>   arm64: dts: allwinner: Add Tanix TX1 support
> 
>  .../devicetree/bindings/arm/sunxi.yaml        |   5 +
>  arch/arm64/boot/dts/allwinner/Makefile        |   1 +
>  .../dts/allwinner/sun50i-h313-tanix-tx1.dts   | 183 ++++++++++++++++++
>  3 files changed, 189 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h313-tanix-tx1.dts
> 
> 





      parent reply	other threads:[~2024-04-21 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 10:49 [PATCH v2 0/2] arm64: dts: allwinner: Add Tanix TX1 support Andre Przywara
2024-04-18 10:49 ` [PATCH v2 1/2] dt-bindings: arm: sunxi: document Tanix TX1 name Andre Przywara
2024-04-18 10:49 ` [PATCH v2 2/2] arm64: dts: allwinner: Add Tanix TX1 support Andre Przywara
2024-04-21 20:11 ` Jernej Škrabec [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=13495191.uLZWGnKmhe@jernej-laptop \
    --to=jernej.skrabec@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=piotr.oniszczuk@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox