dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	harry.wentland@amd.com, Louis Chauvet <louis.chauvet@bootlin.com>
Subject: Re: [PATCH v4 3/9] drm: link connectors to backlight devices
Date: Fri, 29 May 2026 11:58:09 +0200	[thread overview]
Message-ID: <9f1b9cf9-5083-4b2b-b95f-ee15d3847852@kernel.org> (raw)
In-Reply-To: <vtyq4mxhyyp5nt4vtl2ct4yxxqogzpqxrvnupwqfa46ucddnil@cul44errvgnb>

On 5/29/26 11:56, Dmitry Baryshkov wrote:
> On Thu, May 28, 2026 at 12:49:05AM -0500, Mario Limonciello (AMD) wrote:
>> This will show which connector in sysfs matches which backlight.
>>
>> Signed-off-by: Mario Limonciello (AMD) <superm1@kernel.org>
>> ---
>>   drivers/gpu/drm/Kconfig             |   1 +
>>   drivers/gpu/drm/Makefile            |   2 +
>>   drivers/gpu/drm/drm_atomic_helper.c |   8 +
>>   drivers/gpu/drm/drm_backlight.c     | 430 ++++++++++++++++++++++++++++
>>   drivers/gpu/drm/drm_connector.c     |  12 +
>>   drivers/gpu/drm/drm_drv.c           |   8 +
>>   drivers/gpu/drm/drm_mode_config.c   |   7 +
>>   drivers/gpu/drm/drm_mode_object.c   |  66 ++++-
>>   drivers/gpu/drm/drm_sysfs.c         |  28 +-
>>   drivers/video/backlight/backlight.c |  17 ++
>>   include/drm/drm_backlight.h         |  46 +++
>>   include/drm/drm_connector.h         |   3 +
>>   include/drm/drm_mode_config.h       |   5 +
>>   include/linux/backlight.h           |  13 +
>>   14 files changed, 641 insertions(+), 5 deletions(-)
>>   create mode 100644 drivers/gpu/drm/drm_backlight.c
>>   create mode 100644 include/drm/drm_backlight.h
>>
>> +
>> +static void __drm_backlight_worker(struct work_struct *w)
>> +{
>> +	struct drm_backlight *b = container_of(w, struct drm_backlight, work);
>> +	static const char * const ep[] = { "BACKLIGHT=1", NULL };
> 
> This caused compile errors on linux-next, I had to drop both const
> specifiers from this declaration.

Yeah - my fault for trusting checkpatch suggestion right before sending 
upstream and not compile testing because it looked "trivial".

Will fix in next spin.

> 
>> +	struct backlight_device *bd;
>> +	bool send_uevent;
>> +	unsigned int v;
>> +
> 
> Nevertheless:
> 
> 
> Tested-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> # SM8150-HDK
> 
> 
> 

Much appreciated!


  reply	other threads:[~2026-05-29  9:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  5:49 [PATCH v4 0/9] Add support for a DRM backlight capability Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 1/9] Revert "backlight: Remove notifier" Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 2/9] backlight: add kernel-internal backlight API Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 3/9] drm: link connectors to backlight devices Mario Limonciello (AMD)
2026-05-29  9:56   ` Dmitry Baryshkov
2026-05-29  9:58     ` Mario Limonciello [this message]
2026-05-28  5:49 ` [PATCH v4 4/9] DRM: Add support for client and driver indicating support for luminance Mario Limonciello (AMD)
2026-05-29  9:53   ` Dmitry Baryshkov
2026-05-28  5:49 ` [PATCH v4 5/9] drm/amd/display: Pass up errors reading actual brightness Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 6/9] drm/amd: Indicate driver supports luminance Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 7/9] drm/amd/display: Allow backlight registration to fail Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 8/9] drm/amd/display: use drm backlight Mario Limonciello (AMD)
2026-05-28  5:49 ` [PATCH v4 9/9] drm/bridge: auto-link panel backlight in bridge connector Mario Limonciello (AMD)
2026-05-29  9:52   ` Dmitry Baryshkov
2026-05-29 15:13 ` [PATCH v4 0/9] Add support for a DRM backlight capability Simon Ser

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=9f1b9cf9-5083-4b2b-b95f-ee15d3847852@kernel.org \
    --to=superm1@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=louis.chauvet@bootlin.com \
    --cc=mario.limonciello@amd.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