From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/5] arm64: dts: qcom: eliza: Add CQS SoM UFS variant
Date: Thu, 22 Oct 2026 11:15:29 +0200 [thread overview]
Message-ID: <560a1b2b-d7b5-4c7e-871c-f98d06cf088e@oss.qualcomm.com> (raw)
In-Reply-To: <20260928-dts-qcom-eliza-add-ufs-variant-v3-4-9a2fdbf6baf2@oss.qualcomm.com>
On 9/28/26 6:36 PM, Abel Vesa wrote:
> The UFS-equipped Eliza CQS SoM is not described by the existing eMMC
> variant. Its storage uses the UFS controller and PHY instead of SDHCI,
> and the vreg_l1d supply needs a 1.14-1.26 V constraint instead of 1.8 V.
> These differences are on the SoM; both variants use the same EVK carrier.
>
> Describe the UFS controller, PHY supplies and reset GPIO in a dedicated
> SoM include, along with the variant-specific vreg_l1d voltage constraint.
> Include eliza-cqs-som.dtsi for the shared hardware so neither storage
> variant duplicates it or inherits the other's storage configuration.
>
> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-10-22 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:36 [PATCH v3 0/5] arm64: dts: qcom: eliza-cqs-evk: Support eMMC and UFS SoMs Abel Vesa
2026-09-28 16:36 ` [PATCH v3 1/5] dt-bindings: arm: qcom: Describe Eliza CQS eMMC and UFS variants Abel Vesa
2026-09-28 16:36 ` [PATCH v3 2/5] arm64: dts: qcom: eliza-cqs-evk: Move sound card support to Eliza EVK generic Abel Vesa
2026-09-28 16:36 ` [PATCH v3 3/5] arm64: dts: qcom: eliza: Separate common CQS SoM and eMMC configuration Abel Vesa
2026-10-22 9:15 ` Konrad Dybcio
2026-09-28 16:36 ` [PATCH v3 4/5] arm64: dts: qcom: eliza: Add CQS SoM UFS variant Abel Vesa
2026-10-22 9:15 ` Konrad Dybcio [this message]
2026-09-28 16:36 ` [PATCH v3 5/5] arm64: dts: qcom: eliza: Add CQS EVK " Abel Vesa
2026-10-22 9:15 ` Konrad Dybcio
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=560a1b2b-d7b5-4c7e-871c-f98d06cf088e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abelvesa@kernel.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=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®