On 28 July 2015 at 16:33, Marek Vasut <ma...@denx.de> wrote:
> On Tuesday, July 28, 2015 at 11:07:57 AM, Michal Suchanek wrote:
>> This 1.8V SPI NOR flash is found on ARM Chromebook XE303C and reads
>> something like 25LQ32VIG in the middle.
>>
>> Signed-off-by: Michal Suchanek <hramr...@gmail.com>
>> ---
>> drivers/mtd/spi-nor/spi-nor.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
>> index d78831b..cba3bd0 100644
>> --- a/drivers/mtd/spi-nor/spi-nor.c
>> +++ b/drivers/mtd/spi-nor/spi-nor.c
>> @@ -559,6 +559,7 @@ static const struct spi_device_id spi_nor_ids[] = {
>>
>> /* GigaDevice */
>> { "gd25q32", INFO(0xc84016, 0, 64 * 1024, 64, SECT_4K) },
>> + { "gd25lq32c", INFO(0xc86016, 0, 64 * 1024, 64, SECT_4K) },
>> { "gd25q64", INFO(0xc84017, 0, 64 * 1024, 128, SECT_4K) },
>> { "gd25q128", INFO(0xc84018, 0, 64 * 1024, 256, SECT_4K) },
>
> Don't we have DT bindings, so we can use jedec,spi-nor prop for all
> new SPI NORs without growing this table ?
When jedec,spi-nor compatible is used an attempt is made to identify
the chip using this table.
When the ID is not in the table (or is misread due to transfer error)
spi-nor probe fails.
Thanks
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
