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
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
