[U-Boot] [PATCH v2] spi: cadence_qspi_apb: Use 32 bit indirect write transaction when possible

Vignesh R vigneshr at ti.com
Tue Dec 6 06:24:28 CET 2016


Hi,

On Thursday 01 December 2016 09:41 AM, Vignesh R wrote:
[...]
>>> Data slave port does accept byte, half-word and word access, there
>>> are
>>> no data aborts. But indirect write controller seems to have
>>> limitation(as documented in section 11.15.4.9.2) couping with non 32-
>>> bit
>>> data writes on TI platform. For example with current driver if I try:
>>>
>>> fatload mmc 0 0x82000000 zImage
>>> sf erase 0x0 0x500000
>>> sf write 0x82000000 0x0 0x35
>>> sf read 0xA0000000 0x0 0x35
>>>
>>>
>>> md.b 0xA0000000
>>> a0000000: 00 00 a0 00 00 00 a0 00 00 00 a0 00 00 00 a0 00
>>> a0000010: 00 00 a0 00 00 00 a0 00 00 00 a0 00 00 00 a0 00
>>> a0000020: 03 00 00 00 18 28 6f 00 00 00 00 00 d8 5b 35 00
>>> a0000030: 01 02 03 00 00 00 00 00 00 00 00 00 00 00 00 00
>>> md.b 0x82000000
>>> 82000000: 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1
>>> 82000010: 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1 00 00 a0 e1
>>> 82000020: 03 00 00 ea 18 28 6f 01 00 00 00 00 d8 5b 35 00
>>> 82000030: 01 02 03 04 00 90 0f e1 88 07 00 eb 01 70 a0 e1
>>>
>>>
>>> As you can see, every fourth byte turn out to be 0x00. Therefore this
>>> patch is required.
>>
>> Thanks Vignesh
>>
>> Interesting to know that the newer version of controller has this
>> constrain. Let me pull out my board to ensure this patch doesn't break
>> the SOCFPGA
>>

Did you get a chance to test this patch? There is also a similar patch
for indirect read as well[1], it would be great if you could give your
Tested-by for both the patches. Thanks!

[1]https://patchwork.ozlabs.org/patch/700990/
-- 
Regards
Vignesh


More information about the U-Boot mailing list