mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Hans de Goede" <hdegoede@redhat.com>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Rodrigo Siqueira" <Rodrigo.Siqueira@amd.com>,
	"Matt Hartley" <matt.hartley@gmail.com>,
	"Kieran Levin" <ktl@framework.net>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Dustin Howett <dustin@howett.net>,
	Matthew Anderson <ruinairas1992@gmail.com>,
	"Derek J. Clark" <derkejohn.clark@gmail.com>
Subject: Re: [PATCH v2 1/3] drm: Add panel backlight quirks
Date: Mon, 24 Jun 2024 13:37:47 -0500	[thread overview]
Message-ID: <93677810-55e5-40b9-8756-c10820dc890e@amd.com> (raw)
In-Reply-To: <ad5d7ff3-e013-46d0-9ddb-5b0afc3dc870@redhat.com>

On 6/23/2024 15:55, Hans de Goede wrote:
> Hi,
> 
> On 6/23/24 10:20 PM, Mario Limonciello wrote:
>> On 6/23/2024 03:51, Thomas Weißschuh wrote:
>>> Panels using a PWM-controlled backlight source without an do not have a
>>> standard way to communicate their valid PWM ranges.
>>> On x86 the ranges are read from ACPI through driver-specific tables.
>>> The built-in ranges are not necessarily correct, or may grow stale if an
>>> older device can be retrofitted with newer panels.
>>>
>>> Add a quirk infrastructure with which the valid backlight ranges can be
>>> maintained as part of the kernel.
>>>
>>
>> So I was just talking to some folks in the Linux handheld gaming community (added to CC) about an issue they have where they need to know the correct panel orientation.  Due to reuse of panels across vendors the orientation on one might not be appropriate on another.  The trick is then to detect the combo of both the panel and the DMI data.
>>
>> It's the same "kind" of problem where something advertised in the firmware should be ignored but only on a panel + SMBIOS combination.
>>
>> So I am wondering if what you're proposing here could be more generalized.  IE "drm_panel_quirks.c" instead?
>>
>> Thoughts?
> 
> Note we already have a quirk mechanism for non upright mounted lcd-panels:
> 
> drivers/gpu/drm/drm_panel_orientation_quirks.c
> 
> note that the info here is shared with the simpledrm and
> efifb drivers, so if the chose is made to extend this then
> that needs to be taken into account.
> 
> Regards,
> 
> Hans

Thanks for sharing.  Totally agree this is this the better way to go for 
what I raised.

  reply	other threads:[~2024-06-24 18:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23  8:51 [PATCH v2 0/3] drm: backlight quirk infrastructure and lower minimum for Framework AMD 13 Thomas Weißschuh
2024-06-23  8:51 ` [PATCH v2 1/3] drm: Add panel backlight quirks Thomas Weißschuh
2024-06-23 20:20   ` Mario Limonciello
2024-06-23 20:55     ` Hans de Goede
2024-06-24 18:37       ` Mario Limonciello [this message]
2024-06-24  9:00   ` Hans de Goede
2024-06-29  4:52   ` Jeff Johnson
2024-06-23  8:51 ` [PATCH v2 2/3] drm: panel-backlight-quirks: Add Framework 13 matte panel Thomas Weißschuh
2024-06-23  8:51 ` [PATCH v2 3/3] drm/amd/display: Add support backlight quirks Thomas Weißschuh
2024-06-24  9:11 ` [PATCH v2 0/3] drm: backlight quirk infrastructure and lower minimum for Framework AMD 13 Hans de Goede
2024-06-24 16:15   ` Thomas Weißschuh
2024-07-18  8:25     ` Hans de Goede
2024-07-20  7:31       ` Thomas Weißschuh
2024-07-22 11:53         ` Hans de Goede
2024-07-24  8:57       ` Jani Nikula
2024-07-24 15:53         ` Alex Deucher
2024-07-02 13:12 ` Mario Limonciello
2024-08-05 12:55 ` Hans de Goede

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=93677810-55e5-40b9-8756-c10820dc890e@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Rodrigo.Siqueira@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=derkejohn.clark@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dustin@howett.net \
    --cc=harry.wentland@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ktl@framework.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matt.hartley@gmail.com \
    --cc=mripard@kernel.org \
    --cc=ruinairas1992@gmail.com \
    --cc=sunpeng.li@amd.com \
    --cc=tzimmermann@suse.de \
    /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®