mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pengyu Luo <mitltlatltl@gmail.com>
To: Lee Jones <lee@kernel.org>, Daniel Thompson <danielt@kernel.org>,
	Jingoo Han <jingoohan1@gmail.com>, Helge Deller <deller@gmx.de>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Pengyu Luo <mitltlatltl@gmail.com>
Subject: [RFC PATCH 1/2] backlight: Rename duplicated devices to support dual-backlight setups
Date: Sun, 25 May 2025 18:40:21 +0800	[thread overview]
Message-ID: <20250525104022.1326997-1-mitltlatltl@gmail.com> (raw)

When registering a backlight device, if a device with the same name
already exists, append "-secondary" to the new device's name. This is
useful for platforms with dual backlight drivers (e.g. some panels use
dual ktz8866), where both instances need to coexist.

For now, only one secondary instance is supported. If more instances
are needed, this logic can be extended with auto-increment or a more
flexible naming scheme.

Suggested-by: Daniel Thompson <danielt@kernel.org>
Signed-off-by: Pengyu Luo <mitltlatltl@gmail.com>
---
 drivers/video/backlight/backlight.c | 20 ++++++++++++++++++--
 1 file changed, 18 insertions(+), 2 deletions(-)

diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
index 9dc93c5e4..991702f5d 100644
--- a/drivers/video/backlight/backlight.c
+++ b/drivers/video/backlight/backlight.c
@@ -365,7 +365,8 @@ struct backlight_device *backlight_device_register(const char *name,
 	struct device *parent, void *devdata, const struct backlight_ops *ops,
 	const struct backlight_properties *props)
 {
-	struct backlight_device *new_bd;
+	struct backlight_device *new_bd, *prev_bd;
+	const char *new_name = NULL;
 	int rc;
 
 	pr_debug("backlight_device_register: name=%s\n", name);
@@ -377,10 +378,23 @@ struct backlight_device *backlight_device_register(const char *name,
 	mutex_init(&new_bd->update_lock);
 	mutex_init(&new_bd->ops_lock);
 
+	/*
+	 * If there is an instance with the same name already, then rename it.
+	 * We also can use an auto-increment field, but it seems that there is
+	 * no triple or quad case.
+	 */
+	prev_bd = backlight_device_get_by_name(name);
+	if (!IS_ERR_OR_NULL(prev_bd)) {
+		new_name = kasprintf(GFP_KERNEL, "%s-secondary", name);
+		if (!new_name)
+			return ERR_PTR(-ENOMEM);
+		put_device(&prev_bd->dev);
+	}
+
 	new_bd->dev.class = &backlight_class;
 	new_bd->dev.parent = parent;
 	new_bd->dev.release = bl_device_release;
-	dev_set_name(&new_bd->dev, "%s", name);
+	dev_set_name(&new_bd->dev, "%s", new_name ? new_name : name);
 	dev_set_drvdata(&new_bd->dev, devdata);
 
 	/* Set default properties */
@@ -414,6 +428,8 @@ struct backlight_device *backlight_device_register(const char *name,
 	list_add(&new_bd->entry, &backlight_dev_list);
 	mutex_unlock(&backlight_dev_list_mutex);
 
+	kfree(new_name);
+
 	return new_bd;
 }
 EXPORT_SYMBOL(backlight_device_register);
-- 
2.49.0


             reply	other threads:[~2025-05-25 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 10:40 Pengyu Luo [this message]
2025-05-25 10:40 ` [RFC PATCH 2/2] backlight: Improve support for dual backlight with primary/secondary linkage Pengyu Luo
2025-05-26  8:53 ` [RFC PATCH 1/2] backlight: Rename duplicated devices to support dual-backlight setups Jani Nikula
2025-06-02 13:45   ` Pengyu Luo

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=20250525104022.1326997-1-mitltlatltl@gmail.com \
    --to=mitltlatltl@gmail.com \
    --cc=danielt@kernel.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jingoohan1@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®