All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: core: add managed version of led_trigger_register
Date: Mon, 04 Jan 2016 10:17:21 +0100	[thread overview]
Message-ID: <568A38A1.5000103@samsung.com> (raw)
In-Reply-To: <56871B99.1080103@gmail.com>

Hi Heiner,

On 01/02/2016 01:36 AM, Heiner Kallweit wrote:
> Complementing devm_led_classdev_register add a managed version of
> led_trigger_register.
>
> I omit a managed version of led_classdev_unregister as the equivalent
> devm_led_classdev_unregister isn't used in the kernel as of today.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
>   drivers/leds/led-triggers.c | 28 ++++++++++++++++++++++++++++
>   include/linux/leds.h        |  2 ++
>   2 files changed, 30 insertions(+)
>
> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
> index e8b1120..e1e9334 100644
> --- a/drivers/leds/led-triggers.c
> +++ b/drivers/leds/led-triggers.c
> @@ -249,6 +249,34 @@ void led_trigger_unregister(struct led_trigger *trig)
>   }
>   EXPORT_SYMBOL_GPL(led_trigger_unregister);
>
> +static void devm_led_trigger_release(struct device *dev, void *res)
> +{
> +	led_trigger_unregister(*(struct led_trigger **)res);
> +}
> +
> +int devm_led_trigger_register(struct device *dev,
> +			      struct led_trigger *trig)
> +{
> +	struct led_trigger **dr;
> +	int rc;
> +
> +	dr = devres_alloc(devm_led_trigger_release, sizeof(*dr),
> +			  GFP_KERNEL);
> +	if (!dr)
> +		return -ENOMEM;
> +
> +	*dr = trig;
> +
> +	rc = led_trigger_register(trig);
> +	if (rc)
> +		devres_free(dr);
> +	else
> +		devres_add(dev, dr);
> +
> +	return rc;
> +}
> +EXPORT_SYMBOL_GPL(devm_led_trigger_register);
> +
>   /* Simple LED Tigger Interface */
>
>   void led_trigger_event(struct led_trigger *trig,
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index fa359c7..3db0654 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -231,6 +231,8 @@ ssize_t led_trigger_show(struct device *dev, struct device_attribute *attr,
>   /* Registration functions for complex triggers */
>   extern int led_trigger_register(struct led_trigger *trigger);
>   extern void led_trigger_unregister(struct led_trigger *trigger);
> +extern int devm_led_trigger_register(struct device *dev,
> +				     struct led_trigger *trigger);
>
>   extern void led_trigger_register_simple(const char *name,
>   				struct led_trigger **trigger);
>

Applied, thanks.

-- 
Best Regards,
Jacek Anaszewski

      reply	other threads:[~2016-01-04  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02  0:36 [PATCH] leds: core: add managed version of led_trigger_register Heiner Kallweit
2016-01-04  9:17 ` Jacek Anaszewski [this message]

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=568A38A1.5000103@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-leds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.