linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	linux-leds@vger.kernel.org
Cc: Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] tools/leds: Add led_hw_brightness_mon program
Date: Sun, 29 Jan 2017 14:37:17 +0100	[thread overview]
Message-ID: <f760c3d4-db3d-b680-ee83-2fd562153102@redhat.com> (raw)
In-Reply-To: <1485690751-4824-1-git-send-email-jacek.anaszewski@gmail.com>

Hi,

On 01/29/2017 12:52 PM, Jacek Anaszewski wrote:
> LED subsystem supports POLLPRI on "brightness_hw_changed" sysfs file
> of LED class devices. This tool demonstrates how to use the feature.
>
> Signed-off-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
> Cc: Hans de Goede <hdegoede@redhat.com>
> Cc: Pavel Machek <pavel@ucw.cz>

Looks good to me:

Acked-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans



> ---
>  tools/leds/Makefile                |  4 +-
>  tools/leds/led_hw_brightness_mon.c | 84 ++++++++++++++++++++++++++++++++++++++
>  2 files changed, 86 insertions(+), 2 deletions(-)
>  create mode 100644 tools/leds/led_hw_brightness_mon.c
>
> diff --git a/tools/leds/Makefile b/tools/leds/Makefile
> index c03a79e..078b666 100644
> --- a/tools/leds/Makefile
> +++ b/tools/leds/Makefile
> @@ -3,11 +3,11 @@
>  CC = $(CROSS_COMPILE)gcc
>  CFLAGS = -Wall -Wextra -g -I../../include/uapi
>
> -all: uledmon
> +all: uledmon led_hw_brightness_mon
>  %: %.c
>  	$(CC) $(CFLAGS) -o $@ $^
>
>  clean:
> -	$(RM) uledmon
> +	$(RM) uledmon led_hw_brightness_mon
>
>  .PHONY: all clean
> diff --git a/tools/leds/led_hw_brightness_mon.c b/tools/leds/led_hw_brightness_mon.c
> new file mode 100644
> index 0000000..1a97064
> --- /dev/null
> +++ b/tools/leds/led_hw_brightness_mon.c
> @@ -0,0 +1,84 @@
> +/*
> + * led_hw_brightness_mon.c
> + *
> + * This program monitors LED brightness level changes having its origin
> + * in hardware/firmware, i.e. outside of kernel control.
> + * A timestamp and brightness value is printed each time the brightness changes.
> + *
> + * Usage: led_notify_mon <device-name>
> + *
> + * <device-name> is the name of the LED class device to be monitored. Pressing
> + * CTRL+C will exit.
> + */
> +
> +#include <errno.h>
> +#include <fcntl.h>
> +#include <poll.h>
> +#include <stdio.h>
> +#include <stdlib.h>
> +#include <string.h>
> +#include <time.h>
> +#include <unistd.h>
> +
> +#include <linux/uleds.h>
> +
> +int main(int argc, char const *argv[])
> +{
> +	int fd, ret;
> +	char brightness_file_path[LED_MAX_NAME_SIZE + 11];
> +	struct pollfd pollfd;
> +	struct timespec ts;
> +	char buf[11];
> +
> +	if (argc != 2) {
> +		fprintf(stderr, "Requires <device-name> argument\n");
> +		return 1;
> +	}
> +
> +	snprintf(brightness_file_path, LED_MAX_NAME_SIZE,
> +		 "/sys/class/leds/%s/brightness_hw_changed", argv[1]);
> +
> +	fd = open(brightness_file_path, O_RDONLY);
> +	if (fd == -1) {
> +		printf("Failed to open %s file\n", brightness_file_path);
> +		return 1;
> +	}
> +
> +	/*
> +	 * read may fail if no hw brightness change has occurred so far,
> +	 * but it is required to avoid spurious poll notifications in
> +	 * the opposite case.
> +	 */
> +	read(fd, buf, sizeof(buf));
> +
> +	pollfd.fd = fd;
> +	pollfd.events = POLLPRI;
> +
> +	while (1) {
> +		ret = poll(&pollfd, 1, -1);
> +		if (ret == -1) {
> +			printf("Failed to poll %s file (%d)\n",
> +				brightness_file_path, ret);
> +			ret = 1;
> +			break;
> +		}
> +
> +		clock_gettime(CLOCK_MONOTONIC, &ts);
> +
> +		ret = read(fd, buf, sizeof(buf));
> +		if (ret < 0)
> +			break;
> +
> +		ret = lseek(pollfd.fd, 0, SEEK_SET);
> +		if (ret < 0) {
> +			printf("lseek failed (%d)\n", ret);
> +			break;
> +		}
> +
> +		printf("[%ld.%09ld] %d\n", ts.tv_sec, ts.tv_nsec, atoi(buf));
> +	}
> +
> +	close(fd);
> +
> +	return ret;
> +}
>

  reply	other threads:[~2017-01-29 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 11:52 [PATCH] tools/leds: Add led_hw_brightness_mon program Jacek Anaszewski
2017-01-29 13:37 ` Hans de Goede [this message]
2017-01-29 16:56 ` Pavel Machek
2017-01-29 19:28   ` 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=f760c3d4-db3d-b680-ee83-2fd562153102@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).