From: Corey Minyard <corey@minyard.net>
To: shankerwangmiao@gmail.com
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
Chong Qiao <qiaochong@loongson.cn>, Lee Jones <lee@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Xi Ruoyao <xry111@xry111.site>, WANG Xuerui <kernel@xen0n.name>,
Yinbo Zhu <zhuyinbo@loongson.cn>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH RFC v5 5/7] ipmi: ls2k: Relax the dependency to its mfd driver
Date: Mon, 3 Aug 2026 15:46:36 -0500 [thread overview]
Message-ID: <anD-LJYB-afdVAXN@mail.minyard.net> (raw)
In-Reply-To: <20260804-ls2kbmc-mod-v5-5-e6bc5cdd9a93@gmail.com>
On Tue, Aug 04, 2026 at 12:55:53AM +0800, Miao Wang via B4 Relay wrote:
> From: Miao Wang <shankerwangmiao@gmail.com>
>
> There is no strong dependency between the IPMI driver and its mfd
> driver. Although the IPMI driver will not work without the mfd driver,
> it is not a hard dependency. The IPMI driver can actually be compiled
> without the mfd driver, and it will just fail to probe. When the mfd
> driver is loaded, the IPMI driver will probe successfully. Therefore,
> the dependency of the IPMI driver on its mfd driver should be relaxed
> to "imply" from "select". This will allow the mfd driver to be compiled
> as a module and the IPMI driver to be compiled as a part of the ipmi_si
> module. The adjustment to Kconfig for the mfd driver will be introduced
> in the later patch in this series.
I don't think that's what "imply" is for. Imply seems to be for if
there is another subsystem that can use this subsystem, but doesn't
require it to exist.
For instance:
config SENSORS_NPCM7XX
tristate "Nuvoton NPCM750 and compatible PWM and Fan controllers"
imply THERMAL
The fan controller will work fine without the thermal subsystem; you
can control the fan speed without it. But the thermal subsystem is the
logical user of this. I looked at many of these things like this.
In the IPMI case, the IPMI driver is useless without the mfd part. So
there's no point in compiling the IPMI part of this if the mfd part is
not there.
I could be wrong, but I can't see why you would want to do this.
-corey
>
> Fixes: d46651d4e3c0 ("ipmi: Add Loongson-2K BMC support")
> Signed-off-by: Miao Wang <shankerwangmiao@gmail.com>
> ---
> drivers/char/ipmi/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/Kconfig b/drivers/char/ipmi/Kconfig
> index 669f7600019747bcd2b37563477cf336f19a0407..f456e3e89416932f0d21bb742153a503aeb24267 100644
> --- a/drivers/char/ipmi/Kconfig
> +++ b/drivers/char/ipmi/Kconfig
> @@ -87,7 +87,7 @@ config IPMI_IPMB
> config IPMI_LS2K
> bool 'Loongson-2K IPMI interface'
> depends on LOONGARCH
> - select MFD_LS2K_BMC_CORE
> + imply MFD_LS2K_BMC_CORE
> help
> Provides a driver for Loongson-2K IPMI interfaces.
>
>
> --
> 2.49.0
>
>
next prev parent reply other threads:[~2026-08-03 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 16:55 [PATCH RFC v5 0/7] mfd: ls2kbmc: multiple fixes for this driver Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 1/7] mfd: ls2kbmc: Make a copy when parsing mode string Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 2/7] mfd: ls2kbmc: Sanity check for the connected pci port Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 3/7] mfd: ls2kbmc: Redraw using exported functions Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 4/7] mfd: ls2kbmc: Cancel the work queue on removal Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 5/7] ipmi: ls2k: Relax the dependency to its mfd driver Miao Wang via B4 Relay
2026-08-03 20:46 ` Corey Minyard [this message]
2026-08-04 9:40 ` Miao Wang
2026-08-04 11:39 ` Corey Minyard
2026-08-04 12:27 ` Miao Wang
2026-08-04 13:56 ` Corey Minyard
2026-08-03 16:55 ` [PATCH RFC v5 6/7] mfd: ls2kbmc: Able to be compiled as a module Miao Wang via B4 Relay
2026-08-03 16:55 ` [PATCH RFC v5 7/7] mfd: ls2kbmc: Capture the reset event of BMC through GPIO Miao Wang via B4 Relay
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=anD-LJYB-afdVAXN@mail.minyard.net \
--to=corey@minyard.net \
--cc=brgl@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=qiaochong@loongson.cn \
--cc=shankerwangmiao@gmail.com \
--cc=xry111@xry111.site \
--cc=zhoubinbin@loongson.cn \
--cc=zhuyinbo@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