Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1269697
| From | Simon Arlott <simon@fire.lp0.eu> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH 2/2] leds-bcm6328: Swap LED ON and OFF definitions |
| Date | 2015-11-15 14:40 +0100 |
| Message-ID | <qv5Hc-20o-13@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <qp1mW-4sA-1@gated-at.bofh.it> <qr8tX-2jQ-7@gated-at.bofh.it> <qr8tX-2jQ-5@gated-at.bofh.it> <qrqhb-5qX-9@gated-at.bofh.it> <qv5Hc-20o-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
The values of BCM6328_LED_MODE_ON and BCM6328_LED_MODE_OFF were named for active low LEDs. These should be swapped so that they are named for the default case of active high LEDs. Signed-off-by: Simon Arlott <simon@fire.lp0.eu> --- On 05/11/15 10:41, Jacek Anaszewski wrote: > On 11/04/2015 04:46 PM, Álvaro Fernández Rojas wrote: >> BCM6328_LED_MODE_ON and BCM6328_LED_MODE_OFF values were extracted from >> Broadcom's GPL code, in which they assume leds are active low by default. >> I can confirm the code is correct as it is right now, since those values >> match the active high / low values of the LEDs managed by GPIO instead >> of by using this driver. > > BCM6328_LED_MODE_ON and BCM6328_LED_MODE_OFF should represent the values > that actually set the LED state according to the current logic. > Otherwise it will confuse people who will be analyzing this code. > We are interested in the logic as it is seen from this driver's > perspective and not GPIO perspective. > > IMO the values should be swapped. drivers/leds/leds-bcm6328.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/leds/leds-bcm6328.c b/drivers/leds/leds-bcm6328.c index 95d0cf9..0329dee 100644 --- a/drivers/leds/leds-bcm6328.c +++ b/drivers/leds/leds-bcm6328.c @@ -48,10 +48,10 @@ BCM6328_SERIAL_LED_SHIFT_DIR) #define BCM6328_LED_MODE_MASK 3 -#define BCM6328_LED_MODE_OFF 0 +#define BCM6328_LED_MODE_ON 0 #define BCM6328_LED_MODE_FAST 1 #define BCM6328_LED_MODE_BLINK 2 -#define BCM6328_LED_MODE_ON 3 +#define BCM6328_LED_MODE_OFF 3 #define BCM6328_LED_SHIFT(X) ((X) << 1) /** @@ -126,9 +126,9 @@ static void bcm6328_led_set(struct led_classdev *led_cdev, *(led->blink_leds) &= ~BIT(led->pin); if ((led->active_low && value == LED_OFF) || (!led->active_low && value != LED_OFF)) - bcm6328_led_mode(led, BCM6328_LED_MODE_OFF); - else bcm6328_led_mode(led, BCM6328_LED_MODE_ON); + else + bcm6328_led_mode(led, BCM6328_LED_MODE_OFF); spin_unlock_irqrestore(led->lock, flags); } @@ -303,8 +303,8 @@ static int bcm6328_led(struct device *dev, struct device_node *nc, u32 reg, val = bcm6328_led_read(mode) >> BCM6328_LED_SHIFT(shift % 16); val &= BCM6328_LED_MODE_MASK; - if ((led->active_low && val == BCM6328_LED_MODE_ON) || - (!led->active_low && val == BCM6328_LED_MODE_OFF)) + if ((led->active_low && val == BCM6328_LED_MODE_OFF) || + (!led->active_low && val == BCM6328_LED_MODE_ON)) led->cdev.brightness = LED_FULL; else led->cdev.brightness = LED_OFF; -- 2.1.4 -- Simon Arlott -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Álvaro Fernández Rojas <noltari@gmail.com> - 2015-11-04 16:50 +0100
Re: [PATCH] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-05 11:50 +0100
[PATCH 2/2] leds-bcm6328: Swap LED ON and OFF definitions Simon Arlott <simon@fire.lp0.eu> - 2015-11-15 14:40 +0100
Re: [PATCH 2/2] leds-bcm6328: Swap LED ON and OFF definitions Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-23 11:30 +0100
[PATCH 1/2] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Simon Arlott <simon@fire.lp0.eu> - 2015-11-15 14:40 +0100
Re: [PATCH 1/2] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-16 15:40 +0100
[PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Simon Arlott <simon@fire.lp0.eu> - 2015-11-16 21:30 +0100
Re: [PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Álvaro Fernández Rojas <noltari@gmail.com> - 2015-11-16 22:40 +0100
Re: [PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Simon Arlott <simon@fire.lp0.eu> - 2015-11-17 08:50 +0100
Re: [PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-17 09:10 +0100
Re: [PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-17 09:20 +0100
[PATCH 1/2 (v3)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Simon Arlott <simon@fire.lp0.eu> - 2015-11-22 21:50 +0100
Re: [PATCH 1/2 (v3)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-23 11:30 +0100
Re: [PATCH 1/2 (v2)] leds-bcm6328: Reuse bcm6328_led_set() instead of copying its functionality Jacek Anaszewski <j.anaszewski@samsung.com> - 2015-11-23 11:30 +0100
csiph-web