From: Jani Nikula <jani.nikula@linux.intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tomas Winkler <tomasw@gmail.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Raag Jadav <raag.jadav@intel.com>
Cc: linux-mtd@lists.infradead.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] mtd: MTD_INTEL_DG should depend on DRM_I915 or DRM_XE
Date: Wed, 30 Jul 2025 13:32:07 +0300 [thread overview]
Message-ID: <d947168fd02d6f820159b456099e6aa8f465b633@intel.com> (raw)
In-Reply-To: <07f67ab8ee78f6bf2559131e193381aafff7479a.1753870424.git.geert+renesas@glider.be>
On Wed, 30 Jul 2025, Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> Intel Discrete Graphics non-volatile memory is onlt present on intel
> discrete graphics devices, and its auxiliary device is instantiated by
> the Intel i915 and Xe2 DRM drivers. Hence add dependencies on DRM_I915
> and DRM_XE, to prevent asking the user about this driver when
> configuring a kernel without Intel graphics support.
>
> Fixes: ceb5ab3cb6463795 ("mtd: add driver for intel graphics non-volatile memory device")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/mtd/devices/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/devices/Kconfig b/drivers/mtd/devices/Kconfig
> index 46cebde79f34b0b7..f0ab74d695347117 100644
> --- a/drivers/mtd/devices/Kconfig
> +++ b/drivers/mtd/devices/Kconfig
> @@ -185,8 +185,8 @@ config MTD_POWERNV_FLASH
>
> config MTD_INTEL_DG
> tristate "Intel Discrete Graphics non-volatile memory driver"
> - depends on AUXILIARY_BUS
> - depends on MTD
> + depends on AUXILIARY_BUS && MTD
> + depends on DRM_I915 || DRM_XE || COMPILE_TEST
I understand the intent, but IIUC auxiliary bus usage should not require
a "depends on" relationship. Couldn't you have MTD_INTEL_DG=y and
DRM_I915=m just fine?
BR,
Jani.
> help
> This provides an MTD device to access Intel Discrete Graphics
> non-volatile memory.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-07-30 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:21 Geert Uytterhoeven
2025-07-30 10:32 ` Jani Nikula [this message]
2025-07-30 11:08 ` Geert Uytterhoeven
2025-07-31 8:23 ` Jani Nikula
2025-07-31 8:31 ` Usyskin, Alexander
2025-07-30 12:18 ` Raag Jadav
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=d947168fd02d6f820159b456099e6aa8f465b633@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alexander.usyskin@intel.com \
--cc=geert+renesas@glider.be \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=raag.jadav@intel.com \
--cc=richard@nod.at \
--cc=rodrigo.vivi@intel.com \
--cc=tomasw@gmail.com \
--cc=vigneshr@ti.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®