public inbox for linux-leds@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Richard Purdie <rpurdie@rpsys.net>, Pavel Machek <pavel@ucw.cz>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH] leds: core: use deferred probing if default trigger isn't available yet
Date: Thu, 23 Feb 2017 22:25:46 +0100	[thread overview]
Message-ID: <2e89ab77-2e33-47dd-035e-a84f1885c554@gmail.com> (raw)
In-Reply-To: <72e43bca-6b3d-8907-fdb3-d95c36d6f737@gmail.com>

Am 23.02.2017 um 22:04 schrieb Jacek Anaszewski:
> Hi Heiner,
> 
> Thanks for the patch. I have one comment below.
> 
> On 02/22/2017 09:35 PM, Heiner Kallweit wrote:
>> When registering a LED device we have the option to set a default trigger.
>> Depending on load order of drivers this trigger may not be available yet.
>> (affected LED device in my case: a DT-configured GPIO LED)
>> So far if the default trigger can't be found this error is silently
>> ignored.
>>
>> Let's change this to return EPROBE_DEFER if the default trigger can't be
>> found. This gives the system the chance to probe the LED device later
>> once the trigger is available.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> ---
>>  drivers/leds/led-class.c    |  6 +++++-
>>  drivers/leds/led-triggers.c | 11 ++++++++---
>>  include/linux/leds.h        |  5 +++--
>>  3 files changed, 16 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
>> index f2b0a80a..efe4f5a3 100644
>> --- a/drivers/leds/led-class.c
>> +++ b/drivers/leds/led-class.c
>> @@ -295,7 +295,11 @@ int led_classdev_register(struct device *parent, struct led_classdev *led_cdev)
>>  	led_init_core(led_cdev);
>>  
>>  #ifdef CONFIG_LEDS_TRIGGERS
>> -	led_trigger_set_default(led_cdev);
>> +	ret = led_trigger_set_default(led_cdev);
>> +	if (ret) {
>> +		led_classdev_unregister(led_cdev);
>> +		return ret;
>> +	}
>>  #endif
>>  
>>  	dev_dbg(parent, "Registered led device: %s\n",
>> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
>> index 431123b0..bad9e986 100644
>> --- a/drivers/leds/led-triggers.c
>> +++ b/drivers/leds/led-triggers.c
>> @@ -157,21 +157,26 @@ void led_trigger_remove(struct led_classdev *led_cdev)
>>  }
>>  EXPORT_SYMBOL_GPL(led_trigger_remove);
>>  
>> -void led_trigger_set_default(struct led_classdev *led_cdev)
>> +int led_trigger_set_default(struct led_classdev *led_cdev)
>>  {
>>  	struct led_trigger *trig;
>> +	int ret = -EPROBE_DEFER;
>>  
>>  	if (!led_cdev->default_trigger)
>> -		return;
>> +		return 0;
>>  
>>  	down_read(&triggers_list_lock);
>>  	down_write(&led_cdev->trigger_lock);
>>  	list_for_each_entry(trig, &trigger_list, next_trig) {
>> -		if (!strcmp(led_cdev->default_trigger, trig->name))
>> +		if (!strcmp(led_cdev->default_trigger, trig->name)) {
>>  			led_trigger_set(led_cdev, trig);
>> +			ret = 0;
> 
> I wonder why we don't break the loop after matching the trigger?
> 
> I think that we can add break here while we are at it since LED Trigger
> core doesn't allow for registering two triggers with the same name.
> 
Indeed.

> Would you mind sending an update and mention it also in the commit
> message?
> 
Fine with me if we can silently improve the existing code ..

> Best regards,
> Jacek Anaszewski
> 
>> +		}
>>  	}
>>  	up_write(&led_cdev->trigger_lock);
>>  	up_read(&triggers_list_lock);
>> +
>> +	return ret;
>>  }
>>  EXPORT_SYMBOL_GPL(led_trigger_set_default);
>>  
>> diff --git a/include/linux/leds.h b/include/linux/leds.h
>> index 38c0bd7c..3e36ce31 100644
>> --- a/include/linux/leds.h
>> +++ b/include/linux/leds.h
>> @@ -280,7 +280,7 @@ extern void led_trigger_blink_oneshot(struct led_trigger *trigger,
>>  				      unsigned long *delay_on,
>>  				      unsigned long *delay_off,
>>  				      int invert);
>> -extern void led_trigger_set_default(struct led_classdev *led_cdev);
>> +extern int led_trigger_set_default(struct led_classdev *led_cdev);
>>  extern void led_trigger_set(struct led_classdev *led_cdev,
>>  			struct led_trigger *trigger);
>>  extern void led_trigger_remove(struct led_classdev *led_cdev);
>> @@ -326,7 +326,8 @@ static inline void led_trigger_blink_oneshot(struct led_trigger *trigger,
>>  				      unsigned long *delay_on,
>>  				      unsigned long *delay_off,
>>  				      int invert) {}
>> -static inline void led_trigger_set_default(struct led_classdev *led_cdev) {}
>> +static inline int led_trigger_set_default(struct led_classdev *led_cdev)
>> +							{ return 0; }
>>  static inline void led_trigger_set(struct led_classdev *led_cdev,
>>  				struct led_trigger *trigger) {}
>>  static inline void led_trigger_remove(struct led_classdev *led_cdev) {}
>>
> 

  reply	other threads:[~2017-02-23 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 20:35 [PATCH] leds: core: use deferred probing if default trigger isn't available yet Heiner Kallweit
2017-02-23 21:04 ` Jacek Anaszewski
2017-02-23 21:25   ` Heiner Kallweit [this message]
2017-02-26 17:09     ` Jacek Anaszewski
2017-02-23 21:08 ` Pavel Machek
2017-02-23 21:23   ` Heiner Kallweit
2017-02-26 17:10     ` Jacek Anaszewski
2017-02-26 21:00       ` Pavel Machek
2017-02-26 22:07         ` Jacek Anaszewski

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=2e89ab77-2e33-47dd-035e-a84f1885c554@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.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