linux-kernel - Re: [PATCH] spi: sc18is602: Don't be that restrictive with the maximum transfer speed

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140317112757.GB11706@sirena.org.uk>
Date:	Mon, 17 Mar 2014 11:27:57 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Axel Lin <axel.lin@...ics.com>, linux-spi@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] spi: sc18is602: Don't be that restrictive with the
 maximum transfer speed

On Sun, Mar 16, 2014 at 08:53:09PM -0700, Guenter Roeck wrote:
> On 03/16/2014 07:07 PM, Axel Lin wrote:

> >Now I'm thinking if it is ok to use master->max_speed_hz as transfer speed when
> >xfer->speed_hz > master->max_speed_hz. And it should be handled in spi core.
> >I'm sending a RFC patch now.

> That is an acceptable alternate solution for me.

That's what I'd expect, take the maximum possible given the available
constraints.

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