linux-kernel - Re: [PATCH] spi: spi-bcm2835.c: Fix 3-wire 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: <42a533cbf1e47ab8c8a44c5e865ec15193a2e956.camel@analog.com>
Date:   Mon, 1 Jul 2019 14:21:21 +0000
From:   "Sa, Nuno" <Nuno.Sa@...log.com>
To:     "lukas@...ner.de" <lukas@...ner.de>
CC:     "linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
        "bcm-kernel-feedback-list@...adcom.com" 
        <bcm-kernel-feedback-list@...adcom.com>,
        "broonie@...nel.org" <broonie@...nel.org>,
        "kernel@...tin.sperl.org" <kernel@...tin.sperl.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "sbranden@...adcom.com" <sbranden@...adcom.com>,
        "wahrenst@....net" <wahrenst@....net>,
        "f.fainelli@...il.com" <f.fainelli@...il.com>,
        "linux-rpi-kernel@...ts.infradead.org" 
        <linux-rpi-kernel@...ts.infradead.org>,
        "eric@...olt.net" <eric@...olt.net>,
        "rjui@...adcom.com" <rjui@...adcom.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] spi: spi-bcm2835.c: Fix 3-wire mode

On Mon, 2019-07-01 at 13:55 +0200, Lukas Wunner wrote:
> I see.  In that case, try:
> 
>  	/* handle all the 3-wire mode */
> -	if ((spi->mode & SPI_3WIRE) && (tfr->rx_buf))
> +	if ((spi->mode & SPI_3WIRE) && (tfr->rx_buf != ctlr->dummy_rx))
>  		cs |= BCM2835_SPI_CS_REN;
>  	else
>  		cs &= ~BCM2835_SPI_CS_REN;
> 

This worked fine. Also, I did a quick backport of the state of your
driver's (both spi-bcm2835 and bcm2835-dma) in revpi_staging and it
also worked fine with my device.
So, as far as I understand, the above suggestion (or my patch) is not
intended to be upstreamed, right? It is just a temporary fix that I can
use while your patchset gets upstream.

Thanks for your help!
Nuno Sá