From: Pradeep Pragallapati <pradeep.pragallapati@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
vkoul@kernel.org, neil.armstrong@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
martin.petersen@oracle.com, andersson@kernel.org,
konradybcio@kernel.org, taniya.das@oss.qualcomm.com,
dmitry.baryshkov@oss.qualcomm.com
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH V1 3/4] arm64: dts: qcom: hamoa: Add UFS nodes for hamoa SoC
Date: Tue, 30 Dec 2025 14:33:07 +0530 [thread overview]
Message-ID: <28751331-d298-4cd6-b98a-c125e3f75eda@oss.qualcomm.com> (raw)
In-Reply-To: <986facd7-92e7-4d29-a196-d49cd9f3d35f@oss.qualcomm.com>
On 12/29/2025 5:45 PM, Konrad Dybcio wrote:
> On 12/29/25 7:06 AM, Pradeep P V K wrote:
>> Add UFS host controller and PHY nodes for hamoa SoC.
>>
>> Signed-off-by: Pradeep P V K <pradeep.pragallapati@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/hamoa.dtsi | 119 +++++++++++++++++++++++++++-
>> 1 file changed, 118 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/hamoa.dtsi b/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> index bb7c14d473c9..340b907657be 100644
>> --- a/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/hamoa.dtsi
>> @@ -834,7 +834,10 @@ gcc: clock-controller@100000 {
>> <0>,
>> <0>,
>> <0>,
>> - <0>;
>> + <0>,
>> + <&ufs_mem_phy 0>,
>> + <&ufs_mem_phy 1>,
>> + <&ufs_mem_phy 2>;
> This patch cannot be applied as-is (needs GCC bindings changes first)
> which you didn't mention in the cover letter.
>
> If it were picked up, we'd get DTB valdation errors.
ok, i will mention the link to GCC postings in my cover letter in my
next patchset.
>
>>
>> power-domains = <&rpmhpd RPMHPD_CX>;
>> #clock-cells = <1>;
>> @@ -3845,6 +3848,120 @@ pcie4_phy: phy@1c0e000 {
>> status = "disabled";
>> };
>>
>> + ufs_mem_phy: phy@1d80000 {
>> + compatible = "qcom,hamoa-qmp-ufs-phy", "qcom,sm8550-qmp-ufs-phy";
>> + reg = <0x0 0x1d80000 0x0 0x2000>;
> Please pad the address part to 8 hex digits, so 0x1d80000 -> 0x01d80000
>
> [...]
ack. i will update in my next patchset.
>
>> + ufs_mem_hc: ufs@1d84000 {
>> + compatible = "qcom,hamoa-ufshc", "qcom,sm8550-ufshc", "qcom,ufshc",
>> + "jedec,ufs-2.0";
> 1 a line would be neater, perhaps in the node above too
sure, will update in my next patchset.
>
>> + reg = <0x0 0x1d84000 0x0 0x3000>;
> Similar case as before
ack. will update in my next patchset.
>
> lgtm otherwise
>
> Konrad
next prev parent reply other threads:[~2025-12-30 9:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 6:06 [PATCH V1 0/4] Add UFS support for Hamoa SoC Pradeep P V K
2025-12-29 6:06 ` [PATCH V1 1/4] scsi: ufs: phy: dt-bindings: Add QMP UFS PHY compatible for Hamoa Pradeep P V K
2025-12-29 7:11 ` Krzysztof Kozlowski
2025-12-30 9:05 ` Pradeep Pragallapati
2025-12-30 9:38 ` Krzysztof Kozlowski
[not found] ` <d3d63b08-43ba-4b25-a939-416d5d647098@oss.qualcomm.com>
2025-12-30 12:08 ` Krzysztof Kozlowski
2025-12-29 12:26 ` Konrad Dybcio
2025-12-30 9:07 ` Pradeep Pragallapati
2025-12-29 6:06 ` [PATCH V1 2/4] scsi: ufs: qcom: dt-bindings: Add UFSHC " Pradeep P V K
2025-12-29 7:13 ` Krzysztof Kozlowski
2025-12-29 12:20 ` Krzysztof Kozlowski
2025-12-30 8:54 ` Pradeep Pragallapati
2025-12-29 7:35 ` Rob Herring (Arm)
2025-12-29 6:06 ` [PATCH V1 3/4] arm64: dts: qcom: hamoa: Add UFS nodes for hamoa SoC Pradeep P V K
2025-12-29 12:15 ` Konrad Dybcio
2025-12-30 9:03 ` Pradeep Pragallapati [this message]
2025-12-29 6:06 ` [PATCH V1 4/4] arm64: dts: qcom: hamoa-iot-evk: Enable UFS Pradeep P V K
2025-12-29 12:17 ` Konrad Dybcio
2025-12-30 8:58 ` Pradeep Pragallapati
2025-12-30 14:19 ` Konrad Dybcio
2025-12-30 14:48 ` Konrad Dybcio
2025-12-29 20:39 ` [PATCH V1 0/4] Add UFS support for Hamoa SoC Rob Herring
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=28751331-d298-4cd6-b98a-c125e3f75eda@oss.qualcomm.com \
--to=pradeep.pragallapati@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
--cc=vkoul@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