mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	<linux-leds@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<pavel@ucw.cz>, <robh@kernel.org>
Subject: Re: [PATCH v3 15/25] leds: lm3601x: Use generic support for composing LED names
Date: Thu, 11 Apr 2019 10:29:08 -0500	[thread overview]
Message-ID: <e8f068fd-531d-aca5-960f-a64d6797d19d@ti.com> (raw)
In-Reply-To: <20190331175501.23471-16-jacek.anaszewski@gmail.com>

Jacek

On 3/31/19 12:54 PM, Jacek Anaszewski wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> Cc: Dan Murphy <dmurphy@ti.com>
> ---
>  drivers/leds/leds-lm3601x.c | 38 +++++++++++++++++---------------------
>  1 file changed, 17 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/leds/leds-lm3601x.c b/drivers/leds/leds-lm3601x.c
> index 081aa71e43a3..d81884c406c3 100644
> --- a/drivers/leds/leds-lm3601x.c
> +++ b/drivers/leds/leds-lm3601x.c
> @@ -10,7 +10,6 @@
>  #include <linux/module.h>
>  #include <linux/regmap.h>
>  #include <linux/slab.h>
> -#include <uapi/linux/uleds.h>
>  
>  #define LM3601X_LED_IR		0x0
>  #define LM3601X_LED_TORCH	0x1
> @@ -90,8 +89,6 @@ struct lm3601x_led {
>  	struct regmap *regmap;
>  	struct mutex lock;
>  
> -	char led_name[LED_MAX_NAME_SIZE];
> -
>  	unsigned int flash_timeout;
>  	unsigned int last_flag;
>  
> @@ -322,10 +319,12 @@ static const struct led_flash_ops flash_ops = {
>  	.fault_get		= lm3601x_flash_fault_get,
>  };
>  
> -static int lm3601x_register_leds(struct lm3601x_led *led)
> +static int lm3601x_register_leds(struct lm3601x_led *led,
> +				 struct fwnode_handle *fwnode)
>  {
>  	struct led_classdev *led_cdev;
>  	struct led_flash_setting *setting;
> +	struct led_init_data init_data;
>  
>  	led->fled_cdev.ops = &flash_ops;
>  
> @@ -342,20 +341,25 @@ static int lm3601x_register_leds(struct lm3601x_led *led)
>  	setting->val = led->flash_current_max;
>  
>  	led_cdev = &led->fled_cdev.led_cdev;
> -	led_cdev->name = led->led_name;
>  	led_cdev->brightness_set_blocking = lm3601x_brightness_set;
>  	led_cdev->max_brightness = DIV_ROUND_UP(led->torch_current_max,
>  						LM3601X_TORCH_REG_DIV);
>  	led_cdev->flags |= LED_DEV_CAP_FLASH;
>  
> -	return led_classdev_flash_register(&led->client->dev, &led->fled_cdev);
> +	init_data.fwnode = fwnode;
> +	init_data.led_hw_name = led->client->name;
> +	init_data.default_label = (led->led_mode == LM3601X_LED_TORCH) ?
> +					"torch" : "infrared";
> +
> +	return led_classdev_flash_register_ext(&led->client->dev,
> +						&led->fled_cdev, &init_data);
>  }
>  
> -static int lm3601x_parse_node(struct lm3601x_led *led)
> +static int lm3601x_parse_node(struct lm3601x_led *led,
> +			      struct fwnode_handle **fwnode)
>  {
>  	struct fwnode_handle *child = NULL;
>  	int ret = -ENODEV;
> -	const char *name;
>  
>  	child = device_get_next_child_node(&led->client->dev, child);
>  	if (!child) {
> @@ -376,17 +380,6 @@ static int lm3601x_parse_node(struct lm3601x_led *led)
>  		goto out_err;
>  	}
>  
> -	ret = fwnode_property_read_string(child, "label", &name);
> -	if (ret) {
> -		if (led->led_mode == LM3601X_LED_TORCH)
> -			name = "torch";
> -		else
> -			name = "infrared";
> -	}
> -
> -	snprintf(led->led_name, sizeof(led->led_name),
> -		"%s:%s", led->client->name, name);
> -
>  	ret = fwnode_property_read_u32(child, "led-max-microamp",
>  					&led->torch_current_max);
>  	if (ret) {
> @@ -411,6 +404,8 @@ static int lm3601x_parse_node(struct lm3601x_led *led)
>  		goto out_err;
>  	}
>  
> +	*fwnode = child;
> +
>  out_err:
>  	fwnode_handle_put(child);
>  	return ret;
> @@ -419,6 +414,7 @@ static int lm3601x_parse_node(struct lm3601x_led *led)
>  static int lm3601x_probe(struct i2c_client *client)
>  {
>  	struct lm3601x_led *led;
> +	struct fwnode_handle *fwnode;
>  	int ret;
>  
>  	led = devm_kzalloc(&client->dev, sizeof(*led), GFP_KERNEL);
> @@ -428,7 +424,7 @@ static int lm3601x_probe(struct i2c_client *client)
>  	led->client = client;
>  	i2c_set_clientdata(client, led);
>  
> -	ret = lm3601x_parse_node(led);
> +	ret = lm3601x_parse_node(led, &fwnode);
>  	if (ret)
>  		return -ENODEV;
>  
> @@ -442,7 +438,7 @@ static int lm3601x_probe(struct i2c_client *client)
>  
>  	mutex_init(&led->lock);
>  
> -	return lm3601x_register_leds(led);
> +	return lm3601x_register_leds(led, fwnode);
>  }
>  
>  static int lm3601x_remove(struct i2c_client *client)
Tested-by: Dan Murphy <dmurphy@ti.com>

  reply	other threads:[~2019-04-11 15:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-31 17:54 [PATCH v3 00/25] Add generic support for composing LED class device name Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 01/25] leds: class: Improve LED and LED flash class registration API Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 02/25] dt-bindings: leds: Add LED_FUNCTION definitions Jacek Anaszewski
2019-04-05  1:11   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 03/25] dt-bindings: leds: Add LED_COLOR_ID definitions Jacek Anaszewski
2019-04-05  1:12   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 04/25] dt-bindings: leds: Add function, color and led-enumerator properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 05/25] leds: core: Add support for composing LED class device names Jacek Anaszewski
2019-04-05 11:45   ` Dan Murphy
2019-04-05 20:08     ` Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 06/25] dt-bindings: sc27xx-blt: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 07/25] leds: sc27xx-blt: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 08/25] dt-bindings: lt3593: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 09/25] leds: lt3593: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 10/25] dt-bindings: lp8860: Add function and color properties Jacek Anaszewski
2019-04-05 11:47   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 11/25] leds: lp8860: Use generic support for composing LED names Jacek Anaszewski
2019-04-11 15:28   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 12/25] dt-bindings: lm3692x: Add function and color properties Jacek Anaszewski
2019-04-05 11:48   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 13/25] leds: lm3692x: Use generic support for composing LED names Jacek Anaszewski
2019-04-11 15:29   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 14/25] dt-bindings: lm36010: Add function and color properties Jacek Anaszewski
2019-04-05 11:48   ` Dan Murphy
2019-03-31 17:54 ` [PATCH v3 15/25] leds: lm3601x: Use generic support for composing LED names Jacek Anaszewski
2019-04-11 15:29   ` Dan Murphy [this message]
2019-03-31 17:54 ` [PATCH v3 16/25] dt-bindings: cr0014114: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 17/25] leds: cr0014114: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 18/25] dt-bindings: aat1290: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 19/25] leds: aat1290: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 20/25] dt-bindings: as3645a: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 21/25] leds: as3645a: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 22/25] dt-bindings: leds-gpio: Add function and color properties Jacek Anaszewski
2019-03-31 17:54 ` [PATCH v3 23/25] leds: gpio: Use generic support for composing LED names Jacek Anaszewski
2019-03-31 17:55 ` [PATCH v3 24/25] dt-bindings: an30259a: Add function and color properties Jacek Anaszewski
2019-03-31 17:55 ` [PATCH v3 25/25] leds: an30259a: Use generic support for composing LED names Jacek Anaszewski
2019-04-04 13:21 ` [PATCH v3 00/25] Add generic support for composing LED class device name Pavel Machek
2019-04-04 19:18   ` Jacek Anaszewski
2019-04-06  9:46     ` Pavel Machek

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=e8f068fd-531d-aca5-960f-a64d6797d19d@ti.com \
    --to=dmurphy@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh@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®