From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm UFS and QMP UFS PHY drivers as built-in
Date: Fri, 17 Apr 2026 10:44:20 +0200 [thread overview]
Message-ID: <c2d7588a-34c7-42de-b809-0733b03d331f@kernel.org> (raw)
In-Reply-To: <aeHxPALfVd7SgtUj@QCOM-aGQu4IUr3Y.na.qualcomm.com>
On 17/04/2026 10:37, Shawn Guo wrote:
> On Fri, Apr 17, 2026 at 10:14:23AM +0200, Krzysztof Kozlowski wrote:
>> On 17/04/2026 05:55, Shawn Guo wrote:
>>> UFS is the primary storage for Linux rootfs across the breadth of
>>> Qualcomm development boards - Mobile, Automotive and IoT. With
>>> Qualcomm UFS host controller driver (SCSI_UFS_QCOM) and the UFS PHY
>>> driver (PHY_QCOM_QMP_UFS) as modules, developers need an initramfs
>>
>> Yes, you always need initramfs and every developer has it.
>>
>>> to boot from UFS, which adds friction to daily development workflows.
>>
>> No friction, it's both standard, easy and all of Qualcomm and Linaro
>> developers have it solved long time ago.
>
> I'm looking at a kernel regression by running git bisect, where kernel
> version string varies for every single boot. How do you usually deal
> with it by using initramfs?
No difference from every other build and boot? I build kernel and the
same step I have initramfs with modules. Whether I bisect or build
kernel for normal boot is exactly the same.
The only difference is `git bisect good`.
>
> If using initramfs is standard and easy, I wonder why Qualcomm QLI
> (meta-qcom) kernel has UFS drivers as built-in.
This I don't know. Distros do various things, but of course there might
be an argument I do not know (e.g. like it was why distros do not make
IPV6 a module).
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-17 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 3:55 [PATCH] arm64: defconfig: Enable Qualcomm UFS and QMP UFS PHY drivers as built-in Shawn Guo
2026-04-17 8:14 ` Krzysztof Kozlowski
2026-04-17 8:37 ` Shawn Guo
2026-04-17 8:44 ` Krzysztof Kozlowski [this message]
2026-04-17 10:37 ` Shawn Guo
2026-04-17 12:57 ` Krzysztof Kozlowski
2026-04-17 22:59 ` Dmitry Baryshkov
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=c2d7588a-34c7-42de-b809-0733b03d331f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=shengchao.guo@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