linux-kernel - Re: omap2-mcspi multi mode

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: <ZmMrJ8uaw85a03Ce@finisterre.sirena.org.uk>
Date: Fri, 7 Jun 2024 16:45:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Colin Foster <colin.foster@...advantage.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
	miquel.raynal@...tlin.com
Subject: Re: omap2-mcspi multi mode

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.

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