linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Matthew Garrett" <matthew.garrett@nebula.com>,
	"Seth Forshee" <seth.forshee@canonical.com>,
	"Lee Chun-Yi" <joeyli.kernel@gmail.com>,
	"Richard Purdie" <rpurdie@rpsys.net>,
	"Igor Gnatenko" <i.gnatenko.brain@gmail.com>,
	"Yves-Alexis Perez" <corsac@debian.org>,
	"Felipe Contreras" <felipe.contreras@gmail.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Ben Jencks" <ben@bjencks.net>,
	"Steven Newbury" <steve@snewbury.org.uk>,
	"James Hogan" <james@albanarts.com>,
	"Kamal Mostafa" <kamal@canonical.com>,
	"Joerg Platte" <jplatte@naasa.net>,
	"Kalle Valo" <kvalo@adurom.com>,
	"Martin Steigerwald" <Martin@lichtvoll.de>,
	"Jörg Otte" <jrg.otte@gmail.com>,
	"Mike Galbraith" <bitbucket@online.de>,
	platform-driver-x86@vger.kernel.org,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>
Subject: Re: [PATCH v4 1/4] backlight: introduce backlight_device_registered
Date: Thu, 10 Oct 2013 08:54:29 +0800	[thread overview]
Message-ID: <5255FAC5.2090105@intel.com> (raw)
In-Reply-To: <2202423.8QyNjoNEPr@vostro.rjw.lan>

On 10/10/2013 08:25 AM, Rafael J. Wysocki wrote:
> On Tuesday, October 08, 2013 02:39:58 PM Aaron Lu wrote:
>> Introduce a new API for modules to query if a specific type of backlight
>> device has been registered. This is useful for some backlight device
>> provider module(e.g. ACPI video) to know if a native control
>> interface(e.g. the interface created by i915) is available and then do
>> things accordingly(e.g. avoid register its own on Win8 systems).
>>
>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
>> Tested-by: Igor Gnatenko <i.gnatenko.brain@gmail.com>
>> Tested-by: Yves-Alexis Perez <corsac@debian.org>
>> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>> ---
>>  drivers/video/backlight/backlight.c | 31 +++++++++++++++++++++++++++++++
>>  include/linux/backlight.h           |  4 ++++
>>  2 files changed, 35 insertions(+)
>>
>> diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
>> index 94a403a..bf2d71d 100644
>> --- a/drivers/video/backlight/backlight.c
>> +++ b/drivers/video/backlight/backlight.c
>> @@ -21,6 +21,9 @@
>>  #include <asm/backlight.h>
>>  #endif
>>  
>> +static struct list_head bd_list_head;
>> +static struct mutex bd_list_mutex;
> 
> I'd prefer these two things to be called backlight_dev_list and
> backlight_dev_list_mutex, respectively.

OK.

> 
>> +
>>  static const char *const backlight_types[] = {
>>  	[BACKLIGHT_RAW] = "raw",
>>  	[BACKLIGHT_PLATFORM] = "platform",
>> @@ -349,10 +352,32 @@ struct backlight_device *backlight_device_register(const char *name,
>>  	mutex_unlock(&pmac_backlight_mutex);
>>  #endif
>>  
>> +	mutex_lock(&bd_list_mutex);
>> +	list_add(&new_bd->entry, &bd_list_head);
>> +	mutex_unlock(&bd_list_mutex);
>> +
>>  	return new_bd;
>>  }
>>  EXPORT_SYMBOL(backlight_device_register);
>>  
>> +bool backlight_device_registered(enum backlight_type type)
>> +{
>> +	bool found = false;
>> +	struct backlight_device *bd;
>> +
>> +	mutex_lock(&bd_list_mutex);
>> +	list_for_each_entry(bd, &bd_list_head, entry) {
>> +		if (bd->props.type == type) {
>> +			found = true;
>> +			break;
>> +		}
>> +	}
> 
> Isn't it useful to be able to register more than one backlight device of the
> same type sometimes?

I think so for some kind of computers. OTOH, the above function should
be enough for the problem we are solving here, if someday we need to
differentiate, we can enhance the code then.

> 
>> +	mutex_unlock(&bd_list_mutex);
>> +
>> +	return found;
>> +}
>> +EXPORT_SYMBOL(backlight_device_registered);
>> +
>>  /**
>>   * backlight_device_unregister - unregisters a backlight device object.
>>   * @bd: the backlight device object to be unregistered and freed.
>> @@ -364,6 +389,10 @@ void backlight_device_unregister(struct backlight_device *bd)
>>  	if (!bd)
>>  		return;
>>  
>> +	mutex_lock(&bd_list_mutex);
>> +	list_del(&bd->entry);
>> +	mutex_unlock(&bd_list_mutex);
>> +
>>  #ifdef CONFIG_PMAC_BACKLIGHT
>>  	mutex_lock(&pmac_backlight_mutex);
>>  	if (pmac_backlight == bd)
>> @@ -499,6 +528,8 @@ static int __init backlight_class_init(void)
>>  
>>  	backlight_class->dev_groups = bl_device_groups;
>>  	backlight_class->pm = &backlight_class_dev_pm_ops;
>> +	INIT_LIST_HEAD(&bd_list_head);
>> +	mutex_init(&bd_list_mutex);
>>  	return 0;
>>  }
>>  
>> diff --git a/include/linux/backlight.h b/include/linux/backlight.h
>> index 53b7794..5f9cd96 100644
>> --- a/include/linux/backlight.h
>> +++ b/include/linux/backlight.h
>> @@ -100,6 +100,9 @@ struct backlight_device {
>>  	/* The framebuffer notifier block */
>>  	struct notifier_block fb_notif;
>>  
>> +	/* list entry of all registered backlight devices */
>> +	struct list_head entry;
>> +
>>  	struct device dev;
>>  };
>>  
>> @@ -123,6 +126,7 @@ extern void devm_backlight_device_unregister(struct device *dev,
>>  					struct backlight_device *bd);
>>  extern void backlight_force_update(struct backlight_device *bd,
>>  				   enum backlight_update_reason reason);
>> +extern bool backlight_device_registered(enum backlight_type type);
>>  
>>  #define to_backlight_device(obj) container_of(obj, struct backlight_device, dev)
> 
> Thanks!

Thanks for the review,
-Aaron

  reply	other threads:[~2013-10-10  0:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  6:39 [PATCH v4 0/4] Fix Win8 backlight issue Aaron Lu
2013-10-08  6:39 ` [PATCH v4 1/4] backlight: introduce backlight_device_registered Aaron Lu
2013-10-10  0:25   ` Rafael J. Wysocki
2013-10-10  0:54     ` Aaron Lu [this message]
2013-10-10  1:07       ` Rafael J. Wysocki
2013-10-10  4:29       ` Jani Nikula
2013-10-10  4:53         ` Aaron Lu
2013-10-10  5:23           ` Jani Nikula
2013-10-08  6:39 ` [PATCH v4 2/4] ACPI / video: seperate backlight control and event interface Aaron Lu
2013-10-08  6:40 ` [PATCH v4 3/4] ACPI / video: Do not register backlight if win8 and native interface exists Aaron Lu
2013-10-10  0:29   ` Rafael J. Wysocki
2013-10-10  1:02     ` Aaron Lu
2013-10-10 12:59       ` Rafael J. Wysocki
2013-10-11  1:09         ` Aaron Lu
2013-10-08  6:40 ` [PATCH v4 4/4] thinkpad-acpi: fix handle locate for video and query of _BCL Aaron Lu

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=5255FAC5.2090105@intel.com \
    --to=aaron.lu@intel.com \
    --cc=Martin@lichtvoll.de \
    --cc=ben@bjencks.net \
    --cc=bitbucket@online.de \
    --cc=corsac@debian.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felipe.contreras@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=i.gnatenko.brain@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=james@albanarts.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=jplatte@naasa.net \
    --cc=jrg.otte@gmail.com \
    --cc=kamal@canonical.com \
    --cc=kvalo@adurom.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    --cc=seth.forshee@canonical.com \
    --cc=steve@snewbury.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).