linux-kernel - Re: [PATCH v2] memory: dfl-emif: Update the dfl emif driver support revision 1

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]

Message-Id: <165821962017.31298.6008809074231024823.b4-ty@linaro.org>
Date:   Tue, 19 Jul 2022 10:33:41 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Santosh Shilimkar <ssantosh@...nel.org>, tianfei.zhang@...el.com
Cc:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        trix@...hat.com, russell.h.weight@...el.com,
        linux-fpga@...r.kernel.org, debaratix.biswas@...el.com,
        matthew.gerlach@...ux.intel.com, yilun.xu@...el.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] memory: dfl-emif: Update the dfl emif driver support revision 1

On Wed, 13 Jul 2022 09:03:55 -0400, Tianfei Zhang wrote:
> From: Debarati Biswas <debaratix.biswas@...el.com>
> 
> The next generation (revision 1) of the DFL EMIF feature device requires
> support for more than 4 memory banks. It does not support the selective
> clearing of memory banks. A capability register replaces the previous
> control register, and contains a bitmask to indicate the presence of each
> memory bank. This bitmask aligns with the previous control register
> bitmask that served the same purpose. The control and capability
> registers are treated like a C Union structure in order to support both
> the new and old revisions of the EMIF device.
> 
> [...]

Applied, thanks!

[1/1] memory: dfl-emif: Update the dfl emif driver support revision 1
      https://git.kernel.org/krzk/linux-mem-ctrl/c/d16232de82d64ce02fe6d43aa51de004755de5e5

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>