From: Bjorn Andersson <andersson@kernel.org>
To: konradybcio@kernel.org, krzk+dt@kernel.org, robh+dt@kernel.org,
dmitry.baryshkov@linaro.org, Sibi Sankar <quic_sibis@quicinc.com>
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,
quic_jjohnson@quicinc.com, maz@kernel.org,
jens.glathe@oldschoolsolutions.biz
Subject: Re: (subset) [PATCH V3 0/3] X1E001DE Snapdragon Devkit for Windows
Date: Tue, 5 Nov 2024 16:53:48 -0800 [thread overview]
Message-ID: <173085441663.26510.11025364605092025731.b4-ty@kernel.org> (raw)
In-Reply-To: <20241025123227.3527720-1-quic_sibis@quicinc.com>
On Fri, 25 Oct 2024 18:02:24 +0530, 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
>
> [...]
Applied, thanks!
[2/3] firmware: qcom: uefisecapp: Allow X1E Devkit devices
commit: 75837f0b2bc61c62c8326fe3a1eb9a100714cfd7
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-11-06 0:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 12:32 [PATCH V3 0/3] X1E001DE Snapdragon Devkit for Windows Sibi Sankar
2024-10-25 12:32 ` [PATCH V3 1/3] dt-bindings: arm: qcom: Add " Sibi Sankar
2024-10-25 12:32 ` [PATCH V3 2/3] firmware: qcom: uefisecapp: Allow X1E Devkit devices Sibi Sankar
2024-10-25 12:32 ` [PATCH V3 3/3] arm64: dts: qcom: Add X1E001DE Snapdragon Devkit for Windows Sibi Sankar
2024-11-04 11:25 ` Konrad Dybcio
2024-10-25 13:55 ` [PATCH V3 0/3] " Rob Herring (Arm)
2024-10-27 20:42 ` Jens Glathe
2024-10-30 17:02 ` Marc Zyngier
2024-10-31 9:46 ` Abel Vesa
2024-10-31 10:00 ` Jens Glathe
2024-10-31 12:29 ` Marc Zyngier
2024-10-31 13:34 ` Jens Glathe
2024-11-06 0:53 ` Bjorn Andersson [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=173085441663.26510.11025364605092025731.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_sibis@quicinc.com \
--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