From: Samuel Holland <samuel@sholland.org>
To: Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Samuel Holland <samuel@sholland.org>
Subject: [PATCH 0/2] iNet U70B Rev 01 Tablet Support
Date: Thu, 29 Dec 2022 16:45:45 -0600 [thread overview]
Message-ID: <20221229224547.25225-1-samuel@sholland.org> (raw)
This series adds a binding and devicetree for yet another A33-based
tablet board. The devicetree currently fails validation because I have
no idea what compatible string to use for the DPI panel. Neither the
hardware nor the software provide any clues about a manufacturer or
model -- the driver used by the vendor Android is called "default_lcd".
Link: https://linux-sunxi.org/Inet_U70B
Samuel Holland (2):
dt-bindings: arm: sunxi: Add iNet U70B Rev 01 Tablet
ARM: dts: sun8i: A33: Add iNet U70B Rev 01
.../devicetree/bindings/arm/sunxi.yaml | 5 +
arch/arm/boot/dts/Makefile | 1 +
.../boot/dts/sun8i-a33-inet-u70b-rev01.dts | 172 ++++++++++++++++++
3 files changed, 178 insertions(+)
create mode 100644 arch/arm/boot/dts/sun8i-a33-inet-u70b-rev01.dts
--
2.37.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-12-29 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 22:45 Samuel Holland [this message]
2022-12-29 22:45 ` [PATCH 1/2] dt-bindings: arm: sunxi: Add iNet U70B Rev 01 Tablet Samuel Holland
2022-12-30 7:53 ` Krzysztof Kozlowski
2022-12-29 22:45 ` [PATCH 2/2] ARM: dts: sun8i: A33: Add iNet U70B Rev 01 Samuel Holland
2023-01-08 20:08 ` [PATCH 0/2] iNet U70B Rev 01 Tablet Support Jernej Škrabec
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=20221229224547.25225-1-samuel@sholland.org \
--to=samuel@sholland.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=robh+dt@kernel.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