From: Jacek Anaszewski <j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Stephan Linz <linz-LlUBiLVY8XKsTnJN9+BGXg@public.gmane.org>
Cc: linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Joseph Jezak" <josejx-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
"Jörg Sommer" <joerg-au2b9oQwubsjnolme5KbmQ@public.gmane.org>,
"Mark Rutland" <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
"Richard Purdie"
<rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.org>,
"Rob Herring" <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Jonathan Corbet" <corbet-T1hC0tSOHrs@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v6] leds: documentation: 'ide-disk' to 'disk-activity'
Date: Mon, 27 Jun 2016 09:04:13 +0200 [thread overview]
Message-ID: <5770CFED.4090300@samsung.com> (raw)
In-Reply-To: <20160624171704.13399-1-linz-LlUBiLVY8XKsTnJN9+BGXg@public.gmane.org>
Hi Stephan,
On 06/24/2016 07:16 PM, Stephan Linz wrote:
> Cc: Joseph Jezak <josejx-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
> Cc: Jörg Sommer <joerg-au2b9oQwubsjnolme5KbmQ@public.gmane.org>
> Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
> Signed-off-by: Stephan Linz <linz-LlUBiLVY8XKsTnJN9+BGXg@public.gmane.org>
> Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> Signed-off-by: Jacek Anaszewski <j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> ---
> Changes in v6:
> - Reorganize v5.
>
> Changes in v5:
> - Keep documentation for the old 'ide-disk' device tree
> binding, but mark as deprecated and refer to the new
> trigger 'disk-activity'.
>
> Changes in v4:
> - Keep the 'ide-disk' trigger and add a second one
> for 'disk-activity'.
>
> Changes in v3:
> - Port to kernel 4.x
> - Split into platform independent and dependent parts.
>
> v2: https://patchwork.ozlabs.org/patch/117485/
> v1: http://dev.gentoo.org/~josejx/ata.patch
> ---
> Documentation/devicetree/bindings/leds/common.txt | 4 +++-
> Documentation/devicetree/bindings/leds/leds-gpio.txt | 4 ++--
> Documentation/laptops/asus-laptop.txt | 2 +-
> Documentation/leds/leds-class.txt | 2 +-
> 4 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
> index af10678..93ef6e6 100644
> --- a/Documentation/devicetree/bindings/leds/common.txt
> +++ b/Documentation/devicetree/bindings/leds/common.txt
> @@ -26,7 +26,9 @@ Optional properties for child nodes:
> "default-on" - LED will turn on (but for leds-gpio see "default-state"
> property in Documentation/devicetree/bindings/gpio/led.txt)
> "heartbeat" - LED "double" flashes at a load average based rate
> - "ide-disk" - LED indicates disk activity
> + "disk-activity" - LED indicates disk activity
> + "ide-disk" - LED indicates IDE disk activity (deprecated),
> + in new implementations use "disk-activity"
> "timer" - LED flashes at a fixed, configurable rate
>
> - led-max-microamp : Maximum LED supply current in microamperes. This property
> diff --git a/Documentation/devicetree/bindings/leds/leds-gpio.txt b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> index cbbeb18..5b1b43a 100644
> --- a/Documentation/devicetree/bindings/leds/leds-gpio.txt
> +++ b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> @@ -33,9 +33,9 @@ Examples:
> leds {
> compatible = "gpio-leds";
> hdd {
> - label = "IDE Activity";
> + label = "Disk Activity";
> gpios = <&mcu_pio 0 GPIO_ACTIVE_LOW>;
> - linux,default-trigger = "ide-disk";
> + linux,default-trigger = "disk-activity";
> };
>
> fault {
> diff --git a/Documentation/laptops/asus-laptop.txt b/Documentation/laptops/asus-laptop.txt
> index 79a1bc6..5f28587 100644
> --- a/Documentation/laptops/asus-laptop.txt
> +++ b/Documentation/laptops/asus-laptop.txt
> @@ -72,7 +72,7 @@ LEDs
> echo 1 > /sys/class/leds/asus::mail/brightness
> will switch the mail LED on.
> You can also know if they are on/off by reading their content and use
> - kernel triggers like ide-disk or heartbeat.
> + kernel triggers like disk-activity or heartbeat.
>
> Backlight
> ---------
> diff --git a/Documentation/leds/leds-class.txt b/Documentation/leds/leds-class.txt
> index 44f5e6b..f1f7ec9 100644
> --- a/Documentation/leds/leds-class.txt
> +++ b/Documentation/leds/leds-class.txt
> @@ -11,7 +11,7 @@ brightness support so will just be turned on for non-zero brightness settings.
> The class also introduces the optional concept of an LED trigger. A trigger
> is a kernel based source of led events. Triggers can either be simple or
> complex. A simple trigger isn't configurable and is designed to slot into
> -existing subsystems with minimal additional code. Examples are the ide-disk,
> +existing subsystems with minimal additional code. Examples are the disk-activity,
> nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
> optimises away.
>
>
Applied, thanks.
--
Best regards,
Jacek Anaszewski
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Stephan Linz <linz@li-pro.net>
Cc: linux-leds@vger.kernel.org, linux-ide@vger.kernel.org,
"Joseph Jezak" <josejx@gentoo.org>,
"Jörg Sommer" <joerg@alea.gnuu.de>,
"Mark Rutland" <mark.rutland@arm.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v6] leds: documentation: 'ide-disk' to 'disk-activity'
Date: Mon, 27 Jun 2016 09:04:13 +0200 [thread overview]
Message-ID: <5770CFED.4090300@samsung.com> (raw)
In-Reply-To: <20160624171704.13399-1-linz@li-pro.net>
Hi Stephan,
On 06/24/2016 07:16 PM, Stephan Linz wrote:
> Cc: Joseph Jezak <josejx@gentoo.org>
> Cc: Jörg Sommer <joerg@alea.gnuu.de>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Stephan Linz <linz@li-pro.net>
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
> ---
> Changes in v6:
> - Reorganize v5.
>
> Changes in v5:
> - Keep documentation for the old 'ide-disk' device tree
> binding, but mark as deprecated and refer to the new
> trigger 'disk-activity'.
>
> Changes in v4:
> - Keep the 'ide-disk' trigger and add a second one
> for 'disk-activity'.
>
> Changes in v3:
> - Port to kernel 4.x
> - Split into platform independent and dependent parts.
>
> v2: https://patchwork.ozlabs.org/patch/117485/
> v1: http://dev.gentoo.org/~josejx/ata.patch
> ---
> Documentation/devicetree/bindings/leds/common.txt | 4 +++-
> Documentation/devicetree/bindings/leds/leds-gpio.txt | 4 ++--
> Documentation/laptops/asus-laptop.txt | 2 +-
> Documentation/leds/leds-class.txt | 2 +-
> 4 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt
> index af10678..93ef6e6 100644
> --- a/Documentation/devicetree/bindings/leds/common.txt
> +++ b/Documentation/devicetree/bindings/leds/common.txt
> @@ -26,7 +26,9 @@ Optional properties for child nodes:
> "default-on" - LED will turn on (but for leds-gpio see "default-state"
> property in Documentation/devicetree/bindings/gpio/led.txt)
> "heartbeat" - LED "double" flashes at a load average based rate
> - "ide-disk" - LED indicates disk activity
> + "disk-activity" - LED indicates disk activity
> + "ide-disk" - LED indicates IDE disk activity (deprecated),
> + in new implementations use "disk-activity"
> "timer" - LED flashes at a fixed, configurable rate
>
> - led-max-microamp : Maximum LED supply current in microamperes. This property
> diff --git a/Documentation/devicetree/bindings/leds/leds-gpio.txt b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> index cbbeb18..5b1b43a 100644
> --- a/Documentation/devicetree/bindings/leds/leds-gpio.txt
> +++ b/Documentation/devicetree/bindings/leds/leds-gpio.txt
> @@ -33,9 +33,9 @@ Examples:
> leds {
> compatible = "gpio-leds";
> hdd {
> - label = "IDE Activity";
> + label = "Disk Activity";
> gpios = <&mcu_pio 0 GPIO_ACTIVE_LOW>;
> - linux,default-trigger = "ide-disk";
> + linux,default-trigger = "disk-activity";
> };
>
> fault {
> diff --git a/Documentation/laptops/asus-laptop.txt b/Documentation/laptops/asus-laptop.txt
> index 79a1bc6..5f28587 100644
> --- a/Documentation/laptops/asus-laptop.txt
> +++ b/Documentation/laptops/asus-laptop.txt
> @@ -72,7 +72,7 @@ LEDs
> echo 1 > /sys/class/leds/asus::mail/brightness
> will switch the mail LED on.
> You can also know if they are on/off by reading their content and use
> - kernel triggers like ide-disk or heartbeat.
> + kernel triggers like disk-activity or heartbeat.
>
> Backlight
> ---------
> diff --git a/Documentation/leds/leds-class.txt b/Documentation/leds/leds-class.txt
> index 44f5e6b..f1f7ec9 100644
> --- a/Documentation/leds/leds-class.txt
> +++ b/Documentation/leds/leds-class.txt
> @@ -11,7 +11,7 @@ brightness support so will just be turned on for non-zero brightness settings.
> The class also introduces the optional concept of an LED trigger. A trigger
> is a kernel based source of led events. Triggers can either be simple or
> complex. A simple trigger isn't configurable and is designed to slot into
> -existing subsystems with minimal additional code. Examples are the ide-disk,
> +existing subsystems with minimal additional code. Examples are the disk-activity,
> nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
> optimises away.
>
>
Applied, thanks.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-06-27 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 17:16 [PATCH v6] leds: documentation: 'ide-disk' to 'disk-activity' Stephan Linz
[not found] ` <20160624171704.13399-1-linz-LlUBiLVY8XKsTnJN9+BGXg@public.gmane.org>
2016-06-27 7:04 ` Jacek Anaszewski [this message]
2016-06-27 7:04 ` Jacek Anaszewski
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=5770CFED.4090300@samsung.com \
--to=j.anaszewski-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=joerg-au2b9oQwubsjnolme5KbmQ@public.gmane.org \
--cc=josejx-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-ide-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linz-LlUBiLVY8XKsTnJN9+BGXg@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rpurdie-Fm38FmjxZ/leoWH0uzbU5w@public.gmane.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.