[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <962d6db3-af85-45b9-9c1d-5369847dcfb4@kernel.org>
Date: Thu, 24 Jul 2025 09:48:02 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ram Kumar Dwivedi <quic_rdwivedi@...cinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: mani@...nel.org, alim.akhtar@...sung.com, avri.altman@....com,
bvanassche@....org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, andersson@...nel.org, konradybcio@...nel.org,
James.Bottomley@...senpartnership.com, martin.petersen@...cle.com,
agross@...nel.org, linux-arm-msm@...r.kernel.org,
linux-scsi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: ufs: qcom: Document HS gear and rate
limit properties
On 24/07/2025 09:36, Ram Kumar Dwivedi wrote:
>>> GPIO connected to the RESET pin of the UFS memory device.
>>>
>>> + limit-hs-gear:
>>
>> If the properties are generic, they should go to the ufs-common.yaml. If
>> not (but why?), then they should be prefixed with 'qcom,' prefix, as
>> usual.
>
> Hi Dmitry,
>
> I have added qcom prefix in latest patchset.
Unlike this patchset here, are you going to test before sending it?
Best regards,
Krzysztof
Powered by blists - more mailing lists