diff options
author | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2023-01-03 22:47:01 +0300 |
---|---|---|
committer | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2023-01-05 22:19:33 +0300 |
commit | 157821fb3e9aaa07cf408686b08d117bf27b7de1 (patch) | |
tree | 40f984b31cd0bea0a5996d022eb421e97038b5dc /.gitattributes | |
parent | 5a9b0c7418448ed3766f61ba0a71d08f259c3181 (diff) | |
download | linux-157821fb3e9aaa07cf408686b08d117bf27b7de1.tar.xz |
drm/i915: Expand force_probe to block probe of devices as well.
There are new cases where we want to block i915 probe, such
as when experimenting or developing the new Xe driver.
But also, with the new hybrid cards, users or developers might
want to use i915 only on integrated and fully block the probe
of the i915 for the discrete. Or vice versa.
There are even older development and validation reasons,
like when you use some distro where the modprobe.blacklist is
not present.
But in any case, let's introduce a more granular control, but without
introducing yet another parameter, but using the existent force_probe
one.
Just by adding a ! in the begin of the id in the force_probe, like
in this case where we would block the probe for Alder Lake:
$ insmod i915.ko force_probe='!46a6'
v2: Take care of '*' and '!*' cases as pointed out by
Gustavo and Jani.
Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Gustavo Sousa <gustavo.sousa@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Acked-by: Gustavo Sousa <gustavo.sousa@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230103194701.1492984-1-rodrigo.vivi@intel.com
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions