mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
	joonas.lahtinen@linux.intel.com, tursulin@ursulin.net,
	airlied@gmail.com, simona@ffwll.ch
Cc: wse@tuxedocomputers.com, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/1] drm/i915/display: Add quirk to force backlight type on some TUXEDO devices
Date: Fri,  7 Aug 2026 22:04:29 +0200	[thread overview]
Message-ID: <20260807200709.464343-1-wse@tuxedocomputers.com> (raw)

Since the proposed general fix, fixed the backlight on TUXEDO devices, but
broke it on other ones:
- https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/15679#note_3581777
- https://lore.kernel.org/all/20260515155340.1000997-1-suraj.kandpal@intel.com/
I'm back here again proposing the fix via a quirk.

I therefore rebased
https://lore.kernel.org/all/20260121223944.1104951-1-wse@tuxedocomputers.com/
to cleanly apply on current drm-tip.

V1->V2: Switch from dmis trings to PCI-IDs
V2->V3: Rebase onto current drm-tip
V3->V4: Better commit message and added comment in code

Werner Sembach (1):
  drm/i915/display: Add quirk to force backlight type on some TUXEDO
    devices

 .../drm/i915/display/intel_dp_aux_backlight.c | 22 ++++++++++++++++-
 drivers/gpu/drm/i915/display/intel_quirks.c   | 24 +++++++++++++++++++
 drivers/gpu/drm/i915/display/intel_quirks.h   |  1 +
 3 files changed, 46 insertions(+), 1 deletion(-)


base-commit: 665722ddd6884c57624bd82d7ab886cf11a7b6f8
-- 
2.43.0


             reply	other threads:[~2026-08-07 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 20:04 Werner Sembach [this message]
2026-08-07 20:04 ` [PATCH v4 1/1] " Werner Sembach
2026-08-10  5:15   ` Kandpal, Suraj

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=20260807200709.464343-1-wse@tuxedocomputers.com \
    --to=wse@tuxedocomputers.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    /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®