From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
"Vadim Pasternak" <vadimp@nvidia.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org
Subject: [PATCH] platform/mellanox: MLXREG_DPU depends on I2C
Date: Thu, 1 May 2025 17:16:20 -0700 [thread overview]
Message-ID: <20250502001622.674263-1-rdunlap@infradead.org> (raw)
WARNING: unmet direct dependencies detected for REGMAP_I2C
Depends on [m]: I2C [=m]
Selected by [y]:
- MLXREG_DPU [=y] && MELLANOX_PLATFORM [=y]
Without the dependency, REGMAP_I2C=y since MLXREG_DPU=y.
Since CONFIG_I2C=m, this causes many (> 230) unmet dependency warnings.
E.g.:
Selected by [m]:
- EEPROM_AT24 [=m] && I2C [=m] && SYSFS [=y]
- SERIAL_MAX310X [=m] && TTY [=y] && HAS_IOMEM [=y] && SPI_MASTER [=y] && I2C [=m]
- PINCTRL_AW9523 [=m] && PINCTRL [=y] && OF [=y] && I2C [=m]
- PINCTRL_CY8C95X0 [=m] && PINCTRL [=y] && I2C [=m]
- GPIO_FXL6408 [=m] && GPIOLIB [=y] && I2C [=m]
- GPIO_DS4520 [=m] && GPIOLIB [=y] && I2C [=m]
- GPIO_PCA953X [=m] && GPIOLIB [=y] && I2C [=m]
- IP5XXX_POWER [=m] && POWER_SUPPLY [=y] && I2C [=m]
- BATTERY_CW2015 [=m] && POWER_SUPPLY [=y] && I2C [=m]
- CHARGER_SBS [=m] && POWER_SUPPLY [=y] && I2C [=m]
Fixes: 3e75f2954116 ("platform/mellanox: mlxreg-dpu: Add initial support for Nvidia DPU")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Vadim Pasternak <vadimp@nvidia.com>
Cc: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org
---
drivers/platform/mellanox/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20250501.orig/drivers/platform/mellanox/Kconfig
+++ linux-next-20250501/drivers/platform/mellanox/Kconfig
@@ -29,6 +29,7 @@ config MLX_PLATFORM
config MLXREG_DPU
tristate "Nvidia Data Processor Unit platform driver support"
+ depends on I2C
select REGMAP_I2C
help
This driver provides support for the Nvidia BF3 Data Processor Units,
next reply other threads:[~2025-05-02 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 0:16 Randy Dunlap [this message]
2025-05-02 12:36 ` Ilpo Järvinen
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=20250502001622.674263-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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
all inboxes | Powered by JetHome®