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-prev] [day] [month] [year] [list]
Date:   Wed, 17 May 2017 10:04:07 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Seraphime Kirkovski <kirkseraph@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 1/2] spi: spidev: introduce
 SPI_IOC_WR_DEFAULT_MAX_SPEED_HZ command

On Mon, May 15, 2017 at 10:17:11AM +0200, Seraphime Kirkovski wrote:
> On Sun, May 14, 2017 at 06:27:16PM +0900, Mark Brown wrote:

> > Do we have any evidence that such users exist?  

> I can't guarantee for other such users, but this change did disturb our 
> workflow. We were using this feature to prototype and test 
> hardware/firmware at different speeds.

> I was thinking this morning that maybe a sysfs interface will be better 
> for setting global settings. Do you prefer ?

I just don't see this as something that should be being varied at
runtime; it is supposed to be the maximum speed that the bus can be run
at, that's not something that should vary at runtime.  Possibly a sysfs
thing but honestly if you're prototyping via spidev I'd just set the
speed in your application each time it starts.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ