mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "David C. Manuelda" <stormbyte@gmail.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: Proposal: Make CONFIG_DRM_TTM_HELPER a user-configurable option
Date: Fri, 15 Aug 2025 11:13:07 +0300	[thread overview]
Message-ID: <d78f5ee29decaf595363baf93e0b184e0a7a3177@intel.com> (raw)
In-Reply-To: <51e650f7-39f3-4e06-a3ed-9941e0ccb0c0@gmail.com>

On Thu, 14 Aug 2025, "David C. Manuelda" <stormbyte@gmail.com> wrote:
> Hi all,
>
> I'm working with external DRM drivers (such as NVIDIA's proprietary 
> module), and I've noticed that `CONFIG_DRM_TTM_HELPER` is currently not 
> user-selectable—it gets pulled in only when enabling other drivers like 
> `nouveau`, `amdgpu`, etc.
>
> This creates a situation where, in order to build support for external 
> drivers that depend on `DRM_TTM_HELPER`, one must also enable unrelated 
> DRM drivers, which may not be desired in certain setups.
>
> In my humble opinion, it would be beneficial to make `DRM_TTM_HELPER` a 
> directly selectable option in `menuconfig`. This would allow users to 
> enable it independently, without dragging in other drivers.

You can either enable it in your .config directly, or add "select
DRM_TTM_HELPER" in the out-of-tree module.

IMO convenience for out-of-tree modules is not really a consideration,
because adding new user selectable kconfig options is an inconvenience
for in-tree users.

BR,
Jani.

-- 
Jani Nikula, Intel

      reply	other threads:[~2025-08-15  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 10:54 David C. Manuelda
2025-08-15  8:13 ` Jani Nikula [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=d78f5ee29decaf595363baf93e0b184e0a7a3177@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stormbyte@gmail.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®