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
| ||
|
Date: Mon, 17 Oct 2022 11:16:21 +0200 From: Cédric Le Goater <clg@...d.org> To: linux-spi@...r.kernel.org Cc: Mark Brown <broonie@...nel.org>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, devicetree@...r.kernel.org, linux-aspeed@...ts.ozlabs.org, openbmc@...ts.ozlabs.org, Joel Stanley <joel@....id.au>, Andrew Jeffery <andrew@...id.au>, Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Cédric Le Goater <clg@...d.org> Subject: [PATCH linux v2 0/3] spi: aspeed: Add a "ranges" property Hello, Currently, the Linux Aspeed SMC driver computes the decoding ranges of each CS (AHB memory window on which the flash contents are mapped) from the size of the detected flash device. It seems that some chips have issues with the computed ranges and for these, it would be nice to be able to define custom decoding ranges in the DT. Here is a little series doing that. Thanks, C. Changes in v2 : - Tested by Naresh Solanki - sent preliminary fix independently https://patchwork.kernel.org/project/linux-arm-kernel/patch/20221016155722.3520802-1-clg@kaod.org/ - changed the sysfs file exposing the register values to debugfs. - refresh on 6.1-rc1 Cédric Le Goater (3): spi: dt-bindings: aspeed: Add a ranges property spi: aspeed: Handle custom decoding ranges spi: aspeed: Introduce a "ranges" debugfs file drivers/spi/spi-aspeed-smc.c | 131 +++++++++++++++++- .../bindings/spi/aspeed,ast2600-fmc.yaml | 9 ++ 2 files changed, 138 insertions(+), 2 deletions(-) -- 2.37.3
Powered by blists - more mailing lists