linux-kernel - Re: [PATCH v4] memory: renesas-rpc-if: Fix HF/OSPI data transfer in Manual 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 13 Apr 2022 11:53:18 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Krzysztof Kozlowski <krzk@...nel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>
Cc:     linux-kernel@...r.kernel.org,
        Wolfram Sang <wsa+renesas@...g-engineering.com>,
        linux-renesas-soc@...r.kernel.org, linux-mtd@...ts.infradead.org,
        Andrew Gabbasov <andrew_gabbasov@...tor.com>,
        Sergey Shtylyov <s.shtylyov@....ru>,
        Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
        Duc Nguyen <duc.nguyen.ub@...esas.com>
Subject: Re: [PATCH v4] memory: renesas-rpc-if: Fix HF/OSPI data transfer in
 Manual Mode

On 13/04/2022 11:48, Krzysztof Kozlowski wrote:
> On Mon, 11 Apr 2022 14:53:45 +0200, Geert Uytterhoeven wrote:
>> HyperFlash devices fail to probe:
>>
>>     rpc-if-hyperflash rpc-if-hyperflash: probing of hyperbus device failed
>>
>> In HyperFlash or Octal-SPI Flash mode, the Transfer Data Enable bits
>> (SPIDE) in the Manual Mode Enable Setting Register (SMENR) are derived
>> from half of the transfer size, cfr. the rpcif_bits_set() helper
>> function.  However, rpcif_reg_{read,write}() does not take the bus size
>> into account, and does not double all Manual Mode Data Register access
>> sizes when communicating with a HyperFlash or Octal-SPI Flash device.
>>
>> [...]
> 
> Applied, thanks!
> 
> [1/1] memory: renesas-rpc-if: Fix HF/OSPI data transfer in Manual Mode
>       commit: 953d7e7cedb49fec97807166be6fa1ecec1cf0c4
> 


Amended. This is not a proper tag:

WARNING: Unexpected content after email: 'Lad Prabhakar
<prabhakar.mahadev-lad.rj@...renesas.com> [QSPI]', should be: 'Lad
Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com> (QSPI)'
#30:
Tested-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com> [QSPI]


Best regards,
Krzysztof