devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>,
	<krzk+dt@kernel.org>, <robh+dt@kernel.org>,
	<dmitry.baryshkov@linaro.org>, <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>,
	<jens.glathe@oldschoolsolutions.biz>
Subject: Re: [PATCH V3 0/3] X1E001DE Snapdragon Devkit for Windows
Date: Wed, 30 Oct 2024 17:02:32 +0000	[thread overview]
Message-ID: <86y1251q3b.wl-maz@kernel.org> (raw)
In-Reply-To: <20241025123227.3527720-1-quic_sibis@quicinc.com>

On Fri, 25 Oct 2024 13:32:24 +0100,
Sibi Sankar <quic_sibis@quicinc.com> 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
> 
> V3:
> * Asked around and looked at the firmware, couldn't find a codename so
>   will keep it as DEVKIT. Will update it if someone from the community
>   finds something else.

My machine has the following information as part of its DMI tables:

Handle 0x0005, DMI type 1, 27 bytes
System Information
	Manufacturer: Qualcomm
	Product Name: Snapdragon-Devkit
	Version: 2.1
	Serial Number: 5
	UUID: 63b5fc8b-9c50-89aa-fd0f-3fcef93dc291
	Wake-up Type: Power Switch
	SKU Number: 6
	Family: SCP_HAMOA

So I guess that Snapdragon-Devkit is another possible name. But given
that it is a bit of a mouthful, devkit, Devkit, or any other variation
on the case would work for me.

> * Update type c roles as reported by ucsi. [Dmitry]
> * Update THUNDERCOMM to Thundercomm. [Dmitry]
> * Update regulator names and sort Order. [Dmitry]
> * Add x1e001DE devkit to the safe list.
> * Mark regulator-nmve as boot enabled.
> 
> 
> V2:
> * Fix Ghz -> GHz  [Jeff]
> * Pick up Ab tag from Rob.
> * Use Vendor in ADSP/CDSP firmware path [Dmitry]
> * Fix reserved gpios [Dmitry]
> * Only port0 supports DRD update the dt accordingly [Dmitry]
> 
> Sibi Sankar (3):
>   dt-bindings: arm: qcom: Add Snapdragon Devkit for Windows
>   firmware: qcom: uefisecapp: Allow X1E Devkit devices
>   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  | 814 ++++++++++++++++++
>  drivers/firmware/qcom/qcom_scm.c              |   1 +
>  4 files changed, 822 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/qcom/x1e001de-devkit.dts

FWIW, I'm running this as part of my KVM test rig with minor changes
to expose the SMMU and allow the ITS on pcie5, and things work as well
as you can expect. FWIW:

Acked-by: Marc Zyngier <maz@kernel.org>
Tested-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2024-10-30 17:02 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 [this message]
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 ` (subset) " Bjorn Andersson

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=86y1251q3b.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.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=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;
as well as URLs for NNTP newsgroup(s).