| 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
| ||
|
Message-ID: <acaf2d70-d821-4951-9072-931cb56b1b9f@leemhuis.info> Date: Fri, 21 Jun 2024 10:21:26 +0200 From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info> To: Colin Foster <colin.foster@...advantage.com>, 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, Linux kernel regressions list <regressions@...ts.linux.dev> Subject: Re: omap2-mcspi multi mode On 11.06.24 16:21, Colin Foster wrote: > 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? Hmmm, I might have missed something, but it looks like nothing happened since that exchange. Did this regression fall through the cracks or can I consider the issue resolved for some reason? Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page. #regzbot poke
Powered by blists - more mailing lists