mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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 16:37:16 +0800	[thread overview]
Message-ID: <aeHxPALfVd7SgtUj@QCOM-aGQu4IUr3Y.na.qualcomm.com> (raw)
In-Reply-To: <898874b3-fb73-4a46-b440-6ea3377c2f2d@kernel.org>

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?

If using initramfs is standard and easy, I wonder why Qualcomm QLI
(meta-qcom) kernel has UFS drivers as built-in.

Shawn

  reply	other threads:[~2026-04-17  8:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  3:55 Shawn Guo
2026-04-17  8:14 ` Krzysztof Kozlowski
2026-04-17  8:37   ` Shawn Guo [this message]
2026-04-17  8:44     ` Krzysztof Kozlowski
2026-04-17 10:37       ` Shawn Guo
2026-04-17 12:57         ` Krzysztof Kozlowski
2026-04-17 22:59         ` Dmitry Baryshkov
2026-04-20  5:40           ` Kuldeep Singh
2026-04-20  6:28             ` Shawn Guo

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=aeHxPALfVd7SgtUj@QCOM-aGQu4IUr3Y.na.qualcomm.com \
    --to=shengchao.guo@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@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®