public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: arnd@arndb.de, Mikko Rapeli <mikko.rapeli@linaro.org>,
	Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	adrian.hunter@intel.com, victor.shih@genesyslogic.com.tw,
	ben.chuang@genesyslogic.com.tw, geert+renesas@glider.be,
	angelogioacchino.delregno@collabora.com, dlan@gentoo.org,
	zhoubinbin@loongson.cn
Subject: Re: [PATCH] mmc: dw_mmc-rockchip: add dependency to ROCKCHIP_PM_DOMAINS
Date: Thu, 11 Sep 2025 18:05:59 +0200	[thread overview]
Message-ID: <1813054.X513TT2pbd@diego> (raw)
In-Reply-To: <CAPDyKFqLag_WkxqOCebvBCJy4TzZEqt-rFD_Z30sajUxgSpcaA@mail.gmail.com>

Hi,

Am Donnerstag, 11. September 2025, 17:03:14 Mitteleuropäische Sommerzeit schrieb Ulf Hansson:
> On Thu, 11 Sept 2025 at 16:43, Mikko Rapeli <mikko.rapeli@linaro.org> wrote:
> > @@ -866,7 +866,7 @@ config MMC_DW_PCI
> >
> >  config MMC_DW_ROCKCHIP
> >         tristate "Rockchip specific extensions for Synopsys DW Memory Card Interface"
> > -       depends on MMC_DW && ARCH_ROCKCHIP
> > +       depends on MMC_DW && ARCH_ROCKCHIP && ROCKCHIP_PM_DOMAINS
> 
> Rather than "depends on", I think a "select" is better to be added
> from the platform's Kconfig. Probably drivers/soc/rockchip/Kconfig is
> where to put this.
> 
> Assuming that ROCKCHIP_PM_DOMAINS is a critical piece for most
> Rockchip platforms to work.

I'd think
- arch/arm64/Kconfig.platforms
- arch/arm/mach-rockchip/Kconfig
would be the correct positions.

And as Ulf suggested, this should be a "select"


And I guess, always selecting it makes sense as well.

Every supported soc back to the before 2012 RK3066 has controllable
power-domains and while the driver is selected in both the arm32+64
defconfigs, this still allows people to manually de-select the driver
leaving most elements to defer.

So yes, always-selecting the driver makes a lot of sense.


Thanks
Heiko



  reply	other threads:[~2025-09-11 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11 14:43 [PATCH] mmc: dw_mmc-rockchip: add dependency to ROCKCHIP_PM_DOMAINS Mikko Rapeli
2025-09-11 15:03 ` Ulf Hansson
2025-09-11 16:05   ` Heiko Stübner [this message]
2025-09-12  8:47     ` Arnd Bergmann
2025-09-12 11:30       ` Mikko Rapeli
2025-09-12 13:24         ` Arnd Bergmann

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=1813054.X513TT2pbd@diego \
    --to=heiko@sntech.de \
    --cc=adrian.hunter@intel.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arnd@arndb.de \
    --cc=ben.chuang@genesyslogic.com.tw \
    --cc=dlan@gentoo.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mikko.rapeli@linaro.org \
    --cc=ulf.hansson@linaro.org \
    --cc=victor.shih@genesyslogic.com.tw \
    --cc=zhoubinbin@loongson.cn \
    /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