From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Richard Purdie <rpurdie@rpsys.net>,
Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 3/3] leds: gpio: Support the "panic-indicator" firmware property
Date: Thu, 14 Apr 2016 10:57:15 +0200 [thread overview]
Message-ID: <570F5B6B.3000702@samsung.com> (raw)
In-Reply-To: <1460570899-24642-4-git-send-email-ezequiel@vanguardiasur.com.ar>
Hi Ezequiel,
It would be good to update also leds-gpio bindings,
of course in a separate patch:
Documentation/devicetree/bindings/leds/leds-gpio.txt
Thanks,
Jacek Anaszewski
On 04/13/2016 08:08 PM, Ezequiel Garcia wrote:
> Calling a GPIO LEDs is quite likely to work even if the kernel
> has paniced, so they are ideal to blink in this situation.
> This commit adds support for the new "panic-indicator"
> firmware property, allowing to mark a given LED to blink on
> a kernel panic.
>
> Signed-off-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
> drivers/leds/leds-gpio.c | 4 ++++
> include/linux/leds.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
> index 61143f55597e..8229f063b483 100644
> --- a/drivers/leds/leds-gpio.c
> +++ b/drivers/leds/leds-gpio.c
> @@ -127,6 +127,8 @@ static int create_gpio_led(const struct gpio_led *template,
> led_dat->cdev.brightness = state ? LED_FULL : LED_OFF;
> if (!template->retain_state_suspended)
> led_dat->cdev.flags |= LED_CORE_SUSPENDRESUME;
> + if (template->panic_indicator)
> + led_dat->cdev.flags |= LED_PANIC_INDICATOR;
>
> ret = gpiod_direction_output(led_dat->gpiod, state);
> if (ret < 0)
> @@ -200,6 +202,8 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
>
> if (fwnode_property_present(child, "retain-state-suspended"))
> led.retain_state_suspended = 1;
> + if (fwnode_property_present(child, "panic-indicator"))
> + led.panic_indicator = 1;
>
> ret = create_gpio_led(&led, &priv->leds[priv->num_leds],
> dev, NULL);
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index 49adf9c6e326..1067fb5f9296 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -359,6 +359,7 @@ struct gpio_led {
> unsigned gpio;
> unsigned active_low : 1;
> unsigned retain_state_suspended : 1;
> + unsigned panic_indicator : 1;
> unsigned default_state : 2;
> /* default_state should be one of LEDS_GPIO_DEFSTATE_(ON|OFF|KEEP) */
> struct gpio_desc *gpiod;
>
next prev parent reply other threads:[~2016-04-14 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 18:08 [PATCH v2 0/3] Extend the LED panic trigger Ezequiel Garcia
2016-04-13 18:08 ` [PATCH v2 1/3] leds: triggers: Allow to switch the trigger to "panic" on a kernel panic Ezequiel Garcia
2016-04-13 18:08 ` [PATCH v2 2/3] devicetree: leds: Introduce "panic-indicator" optional property Ezequiel Garcia
2016-04-14 16:33 ` Rob Herring
2016-04-14 16:46 ` Robin Murphy
2016-04-13 18:08 ` [PATCH v2 3/3] leds: gpio: Support the "panic-indicator" firmware property Ezequiel Garcia
2016-04-14 8:57 ` Jacek Anaszewski [this message]
2016-04-19 16:18 ` Ezequiel Garcia
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=570F5B6B.3000702@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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