public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>
Cc: 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:14:23 +0200	[thread overview]
Message-ID: <898874b3-fb73-4a46-b440-6ea3377c2f2d@kernel.org> (raw)
In-Reply-To: <20260417035509.1021860-1-shengchao.guo@oss.qualcomm.com>

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.

> Promote both to built-in to allow booting directly from UFS without
> an initramfs.
> 
> PHY_QCOM_QMP is a menuconfig umbrella for all Qualcomm QMP PHY drivers.
> Setting it to built-in is required to allow any of its sub-drivers to be
> built-in.  Since only the UFS PHY (PHY_QCOM_QMP_UFS) needs to be
> built-in for the rootfs use case, the PCIe and USB sub-drivers
> (PHY_QCOM_QMP_PCIE, PHY_QCOM_QMP_PCIE_8996, PHY_QCOM_QMP_USB) are
> explicitly set to module to avoid unnecessarily inflating the kernel
> image.  The combo PHY sub-driver (PHY_QCOM_QMP_COMBO) is naturally
> capped at module by its dependencies on TYPEC=m and DRM=m.
> 
> Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> ---
>  arch/arm64/configs/defconfig | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index dd1ac01ee29b..f6ac2d29cbdf 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -1316,7 +1316,7 @@ CONFIG_SCSI_UFSHCD=y
>  CONFIG_SCSI_UFS_BSG=y
>  CONFIG_SCSI_UFSHCD_PLATFORM=y
>  CONFIG_SCSI_UFS_CDNS_PLATFORM=m
> -CONFIG_SCSI_UFS_QCOM=m
> +CONFIG_SCSI_UFS_QCOM=y

No, I reiterated this many times on the list, so once more: no.

This is fine as module.

Best regards,
Krzysztof

  reply	other threads:[~2026-04-17  8:14 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 [this message]
2026-04-17  8:37   ` Shawn Guo
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

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=898874b3-fb73-4a46-b440-6ea3377c2f2d@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