From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
Bart Van Assche <bvanassche@acm.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
Subject: Re: [PATCH v2 3/3] dt-bindings: ufs: qcom: Split SM8650 and similar
Date: Fri, 1 Aug 2025 16:21:55 +0200 [thread overview]
Message-ID: <8eee4b1c-2965-41e9-9f8f-f771b1af3beb@kernel.org> (raw)
In-Reply-To: <l733rhzqpl5guulziufwgewp6ljv4vhekcnvlqh4baycvqnwd4@ywcexv3racyc>
On 01/08/2025 14:28, Manivannan Sadhasivam wrote:
> On Thu, Jul 31, 2025 at 09:15:54AM GMT, Krzysztof Kozlowski wrote:
>> The binding for Qualcomm SoC UFS controllers grew and it will grow
>> further. Split SM8650 and SM8750 UFS controllers which:
>> 1. Do not reference ICE as IO address space, but as phandle,
>> 2. Have same order of clocks.
>> 3. Have MCQ IO address space. Document that MCQ address space as
>> optional to maintain backwards compatibility and because Linux
>> drivers can operate perfectly fine without it (thus without MCQ
>> feature). Linux driver already uses "mcq" as possible name for
>> "reg-names" property.
>
> Since Qcom SoC memory maps have holes and shared registers in the whole 'mcq'
> region, it is preferred to map only the required parts. So please drop 'mcq' and
> add 'mcq_sqd', 'mcq_vs' regions.
No, it is not preferred. The docs are clearly stating that there is oone
address space for MCQ and continuous.
We have been fixing above approach you propose also for other devices,
so this should not go to the broken part.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-01 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 7:15 [PATCH v2 0/3] dt-bindings: ufs: qcom: Split SC7180, SM8650 and similar into separate file Krzysztof Kozlowski
2025-07-31 7:15 ` [PATCH v2 1/3] dt-bindings: ufs: qcom: Split common part to qcom,ufs-common.yaml Krzysztof Kozlowski
2025-07-31 17:31 ` Rob Herring (Arm)
2025-07-31 7:15 ` [PATCH v2 2/3] dt-bindings: ufs: qcom: Split SC7180 and similar Krzysztof Kozlowski
2025-07-31 17:33 ` Rob Herring (Arm)
2025-07-31 7:15 ` [PATCH v2 3/3] dt-bindings: ufs: qcom: Split SM8650 " Krzysztof Kozlowski
2025-07-31 17:34 ` Rob Herring (Arm)
2025-08-01 12:28 ` Manivannan Sadhasivam
2025-08-01 14:21 ` Krzysztof Kozlowski [this message]
2025-08-06 2:37 ` [PATCH v2 0/3] dt-bindings: ufs: qcom: Split SC7180, SM8650 and similar into separate file Martin K. Petersen
2025-08-06 5:58 ` Krzysztof Kozlowski
2025-08-14 14:27 ` Krzysztof Kozlowski
2025-08-14 19:00 ` Martin K. Petersen
2025-08-15 3:13 ` Martin K. Petersen
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=8eee4b1c-2965-41e9-9f8f-f771b1af3beb@kernel.org \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--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=krzysztof.kozlowski@linaro.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=quic_rdwivedi@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
all inboxes | Powered by JetHome®