From: David Wronek <davidwronek@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Richard Cochran <richardcochran@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, David Wronek <davidwronek@gmail.com>
Subject: [PATCH 0/3] arm64: dts: qcom: sm8250-lenovo-j716f: Add initial device tree
Date: Sun, 27 Nov 2022 18:08:55 +0100 [thread overview]
Message-ID: <20221127170858.440040-1-davidwronek@gmail.com> (raw)
The Lenovo Xiaoxin Pad Pro 2021 is an Android tablet based on Qualcomm
SM8250. The downstream kernel sources have not been released by the
vendor.
Following features are working:
- GPIO keys
- SimpleFB
- UFS
- USB
- Regulators
- I2C
David Wronek (3):
dt-bindings: arm: qcom: Document Lenovo Xiaoxin Pad Pro 2021
arm64: dts: qcom: sm8250-lenovo-j716f: Add initial device tree
arm64: dts: qcom: sm8250-lenovo-j716f: Enable ADSP/CDSP/SLPI
.../devicetree/bindings/arm/qcom.yaml | 1 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../boot/dts/qcom/sm8250-lenovo-j716f.dts | 576 ++++++++++++++++++
3 files changed, 578 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/sm8250-lenovo-j716f.dts
--
2.38.1
next reply other threads:[~2022-11-27 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 17:08 David Wronek [this message]
2022-11-27 17:08 ` [PATCH 1/3] dt-bindings: arm: qcom: Document Lenovo Xiaoxin Pad Pro 2021 David Wronek
2022-11-27 19:00 ` Krzysztof Kozlowski
2022-11-27 17:08 ` [PATCH 2/3] arm64: dts: qcom: sm8250-lenovo-j716f: Add initial device tree David Wronek
2022-11-27 19:03 ` Krzysztof Kozlowski
2022-11-27 17:08 ` [PATCH 3/3] arm64: dts: qcom: sm8250-lenovo-j716f: Enable ADSP/CDSP/SLPI David Wronek
2022-11-27 19:04 ` Krzysztof Kozlowski
2022-11-27 19:16 ` Dmitry Baryshkov
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=20221127170858.440040-1-davidwronek@gmail.com \
--to=davidwronek@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).