From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH 0/2] driver: core: Allow drivers to opt out of driver_override
Date: Fri, 20 Nov 2026 17:23:43 +0100 [thread overview]
Message-ID: <awByB3M1qPiye8JL@monoceros> (raw)
In-Reply-To: <20260922-driver-override-opt-out-v1-0-58c35ded3b83@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Hello Thierry,
On Tue, Sep 22, 2026 at 01:38:27PM +0200, Thierry Reding wrote:
> Overriding the driver to bind to may not make sense for some drivers.
> One example of this is platform drivers that use device data obtained
> through device ID matching (such as OF or ACPI) and they cannot work
> without that device data.
>
> Usually the device ID matching is the only way that such drivers can
> match against a device, so drivers shouldn't need to check that their
> device data is valid. For such drivers, driver_override is the only
> corner case that can lead to a case where no device data is found.
> Instead of requiring each and every driver to handle this case, move
> handling into the core and let drivers opt out of this override
> mechanism if it doesn't make any sense for them.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
https://lore.kernel.org/all/cover.1795171088.git.u.kleine-koenig@baylibre.com/
is the more promising approach that doesn't require each driver to
opt-out of force-binding, so I'm discarding this series from my patch
queue.
Thanks
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-11-20 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:38 Thierry Reding
2026-09-22 11:38 ` [PATCH 1/2] " Thierry Reding
2026-09-22 12:13 ` Greg Kroah-Hartman
2026-09-22 12:49 ` Danilo Krummrich
2026-09-22 13:17 ` Uwe Kleine-König
2026-09-22 14:09 ` Thierry Reding
2026-09-25 17:21 ` Uwe Kleine-König
2026-09-22 11:38 ` [PATCH 2/2] pwm: tegra: Opt " Thierry Reding
2026-11-20 16:23 ` Uwe Kleine-König [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=awByB3M1qPiye8JL@monoceros \
--to=ukleinek@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=treding@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®