linux-kernel - [PATCH 0/2] pwm: some improvements to sysfs interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue,  5 Aug 2014 17:12:16 +0200
From:	Aurelio Colosimo <aurelio.colosimo@...il.com>
To:	Thierry Reding <thierry.reding@...il.com>,
	Randy Dunlap <rdunlap@...radead.org>
Cc:	linux-pwm@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org,
	Aurelio Colosimo <aurelio@...eliocolosimo.it>
Subject: [PATCH 0/2] pwm: some improvements to sysfs interface

This set of patches adds two more features in pwm sysfs, which I
developed for the driver of my pwm device (a virtualization of
AVR pwm outputs, not submitted to mainline yet):
    
- an optional static name for each pwm device, so that driver develop
  can give a name to the output itself, in a similar way as gpio system
  does;
    
- the attribute 'max', and the attribute 'resolution', in
  nanoseconds, specific for each pwm device.
    
  Each new field is initialized with a default (meaningful) value;
  anyway, if desired, pwm drivers maintainers should fix their
  drivers in order to use the new fields.
    
Aurelio Colosimo (2):
  pwm: new field name added to pwm_device
  pwm: new fields, max and resolution, added to sysfs

 drivers/pwm/core.c  |  2 ++
 drivers/pwm/sysfs.c | 29 ++++++++++++++++++++++++++++-
 include/linux/pwm.h |  3 +++
 3 files changed, 33 insertions(+), 1 deletion(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/