Introduce mlxreg LED driver
Subsystems (2)
v8 cover Introduce mlxreg LED driver
This patch:
- Fixes text in Kconfig.
- Introduces LED driver, based on regmap interface.
Vadim Pasternak (2):
leds: fix Kconfig text for MLXCPLD, SYSCON, MC13783, NETXBIG
leds: add driver for support Mellanox regmap LEDs for BMC and x86
platform
MAINTAINERS | 1 + drivers/leds/Kconfig | 20 ++- drivers/leds/Makefile | 1 + drivers/leds/leds-mlxreg.c | 311 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 328 insertions(+), 5 deletions(-) create mode 100644 drivers/leds/leds-mlxreg.c
Signature · 1 line
2.1.4
PATCH v8 1/2 leds: fix Kconfig text for MLXCPLD, SYSCON, MC13783, NETXBIG
It fixes grammatical errors in Kconfig file for LEDS_SYSCON, LEDS_MLXCPLD, LEDS_MC13783, LEDS_NETXBIG.
---v7->v8
Comments pointed out by Pavel:
- Change "enable" to enables for LEDS_SYSCON Kconfig text; Fixed added by Vadim:
- Change "enable" to enables for LEDS_MC13783, LEDS_NETXBIG Kconfig
text; --- drivers/leds/Kconfig | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/leds/Kconfig +5 -5
@@ -521,7 +521,7 @@ config LEDS_MC13783 depends on LEDS_CLASS depends on MFD_MC13XXX help - This option enable support for on-chip LED drivers found + This option enables support for on-chip LED drivers found on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC. config LEDS_NS2
@@ -544,7 +544,7 @@ config LEDS_NETXBIG depends on MACH_KIRKWOOD default y help - This option enable support for LEDs found on the LaCie 2Big + This option enables support for LEDs found on the LaCie 2Big and 5Big Network v2 boards. The LEDs are wired to a CPLD and are controlled through a GPIO extension bus.
@@ -674,7 +674,7 @@ config LEDS_SYSCON depends on MFD_SYSCON depends on OF help - This option enabled support for the LEDs on syscon type + This option enables support for the LEDs on syscon type devices. This will only work with device tree enabled devices.
@@ -691,8 +691,8 @@ config LEDS_MLXCPLD depends on X86 && DMI depends on LEDS_CLASS help - This option enabled support for the LEDs on the Mellanox - boards. Say Y to enabled these. + This option enables support for the LEDs on the Mellanox + boards. Say Y to enable these. config LEDS_USER tristate "Userspace LED support"
Signature · 1 line
2.1.4
Jacek Anaszewski
AppliedRe: [PATCH v8 1/2] leds: fix Kconfig text for MLXCPLD, SYSCON, MC13783, NETXBIG
Hi Vadim,
Quoted 49 lines · Vadim Pasternak
It fixes grammatical errors in
Kconfigfile forLEDS_SYSCON,LEDS_MLXCPLD,LEDS_MC13783,LEDS_NETXBIG.Signed-off-by Vadim Pasternak <[email protected]>Reported-by Jacek Anaszewski <[email protected]>---
v7->v8
Comments pointed out by Pavel:
- Change "enable" to enables forLEDS_SYSCONKconfigtext; Fixed added by Vadim:
- Change "enable" to enables forLEDS_MC13783,LEDS_NETXBIGKconfigtext; --- drivers/leds/Kconfig | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)drivers/leds/Kconfig +3
-3@@ -521,7 +521,7 @@ config LEDS_MC13783 depends on LEDS_CLASS depends on MFD_MC13XXX help - This option enable support for on-chip LED drivers found + This option enables support for on-chip LED drivers found on Freescale Semiconductor MC13783/MC13892/MC34708 PMIC. config LEDS_NS2@@ -544,7 +544,7 @@ config LEDS_NETXBIG depends on MACH_KIRKWOOD default y help - This option enable support for LEDs found on the LaCie 2Big + This option enables support for LEDs found on the LaCie 2Big and 5Big Network v2 boards. The LEDs are wired to a CPLD and are controlled through a GPIO extension bus.@@ -674,7 +674,7 @@ config LEDS_SYSCON depends on MFD_SYSCON depends on OF help - This option enabled support for the LEDs on syscon type + This option enables support for the LEDs on syscon type devices. This will only work with device tree enabled devices.
drivers/leds/Kconfig config LEDS_MLXCPLD · line 698
Quoted 10 lines
drivers/leds/Kconfig +2
-2@@ -691,8 +691,8 @@ config LEDS_MLXCPLD depends on X86 && DMI depends on LEDS_CLASS help - This option enabled support for the LEDs on the Mellanox - boards. Say Y to enabled these. + This option enables support for the LEDs on the Mellanox + boards. Say Y to enable these. config LEDS_USER tristate "Userspace LED support"
Applied, thanks.
Signature · 2 lines
Best regards, Jacek Anaszewski
PATCH v8 2/2 leds: add driver for support Mellanox regmap LEDs for BMC and x86 platform
In reply to Vadim PasternakDriver obtains LED devices according to system configuration and creates devices in form: "devicename:color:function", like
The full path is to be:
/sys/class/leds/mlxreg\:status\:amber/brightness
After timer trigger activation:
echo timer > /sys/class/leds/mlxreg\:status\:amber/trigger Attributes for LED blinking will appaer in sysfs infrastructure:
/sys/class/leds/mlxreg\:status\:amber/delay_off /sys/class/leds/mlxreg\:status\:amber/delay_on
LED setting is controlled through the on-board programmable devices, which exports its register map. This device could be attached to any bus type, for which register mapping is supported.
---v8->v8v6->v7
Comments pointed out by Jacek:
- Fix text in Kconfig;v5->v6
Changes added by Vadim:
- Change year to 2018 in Copyright;
- Change structure mlxreg_core_led_platform_data name to common name mlxreg_core_platform_data, as it has been pushed to
git://git.infradead.org/linux-platform-drivers-x86.git to branch, commit 1f976f6978bf6156ce822eb279ac86c519b10329 (1f976f6), file include/linux/platform_data/mlxreg.h
- Add orange color, as alternative to red (some systems use orange,
instead of red);
- Drop mlxreg_led_dt_match, since the driver is to be activated by another
common Mellanox platform driver, mlx-platform or mlx-platform-of;v4->v5
Comments pointed out by Jacek:
- Make consistent naming in mlxreg_led_brightness_set, mlxreg_led_brightness_get, mlxreg_led_config;
- Remove unnecessary data assignment in mlxreg_led_config; Changes added by Vadim:
- Add internal structure mlxreg_led_data to leds-mlxreg.c;v3->v4
Comments pointed out by Jacek:
- add led in declaration mlxreg_led_store_hw and mlxreg_led_get_hw;
- rearrange local variables names in mlxreg_led_config; Comments pointed out by Pavel:
- replace _HALF/_FULL with BLINK_3HZ/BLINK_6HZ;
- in mlxreg_led_get_hw just return after access error;
- explicit check for green led is not added, since control device can be programmed for blue LED and this case it reuses masks of green LED.v2->v3:
Comments pointed out by Jacek:
- fix order in includes;
- add declaration pdata in mlxreg_led_store_hw and mlxreg_led_get_hw;
- add declaration of led_data in mlxreg_led_config;
- use LED_ON in assignment instead of 1;
- fix mutex call in mlxreg_led_remove;v1->v2:
Comments pointed out by Jacek:
- remove macros MLXREG_MAP and MLXREG_CDEV;
- brightness_set_blocking insteaf of brightness_set, this fix allows removing of context validation and workqueue and also three fields from struct mlxreg_core_led_data in mlxreg.h;
- remove MLXREG_LED_NAME;
- extend Kconfig description;
Changes added by Vadim:
- remove unnecessary includes after dropping workqueue;
--- MAINTAINERS | 1 + drivers/leds/Kconfig | 10 ++ drivers/leds/Makefile | 1 + drivers/leds/leds-mlxreg.c | 311 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 323 insertions(+) create mode 100644 drivers/leds/leds-mlxreg.c
MAINTAINERS +1 -0
@@ -9003,6 +9003,7 @@ M: Vadim Pasternak <[email protected]> L: [email protected] S: Supported F: drivers/leds/leds-mlxcpld.c +F: drivers/leds/leds-mlxreg.c F: Documentation/leds/leds-mlxcpld.txt MELLANOX PLATFORM DRIVER
drivers/leds/Kconfig +10 -0
@@ -694,6 +694,16 @@ config LEDS_MLXCPLD This option enables support for the LEDs on the Mellanox boards. Say Y to enable these. +config LEDS_MLXREG + tristate "LED support for the Mellanox switches management control" + depends on LEDS_CLASS + help + This option enables support for the LEDs on the Mellanox Ethernet and + InfiniBand switches. The driver can be activated from the device tree + or by the direct platform device add call. Say Y to enable these. To + compile this driver as a module, choose 'M' here: the module will be + called leds-mlxreg. + config LEDS_USER tristate "Userspace LED support" depends on LEDS_CLASS
drivers/leds/Makefile +1 -0
@@ -72,6 +72,7 @@ obj-$(CONFIG_LEDS_IS31FL319X) += leds-is31fl319x.o obj-$(CONFIG_LEDS_IS31FL32XX) += leds-is31fl32xx.o obj-$(CONFIG_LEDS_PM8058) += leds-pm8058.o obj-$(CONFIG_LEDS_MLXCPLD) += leds-mlxcpld.o +obj-$(CONFIG_LEDS_MLXREG) += leds-mlxreg.o obj-$(CONFIG_LEDS_NIC78BX) += leds-nic78bx.o obj-$(CONFIG_LEDS_MT6323) += leds-mt6323.o obj-$(CONFIG_LEDS_LM3692X) += leds-lm3692x.o
drivers/leds/leds-mlxreg.c new file +311 -0
311 lines not on this page · raw message
Signature · 1 line
2.1.4
Re: [PATCH v8 2/2] leds: add driver for support Mellanox regmap LEDs for BMC and x86 platform
Hi Vadim,
There are still three issues - one recently discussed, and two I've just noticed. See below.
Quoted 91 lines · Vadim Pasternak
Driver obtains LED devices according to system configuration and creates devices in form: "devicename:color:function", like
The full path is to be:
/sys/class/leds/mlxreg\:status\:amber/brightness
After timer trigger activation:
echo timer > /sys/class/leds/mlxreg\:status\:amber/trigger Attributes for LED blinking will appaer in sysfs infrastructure:
/sys/class/leds/mlxreg\:status\:amber/delay_off /sys/class/leds/mlxreg\:status\:amber/delay_onLED setting is controlled through the on-board programmable devices, which exports its register map. This device could be attached to any bus type, for which register mapping is supported.
Signed-off-by Vadim Pasternak <[email protected]>Acked-by Pavel Machek <[email protected]>---
v8->v8v6->v7
Comments pointed out by Jacek:
- Fix text inKconfig;v5->v6
Changes added by Vadim:
- Change year to 2018 in Copyright;
- Change structuremlxreg_core_led_platform_dataname to common namemlxreg_core_platform_data, as it has been pushed to
git://git.infradead.org/linux-platform-drivers-x86.gitto branch, commit1f976f6978bf6156ce822eb279ac86c519b10329(1f976f6), fileinclude/linux/platform_data/mlxreg.h
- Add orange color, as alternative to red (some systems use orange,instead of red); - Drop mlxreg_led_dt_match, since the driver is to be activated by another common Mellanox platform driver, mlx-platform or mlx-platform-of;
v4->v5
Comments pointed out by Jacek:
- Make consistent naming inmlxreg_led_brightness_set,mlxreg_led_brightness_get,mlxreg_led_config;
- Remove unnecessary data assignment inmlxreg_led_config; Changes added by Vadim:
- Add internal structuremlxreg_led_datatoleds-mlxreg.c;v3->v4
Comments pointed out by Jacek:
- add led in declarationmlxreg_led_store_hwandmlxreg_led_get_hw;
- rearrange local variables names inmlxreg_led_config; Comments pointed out by Pavel:
- replace _HALF/_FULL with BLINK_3HZ/BLINK_6HZ;
- inmlxreg_led_get_hwjust return after access error;
- explicit check for green led is not added, since control device can be programmed for blue LED and this case it reuses masks of green LED.v2->v3:
Comments pointed out by Jacek:
- fix order in includes;
- add declaration pdata inmlxreg_led_store_hwandmlxreg_led_get_hw;
- add declaration ofled_datainmlxreg_led_config;
- useLED_ONin assignment instead of 1;
- fix mutex call inmlxreg_led_remove;v1->v2:
Comments pointed out by Jacek:
- remove macrosMLXREG_MAPandMLXREG_CDEV;
-brightness_set_blockinginsteaf ofbrightness_set, this fix allows removing of context validation and workqueue and also three fields from structmlxreg_core_led_datainmlxreg.h;
- removeMLXREG_LED_NAME;
- extendKconfigdescription;
Changes added by Vadim:
- remove unnecessary includes after dropping workqueue;--- MAINTAINERS | 1 + drivers/leds/Kconfig | 10 ++ drivers/leds/Makefile | 1 + drivers/leds/leds-mlxreg.c | 311 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 323 insertions(+) create mode 100644 drivers/leds/leds-mlxreg.cMAINTAINERS +1
-0@@ -9003,6 +9003,7 @@ M: Vadim Pasternak <[email protected]> L: [email protected] S: Supported F: drivers/leds/leds-mlxcpld.c +F: drivers/leds/leds-mlxreg.c F: Documentation/leds/leds-mlxcpld.txt MELLANOX PLATFORM DRIVERdrivers/leds/Kconfig +0
-0
drivers/leds/Kconfig config LEDS_MLXCPLD · line 702
Quoted 9 lines
drivers/leds/Kconfig +6
-0@@ -694,6 +694,16 @@ config LEDS_MLXCPLD This option enables support for the LEDs on the Mellanox boards. Say Y to enable these. +config LEDS_MLXREG + tristate "LED support for the Mellanox switches management control" + depends on LEDS_CLASS + help + This option enables support for the LEDs on the Mellanox Ethernet and + InfiniBand switches. The driver can be activated from the device tree
We agreed on dropping device tree from this description, didn't we? :-)
Quoted 171 lines
drivers/leds/Kconfig +4
-0+ or by the direct platform device add call. Say Y to enable these. To + compile this driver as a module, choose 'M' here: the module will be + called leds-mlxreg. + config LEDS_USER tristate "Userspace LED support" depends on LEDS_CLASSdrivers/leds/Makefile +1
-0@@ -72,6 +72,7 @@ obj-$(CONFIG_LEDS_IS31FL319X) += leds-is31fl319x.o obj-$(CONFIG_LEDS_IS31FL32XX) += leds-is31fl32xx.o obj-$(CONFIG_LEDS_PM8058) += leds-pm8058.o obj-$(CONFIG_LEDS_MLXCPLD) += leds-mlxcpld.o +obj-$(CONFIG_LEDS_MLXREG) += leds-mlxreg.o obj-$(CONFIG_LEDS_NIC78BX) += leds-nic78bx.o obj-$(CONFIG_LEDS_MT6323) += leds-mt6323.o obj-$(CONFIG_LEDS_LM3692X) += leds-lm3692x.odrivers/leds/leds-mlxreg.c new file +146
-0@@ -0,0 +1,311 @@ +/* +* Copyright (c) 2018 Mellanox Technologies. All rights reserved. +* Copyright (c) 2018 Vadim Pasternak <[email protected]> +* +* Redistribution and use in source and binary forms, with or without +* modification, are permitted provided that the following conditions are met: +* +* 1. Redistributions of source code must retain the above copyright +* notice, this list of conditions and the following disclaimer. +* 2. Redistributions in binary form must reproduce the above copyright +* notice, this list of conditions and the following disclaimer in the +* documentation and/or other materials provided with the distribution. +* 3. Neither the names of the copyright holders nor the names of its +* contributors may be used to endorse or promote products derived from +* this software without specific prior written permission. +* +* Alternatively, this software may be distributed under the terms of the +* GNU General Public License ("GPL") version 2 as published by the Free +* Software Foundation. +* +* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" +* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE +* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF +* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS +* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN +* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE +* POSSIBILITY OF SUCH DAMAGE. +*/ + +#include <linux/bitops.h> +#include <linux/device.h> +#include <linux/io.h> +#include <linux/leds.h> +#include <linux/module.h> +#include <linux/of_device.h> +#include <linux/platform_data/mlxreg.h> +#include <linux/platform_device.h> +#include <linux/regmap.h> + +/* Codes for LEDs. */ +#define MLXREG_LED_OFFSET_BLINK_3HZ 0x01/* Offset from solid: 3Hz blink */ +#define MLXREG_LED_OFFSET_BLINK_6HZ 0x02/* Offset from solid: 6Hz blink */ +#define MLXREG_LED_IS_OFF 0x00/* Off */ +#define MLXREG_LED_RED_SOLID 0x05/* Solid red */ +#define MLXREG_LED_GREEN_SOLID 0x0D/* Solid green */ +#define MLXREG_LED_AMBER_SOLID 0x09/* Solid amber */ +#define MLXREG_LED_BLINK_3HZ 167/* ~167 msec off/on - HW support */ +#define MLXREG_LED_BLINK_6HZ 83/* ~83 msec off/on - HW support */ + +/** +* struct mlxreg_led_data - led control data: +* +* @data: led configuration data; +* @led_classdev: led class data; +* @base_color: base led color (other colors have constant offset from base); +* @led_data: led data; +* @data_parent: pointer to private device control data of parent; +*/ +struct mlxreg_led_data { +struct mlxreg_core_data *data; +struct led_classdev led_cdev; +u8 base_color; +void *data_parent; +char led_cdev_name[MLXREG_CORE_LABEL_MAX_SIZE ]; +}; + +#define cdev_to_priv (c) container_of(c, struct mlxreg_led_data, led_cdev) + +/** +* struct mlxreg_led_priv_data - platform private data: +* +* @pdev: platform device; +* @pdata: platform data; +* @access_lock: mutex for attribute IO access; +*/ +struct mlxreg_led_priv_data { +struct platform_device *pdev; +struct mlxreg_core_platform_data *pdata; +struct mutex access_lock;/* protect IO operations */ +}; + +static int +mlxreg_led_store_hw (struct mlxreg_led_data *led_data,u8 vset) +{ +struct mlxreg_led_priv_data *priv = led_data->data_parent; +struct mlxreg_core_platform_data *led_pdata = priv->pdata; +struct mlxreg_core_data *data = led_data->data; +u32 regval; +u32 nib; +int ret; + +/* +* Each LED is controlled through low or high nibble of the relevant +* register byte. Register offset is specified by off parameter. +* Parameter vset provides color code: 0x0 for off, 0x5 for solid red, +* 0x6 for 3Hz blink red, 0xd for solid green, 0xe for 3Hz blink +* green. +* Parameter mask specifies which nibble is used for specific LED: mask +* 0xf0 - lower nibble is to be used (bits from 0 to 3), mask 0x0f - +* higher nibble (bits from 4 to 7). +*/ +mutex_lock (&priv->access_lock); + + ret =regmap_read (led_pdata->regmap, data->reg, ®val); +if (ret) + goto access_error; + + nib = (ror32 (data->mask, data->bit) ==0xf0 ) ?rol32 (vset, data->bit) : +rol32 (vset, data->bit +4 ); + regval = (regval & data->mask) | nib; + + ret =regmap_write (led_pdata->regmap, data->reg, regval); + +access_error: +mutex_unlock (&priv->access_lock); + +return ret; +} + +static enum led_brightness +mlxreg_led_get_hw (struct mlxreg_led_data *led_data) +{ +struct mlxreg_led_priv_data *priv = led_data->data_parent; +struct mlxreg_core_platform_data *led_pdata = priv->pdata; +struct mlxreg_core_data *data = led_data->data; +u32 regval; +int ret; + +/* +* Each LED is controlled through low or high nibble of the relevant +* register byte. Register offset is specified by off parameter. +* Parameter vset provides color code: 0x0 for off, 0x5 for solid red, +* 0x6 for 3Hz blink red, 0xd for solid green, 0xe for 3Hz blink +* green. +* Parameter mask specifies which nibble is used for specific LED: mask +* 0xf0 - lower nibble is to be used (bits from 0 to 3), mask 0x0f - +* higher nibble (bits from 4 to 7). +*/ + ret =regmap_read (led_pdata->regmap, data->reg, ®val); +if (ret <0 ) { +dev_warn (led_data->led_cdev.dev,"Failed to get current brightness, error: %d\n" , + ret);
drivers/leds/leds-mlxreg.c line 156
Quoted 10 lines
drivers/leds/leds-mlxreg.c new file +10
-0+/* Assume the LED is OFF */ +return LED_OFF ; + } + + regval = regval & ~data->mask; + regval = (ror32 (data->mask, data->bit) ==0xf0 ) ?ror32 (regval, + data->bit) :ror32 (regval, data->bit +4 ); +if (regval >= led_data->base_color && + regval <= (led_data->base_color +MLXREG_LED_OFFSET_BLINK_6HZ )) + ret =LED_FULL ;
Let's have enum led_brightness brightness here instead of ret. It will be consistent with the brightness_get op return type.
Quoted 53 lines
drivers/leds/leds-mlxreg.c new file +53
-0+else + ret =LED_OFF ; + +return ret; +} + +static int +mlxreg_led_brightness_set (struct led_classdev *cled,enum led_brightness value) +{ +struct mlxreg_led_data *led_data =cdev_to_priv (cled); + +if (value) +return mlxreg_led_store_hw (led_data, led_data->base_color); +else +return mlxreg_led_store_hw (led_data,MLXREG_LED_IS_OFF ); +} + +static enum led_brightness +mlxreg_led_brightness_get (struct led_classdev *cled) +{ +struct mlxreg_led_data *led_data =cdev_to_priv (cled); + +return mlxreg_led_get_hw (led_data); +} + +static int +mlxreg_led_blink_set (struct led_classdev *cled,unsigned long *delay_on, +unsigned long *delay_off) +{ +struct mlxreg_led_data *led_data =cdev_to_priv (cled); +int err; + +/* +* HW supports two types of blinking: full (6Hz) and half (3Hz). +* For delay on/off zero LED is setting to solid color. For others +* combination blinking is to be controlled by the software timer. +*/ +if (!(*delay_on ==0 && *delay_off ==0 ) && + !(*delay_on ==MLXREG_LED_BLINK_3HZ && + *delay_off ==MLXREG_LED_BLINK_3HZ ) && + !(*delay_on ==MLXREG_LED_BLINK_6HZ && + *delay_off ==MLXREG_LED_BLINK_6HZ )) +return -EINVAL ; + +if (*delay_on ==MLXREG_LED_BLINK_6HZ ) + err =mlxreg_led_store_hw (led_data, led_data->base_color + +MLXREG_LED_OFFSET_BLINK_6HZ ); +else if (*delay_on ==MLXREG_LED_BLINK_3HZ ) + err =mlxreg_led_store_hw (led_data, led_data->base_color + +MLXREG_LED_OFFSET_BLINK_3HZ ); +else + err =mlxreg_led_store_hw (led_data, led_data->base_color); +
drivers/leds/leds-mlxreg.c line 219
Quoted 10 lines
drivers/leds/leds-mlxreg.c new file +10
-0+return err; +} + +static int mlxreg_led_config (struct mlxreg_led_priv_data *priv) +{ +struct mlxreg_core_platform_data *led_pdata = priv->pdata; +struct mlxreg_core_data *data = led_pdata->data; +struct mlxreg_led_data *led_data; +struct led_classdev *led_cdev; +int brightness;
s/int/enum led_brightness/
Quoted 93 lines
drivers/leds/leds-mlxreg.c new file +92
-0+int i; +int err; + +for (i =0 ; i < led_pdata->counter; i++, data++) { + led_data =devm_kzalloc (&priv->pdev->dev,sizeof (*led_data), +GFP_KERNEL ); +if (!led_data) +return -ENOMEM ; + + led_cdev = &led_data->led_cdev; + led_data->data_parent = priv; +if (strstr (data->label,"red" ) || +strstr (data->label,"orange" )) { + brightness =LED_OFF ; + led_data->base_color =MLXREG_LED_RED_SOLID ; + }else if (strstr (data->label,"amber" )) { + brightness =LED_OFF ; + led_data->base_color =MLXREG_LED_AMBER_SOLID ; + }else { + brightness =LED_OFF ; + led_data->base_color =MLXREG_LED_GREEN_SOLID ; + } +sprintf (led_data->led_cdev_name,"%s:%s" ,"mlxreg" , + data->label); + led_cdev->name = led_data->led_cdev_name; + led_cdev->brightness = brightness; + led_cdev->max_brightness =LED_ON ; + led_cdev->brightness_set_blocking = + mlxreg_led_brightness_set; + led_cdev->brightness_get = mlxreg_led_brightness_get; + led_cdev->blink_set = mlxreg_led_blink_set; + led_cdev->flags =LED_CORE_SUSPENDRESUME ; + led_data->data = data; + err =devm_led_classdev_register (&priv->pdev->dev, led_cdev); +if (err) +return err; + +if (led_cdev->brightness) +mlxreg_led_brightness_set (led_cdev, + led_cdev->brightness); +dev_info (led_cdev->dev,"label: %s, mask: 0x%02x, offset:0x%02x\n" , + data->label, data->mask, data->reg); + } + +return 0 ; +} + +static int mlxreg_led_probe (struct platform_device *pdev) +{ +struct mlxreg_core_platform_data *led_pdata; +struct mlxreg_led_priv_data *priv; + + led_pdata =dev_get_platdata (&pdev->dev); +if (!led_pdata) { +dev_err (&pdev->dev,"Failed to get platform data.\n" ); +return -EINVAL ; + } + + priv =devm_kzalloc (&pdev->dev,sizeof (*priv),GFP_KERNEL ); +if (!priv) +return -ENOMEM ; + +mutex_init (&priv->access_lock); + priv->pdev = pdev; + priv->pdata = led_pdata; + +return mlxreg_led_config (priv); +} + +static int mlxreg_led_remove (struct platform_device *pdev) +{ +struct mlxreg_led_priv_data *priv =dev_get_drvdata (&pdev->dev); + +mutex_destroy (&priv->access_lock); + +return 0 ; +} + +static struct platform_driver mlxreg_led_driver = { + .driver = { + .name ="leds-mlxreg" , + }, + .probe = mlxreg_led_probe, + .remove = mlxreg_led_remove, +}; + +module_platform_driver (mlxreg_led_driver); + +MODULE_AUTHOR ("Vadim Pasternak <[email protected]>" ); +MODULE_DESCRIPTION ("Mellanox LED regmap driver" ); +MODULE_LICENSE ("Dual BSD/GPL" ); +MODULE_ALIAS ("platform:leds-mlxreg" );
Signature · 2 lines
Best regards, Jacek Anaszewski