From: Krzysztof Kozlowski <krzk@kernel.org>
To: Taniya Das <taniya.das@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Change CONFIG_SM_TCSRCC_8750 from m to y
Date: Fri, 17 Oct 2025 06:30:53 +0200 [thread overview]
Message-ID: <30390038-0f90-48a4-befe-475cf88ba1fb@kernel.org> (raw)
In-Reply-To: <20251017-update_defconfig_tcsrcc_sm8750-v1-1-34b1b47a0bda@oss.qualcomm.com>
On 16/10/2025 20:53, Taniya Das wrote:
> The TCSR clock controller is required during boot to provide the ref
> clocks to the UFS controller. Setting CONFIG_SM_TCSRCC_8750 to y ensures
> the UFS driver successfully probe and initialize the device.
>
> Without this change, the UFS subsystem fails to mount as a usable file
> system during boot.
That's not what I observed. UFS works fine, especially that it is a
module, so no, this is not a desired change and explanation is not only
insufficient but actually incorrect.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-17 4:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:53 [PATCH] arm64: defconfig: Change CONFIG_SM_TCSRCC_8750 from m to y Taniya Das
2025-10-17 4:30 ` Krzysztof Kozlowski [this message]
2025-10-17 5:16 ` Taniya Das
2025-10-17 5:21 ` Krzysztof Kozlowski
2025-10-17 5:49 ` Taniya Das
2025-10-17 5:56 ` Krzysztof Kozlowski
2025-10-17 6:54 ` Krzysztof Kozlowski
2025-10-17 6:57 ` Taniya Das
2025-10-17 7:37 ` Krzysztof Kozlowski
2025-10-17 8:15 ` Konrad Dybcio
2025-10-17 8:34 ` Krzysztof Kozlowski
2025-10-17 6:55 ` Taniya Das
2025-10-17 7:36 ` Krzysztof Kozlowski
2025-10-17 21:47 ` Bjorn Andersson
2025-10-17 21:41 ` Bjorn Andersson
2025-10-21 9:12 ` Taniya Das
2025-10-19 11:57 ` Dmitry Baryshkov
2025-10-21 9:15 ` Taniya Das
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=30390038-0f90-48a4-befe-475cf88ba1fb@kernel.org \
--to=krzk@kernel.org \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taniya.das@oss.qualcomm.com \
/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