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: <ZmhdWw/dV5HRU/Nh@colin-ia-desktop>
Date: Tue, 11 Jun 2024 09:21:15 -0500
From: Colin Foster <colin.foster@...advantage.com>
To: Mark Brown <broonie@...nel.org>,
	Louis Chauvet <louis.chauvet@...tlin.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
	miquel.raynal@...tlin.com
Subject: Re: omap2-mcspi multi mode

Hi Louis,

On Fri, Jun 07, 2024 at 04:45:43PM +0100, Mark Brown wrote:
> On Thu, Jun 06, 2024 at 10:14:27PM -0500, Colin Foster wrote:
> 
> > So I think the question I have is:
> 
> > Should the CS line be de-asserted at the end of "spi_write"?
> 
> Absent bodging with cs_change after any spi message the chip select
> should be left deasserted.

Do you have hardware to reproduce my results of two spi messages no
longer toggling the CS line and leaving the line at GND through the
transactions?


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ