From: Ram Kumar Dwivedi <ram.dwivedi@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: mani@kernel.org, alim.akhtar@samsung.com, avri.altman@wdc.com,
bvanassche@acm.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, James.Bottomley@hansenpartnership.com,
martin.petersen@oracle.com, quic_ahari@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V1 2/3] dt-bindings: ufs: Document bindings for SA8255P UFS Host Controller
Date: Wed, 10 Dec 2025 21:22:27 +0530 [thread overview]
Message-ID: <bd2d11b0-c4fb-418c-9a0e-7f5d63bbed8c@oss.qualcomm.com> (raw)
In-Reply-To: <p6a5nazgd74fwbo6c3ctgvwifcigwwn4azkiu7nrmovrn5cmqn@nxzryxyx4oao>
On 15-Nov-25 1:02 AM, Bjorn Andersson wrote:
> On Fri, Nov 14, 2025 at 08:26:45PM +0530, Ram Kumar Dwivedi wrote:
>> From: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>>
>> Document the device tree bindings for UFS host controller on
>> Qualcomm SA8255P platform which integrates firmware-managed
>> resources.
>>
>> The platform firmware implements the SCMI server and manages
>> resources such as the PHY, clocks, regulators and resets via the
>> SCMI power protocol. As a result, the OS-visible DT only describes
>> the controller’s MMIO, interrupt, IOMMU and power-domain interfaces.
>>
>> The generic "qcom,ufshc" and "jedec,ufs-2.0" compatible strings are
>> removed from the binding, since this firmware managed design won't
>> be compatible with the drivers doing full resource management.
>>
>> Co-developed-by: Anjana Hari <quic_ahari@quicinc.com>
>> Signed-off-by: Anjana Hari <quic_ahari@quicinc.com>
>> Signed-off-by: Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
>> ---
>> .../bindings/ufs/qcom,sa8255p-ufshc.yaml | 63 +++++++++++++++++++
>> 1 file changed, 63 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml b/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
>> new file mode 100644
>> index 000000000000..3b31f6282feb
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
>> @@ -0,0 +1,63 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/ufs/qcom,sa8255p-ufshc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Qualcomm SA8255P UFS Host Controller
>> +
>> +maintainers:
>> + - Ram Kumar Dwivedi <ram.dwivedi@oss.qualcomm.com>
>> + - Anjana Hari <quic_ahari@quicinc.com>
>
> This should be @oss.qualcomm.com, or @qti.qualcomm.com, not
> @quicinc.com.
Hi Bjorn,
Thanks for pointing this out. I’ve updated this in the
latest patchset.
Thanks,
Ram.
>
>> +
>> +properties:
>> + compatible:
>> + const: qcom,sa8255p-ufshc
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + iommus:
>> + maxItems: 1
>> +
>> + dma-coherent:
>> + type: boolean
>> +
>> + power-domains:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - power-domains
>> + - iommus
>> + - dma-coherent
>> +
>> +allOf:
>> + - $ref: ufs-common.yaml
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> +
>> + soc {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> +
>> + ufshc@1d84000 {
>> + compatible = "qcom,sa8255p-ufshc";
>> + reg = <0x0 0x01d84000 0x0 0x3000>;
>
> Drop the two 0x0 and you don't need to change address/size-cells.
>
> Regards,
> Bjorn
>
>> + interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>;
>> + lanes-per-direction = <2>;
>> +
>> + iommus = <&apps_smmu 0x100 0x0>;
>> + power-domains = <&scmi3_pd 0>;
>> + dma-coherent;
>> + };
>> + };
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2025-12-10 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 14:56 [PATCH V1 0/3] ufs: ufs-qcom: Add support firmware managed platforms Ram Kumar Dwivedi
2025-11-14 14:56 ` [PATCH V1 1/3] MAINTAINERS: broaden UFS Qualcomm binding file pattern Ram Kumar Dwivedi
2025-11-19 8:21 ` Dmitry Baryshkov
2025-11-20 5:48 ` Manivannan Sadhasivam
2025-11-14 14:56 ` [PATCH V1 2/3] dt-bindings: ufs: Document bindings for SA8255P UFS Host Controller Ram Kumar Dwivedi
2025-11-14 19:32 ` Bjorn Andersson
2025-12-10 15:52 ` Ram Kumar Dwivedi [this message]
2025-12-10 15:56 ` Ram Kumar Dwivedi
2025-12-11 6:30 ` Krzysztof Kozlowski
2025-11-15 11:55 ` Krzysztof Kozlowski
2025-12-10 15:47 ` Ram Kumar Dwivedi
2025-11-14 14:56 ` [PATCH V1 3/3] ufs: ufs-qcom: Add support for firmware-managed resource abstraction Ram Kumar Dwivedi
2025-11-20 5:53 ` Manivannan Sadhasivam
2025-12-10 16:03 ` Ram Kumar Dwivedi
2025-12-12 0:45 ` Manivannan Sadhasivam
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=bd2d11b0-c4fb-418c-9a0e-7f5d63bbed8c@oss.qualcomm.com \
--to=ram.dwivedi@oss.qualcomm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_ahari@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;
as well as URLs for NNTP newsgroup(s).