From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wasim Nazir <quic_wasimn@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com,
kernel@oss.qualcomm.com,
Sayali Lokhande <quic_sayalil@quicinc.com>
Subject: Re: [PATCH v7 6/6] arm64: dts: qcom: Add UFS support for qcs9075 IQ-9075-EVK
Date: Wed, 21 May 2025 16:23:02 +0200 [thread overview]
Message-ID: <585d1751-a909-442d-986e-88721a093ec8@kernel.org> (raw)
In-Reply-To: <b9ecd0c9-c8fd-45e6-b2ff-6ccb72bdfd49@kernel.org>
On 21/05/2025 16:21, Krzysztof Kozlowski wrote:
> On 21/05/2025 16:08, Wasim Nazir wrote:
>> From: Sayali Lokhande <quic_sayalil@quicinc.com>
>>
>> Add UFS support for qcs9075 IQ-9075-EVK board.
>>
>> Signed-off-by: Sayali Lokhande <quic_sayalil@quicinc.com>
>> Signed-off-by: Wasim Nazir <quic_wasimn@quicinc.com>
>> ---
>> .../arm64/boot/dts/qcom/qcs9075-iq-9075-evk.dts | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs9075-iq-9075-evk.dts b/arch/arm64/boot/dts/qcom/qcs9075-iq-9075-evk.dts
>> index 30a36ffa40be..ba8a359d8fee 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs9075-iq-9075-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/qcs9075-iq-9075-evk.dts
>> @@ -276,3 +276,20 @@ &uart10 {
>> &xo_board_clk {
>> clock-frequency = <38400000>;
>> };
>> +
>> +&ufs_mem_hc {
>
> Please follow DTS coding style.
And you just added this file. Squash the patches so you will see the
mishap in ordering.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-21 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 14:07 [PATCH v7 0/6] qcom: Add support for IQ-9075-evk board Wasim Nazir
2025-05-21 14:08 ` [PATCH v7 1/6] dt-bindings: arm: qcom: Add bindings for QCS9075 SOC based board Wasim Nazir
2025-05-21 14:20 ` Krzysztof Kozlowski
2025-05-21 15:35 ` Wasim Nazir
2025-05-21 16:26 ` Krzysztof Kozlowski
2025-05-21 19:18 ` Wasim Nazir
2025-05-21 14:08 ` [PATCH v7 2/6] arm64: dts: qcom: iq9: Introduce new memory map for qcs9100/qcs9075 Wasim Nazir
2025-05-21 14:08 ` [PATCH v7 3/6] arm64: dts: qcom: qcs9075: Introduce QCS9075 SOM Wasim Nazir
2025-05-21 14:08 ` [PATCH v7 4/6] arm64: dts: qcom: Add support for qcs9075 IQ-9075-EVK Wasim Nazir
2025-05-21 16:57 ` Konrad Dybcio
2025-05-21 19:29 ` Wasim Nazir
2025-05-21 14:08 ` [PATCH v7 5/6] arm64: dts: qcom: Add support L4C LDO " Wasim Nazir
2025-05-21 14:21 ` Krzysztof Kozlowski
2025-05-21 14:08 ` [PATCH v7 6/6] arm64: dts: qcom: Add UFS support " Wasim Nazir
2025-05-21 14:21 ` Krzysztof Kozlowski
2025-05-21 14:23 ` Krzysztof Kozlowski [this message]
2025-05-21 15:44 ` Wasim Nazir
2025-05-21 14:33 ` Dmitry Baryshkov
2025-05-21 15:38 ` Wasim Nazir
2025-05-22 18:54 ` [PATCH v7 0/6] qcom: Add support for IQ-9075-evk board Rob Herring (Arm)
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=585d1751-a909-442d-986e-88721a093ec8@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_sayalil@quicinc.com \
--cc=quic_wasimn@quicinc.com \
--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