From: Sibi Sankar <quic_sibis@quicinc.com>
To: <andersson@kernel.org>, <konradybcio@kernel.org>,
<krzk+dt@kernel.org>, <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <conor+dt@kernel.org>,
<abel.vesa@linaro.org>, <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH 0/2] X1E001DE Snapdragon Devkit for Windows
Date: Wed, 23 Oct 2024 16:35:35 +0530 [thread overview]
Message-ID: <f67d0fcd-4940-a57a-0e11-b98ed29cd09d@quicinc.com> (raw)
In-Reply-To: <20240911073337.90577-1-quic_sibis@quicinc.com>
On 9/11/24 13:03, Sibi Sankar wrote:
> Add initial support for X1E001DE Snapdragon Devkit for Windows. X1E001DE
> is the speed binned variant of X1E80100 that supports turbo boost up to
> 4.3 Ghz. The initial support includes the following:
>
> -DSPs
> -Ethernet (RTL8125BG) over the pcie 5 instance.
> -NVme
> -Wifi
> -USB-C ports
>
Hi All,
With the X1E Devkit cancelled and with no firmware updates promised for
it perpetually, please chime in and let me know if you still want to get
this series and rest (external-dp, usb-A ports, sd card slot and 3.5 mm
Jack) merged and have it supported upstream for the folks who already
received it!
-Sibi
> Link: https://www.qualcomm.com/news/releases/2024/05/qualcomm-accelerates-development-for-copilot--pcs-with-snapdrago
>
> Sibi Sankar (2):
> dt-bindings: arm: qcom: Add Snapdragon Devkit for Windows
> arm64: dts: qcom: Add X1E001DE Snapdragon Devkit for Windows
>
> .../devicetree/bindings/arm/qcom.yaml | 6 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> arch/arm64/boot/dts/qcom/x1e001de-devkit.dts | 813 ++++++++++++++++++
> 3 files changed, 820 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/x1e001de-devkit.dts
>
next prev parent reply other threads:[~2024-10-23 11:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 7:33 [PATCH 0/2] X1E001DE Snapdragon Devkit for Windows Sibi Sankar
2024-09-11 7:33 ` [PATCH 1/2] dt-bindings: arm: qcom: Add " Sibi Sankar
2024-09-11 15:44 ` Jeff Johnson
2024-10-05 15:25 ` Sibi Sankar
2024-09-16 17:20 ` Rob Herring (Arm)
2024-09-11 7:33 ` [PATCH 2/2] arm64: dts: qcom: Add X1E001DE " Sibi Sankar
2024-09-11 7:55 ` Dmitry Baryshkov
2024-10-01 2:42 ` Bjorn Andersson
2024-10-01 6:56 ` Dmitry Baryshkov
2024-10-01 8:51 ` Manivannan Sadhasivam
2024-10-05 19:03 ` Sibi Sankar
2024-10-06 17:06 ` Dmitry Baryshkov
2024-10-06 18:01 ` Manivannan Sadhasivam
2024-10-15 13:51 ` Manivannan Sadhasivam
2024-10-15 13:57 ` Dmitry Baryshkov
2024-10-15 15:27 ` Manivannan Sadhasivam
2024-10-16 10:14 ` Dmitry Baryshkov
2024-10-05 18:43 ` Sibi Sankar
2024-10-23 11:05 ` Sibi Sankar [this message]
2024-10-23 20:46 ` [PATCH 0/2] " Rob Clark
2024-10-24 5:13 ` Jens Glathe
2024-10-24 5:30 ` Jens Glathe
2024-10-24 8:14 ` neil.armstrong
2024-10-24 16:02 ` Marc Zyngier
2024-10-24 16:15 ` Johan Hovold
2024-10-24 16:28 ` Marc Zyngier
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=f67d0fcd-4940-a57a-0e11-b98ed29cd09d@quicinc.com \
--to=quic_sibis@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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