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: Fri, 10 Jan 2020 14:58:54 +0000 From: John Garry <john.garry@...wei.com> To: Mark Brown <broonie@...nel.org> CC: <tudor.ambarus@...rochip.com>, <linux-kernel@...r.kernel.org>, <chenxiang66@...ilicon.com>, <linuxarm@...wei.com>, <linux-spi@...r.kernel.org>, <marek.vasut@...il.com>, <linux-mtd@...ts.infradead.org>, <xuejiancheng@...ilicon.com>, <fengsheng5@...wei.com>, Mika Westerberg <mika.westerberg@...ux.intel.com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, wanghuiqiang <wanghuiqiang@...wei.com>, <liusimin4@...wei.com> Subject: Re: [PATCH v2 2/3] spi: Add HiSilicon v3xx SPI NOR flash controller driver On 10/01/2020 14:07, Mark Brown wrote: + Mika, Andy > On Fri, Jan 10, 2020 at 11:55:37AM +0000, John Garry wrote: > Hi Mark, >> I will note that PRP0001+"jedec,spi-nor" compatible DSD seems to be the >> defacto method to describe the SPI NOR-compat part for ACPI - that's what >> I'm using. We could add properties there, but that seems improper. > > OK, so that's just reusing the DT binding in which case everything > that's valid for the DT binding should also be valid for ACPI - I > thought that actually worked automatically without you having to do > anything in the code but ICBW. I thought that it would be improper as we could be mixing ACPI methods to describe the serial bus (SPI Serial Bus Connection Resource Descriptor) and also DT properties which could conflict, like CS active high. However I do see extra properties than "compatible" being added in DSD for PRP0001: https://patchwork.ozlabs.org/patch/662813/ (see EEPROM part) And if we were to do this, I think that we would need to add some device_property_read_u32("spi-rx-bus-width", ...), etc calls in the SPI FW parsing for ACPI path - I couldn't see that. Thanks, John
Powered by blists - more mailing lists