From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Vadim Pasternak <vadimp@nvidia.com>,
Ciju Rajan K <crajank@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
Michael Shych <michaelsh@nvidia.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/mellanox: mlxreg-dpu: add I2C dependency
Date: Mon, 5 May 2025 14:38:26 +0300 (EEST) [thread overview]
Message-ID: <60faeb10-ecf0-1027-d09b-171de50cc3eb@linux.intel.com> (raw)
In-Reply-To: <20250502203739.2143173-1-arnd@kernel.org>
On Fri, 2 May 2025, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> REGMAP_I2C cannot be selected unless I2C is already enabled:
>
> WARNING: unmet direct dependencies detected for REGMAP_I2C
> Depends on [n]: I2C [=n]
> Selected by [y]:
> - MLXREG_DPU [=y] && MELLANOX_PLATFORM [=y]
>
> Fixes: 3e75f2954116 ("platform/mellanox: mlxreg-dpu: Add initial support for Nvidia DPU")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/platform/mellanox/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/mellanox/Kconfig b/drivers/platform/mellanox/Kconfig
> index 7204b10388ca..e3afbe62c7f6 100644
> --- a/drivers/platform/mellanox/Kconfig
> +++ b/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,
This has been long fixed in the review-ilpo-next branch but LKP has been
slow to build test it so the fix hasn't propagated into fox-next. I just
pushed the changes into for-next as it seems LKP might not build that at
all.
--
i.
prev parent reply other threads:[~2025-05-05 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 20:37 [PATCH] platform/mellanox: mlxreg-dpu: add I2C dependency Arnd Bergmann
2025-05-05 11:38 ` Ilpo Järvinen [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=60faeb10-ecf0-1027-d09b-171de50cc3eb@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=crajank@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelsh@nvidia.com \
--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