public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Shawn Lin <shawn.lin@rock-chips.com>,
	Diederik de Haas <didi.debian@cknow.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v2] arm64: defconfig: Enable Rockchip UFS host driver
Date: Tue, 20 May 2025 21:01:48 +0200	[thread overview]
Message-ID: <24315320.6Emhk5qWAg@phil> (raw)
In-Reply-To: <D9VW95BJVUZM.2KDNW7JLCKKF0@cknow.org>

Am Mittwoch, 14. Mai 2025, 14:48:46 Mitteleuropäische Sommerzeit schrieb Diederik de Haas:
> Hi,
> 
> I'm updating my own kernel config and have a question about this change.
> 
> On Wed Mar 5, 2025 at 8:54 AM CET, Shawn Lin wrote:
> > Enable Rockchip UFS host driver.
> >
> > This driver is first introduced on Rockchip RK3576 SoC, and will
> > be used for more SoCs in near future, so add it to defconfig
> > will make these platforms work better.
> >
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> > ---
> >
> >  arch/arm64/configs/defconfig | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > index 3a3706d..907e92d 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -1191,6 +1191,7 @@ CONFIG_SCSI_UFS_HISI=y
> >  CONFIG_SCSI_UFS_RENESAS=m
> >  CONFIG_SCSI_UFS_TI_J721E=m
> >  CONFIG_SCSI_UFS_EXYNOS=y
> > +CONFIG_SCSI_UFS_ROCKCHIP=y
> 
> Is there a particular reason why this is `=y` and not `=m`?
> 
> For SCSI_UFS_EXYNOS there is an explicit reason for `=y` in
> 5be91fe8d91b ("arm64: defconfig: Enable Exynos UFS driver")
> (it won't detect (some?) UFS devices otherwise)
> 
> But this patch/commit doesn't say if/why it must be built-in.
> Is there such a reason or is `=m` fine as well?

Most things are supposed to be modules. Though the on-soc mass-
storage devices get a bit of leniency ;-) .

I.e. defconfig is supposed to get you started, so not having to jump
through an initramfs to load the mmc of ufs module is helpful.


Heiko




      reply	other threads:[~2025-05-20 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  7:54 [PATCH v2] arm64: defconfig: Enable Rockchip UFS host driver Shawn Lin
2025-03-06 13:09 ` Heiko Stuebner
2025-05-14 12:48 ` Diederik de Haas
2025-05-20 19:01   ` Heiko Stuebner [this message]

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=24315320.6Emhk5qWAg@phil \
    --to=heiko@sntech.de \
    --cc=didi.debian@cknow.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.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