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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 1 Mar 2016 09:59:32 +0100
From:	Martin Kepplinger <martink@...teo.de>
To:	Jonathan Cameron <jic23@...nel.org>, daniel.baluta@...el.com,
	lars@...afoo.de, mranostay@...il.com, hamohammed.sa@...il.com,
	darshanapadmadas@...il.com, mfuzzey@...keon.com,
	octavian.purdila@...el.com, irina.tirdea@...el.com,
	cristina.opriceana@...il.com, vladimir.barinov@...entembedded.com
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>
Subject: extending /sys/.../iio:deviceX/in_accelX_power_mode

Would it be ok, if adding in_accelX_power_mode to a driver, to extend it
so that in_accel_power_mode_available offers:

low_noise low_power low_power_low_noise normal

if there's a default "normal" mode, plus options to increase or decrease
oversampling / power consumption for my device?

Specifically I'm unsure about "low_power_low_noise" being enough
user-friendly. The chip I work with just happens to offer these 4 modes.
Would you leave out "low_power_low_noise" and go with

low_noise low_power normal

or is it not even desired to add "normal" to the list?

Although strictly not necessary, I would add any new addition to the
Documentation as well.

thanks
                            martin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ