On 06/27/2017 09:32 PM, matthew.gerlach-VuQAYsv1563Yd54FQh9/CA@public.gmane.org wrote:

[...]

quoted

quoted

Hi Marek,

I am trying to write an MTD/spi-nor driver for version 2 of the
Altera Quadspi contoller.  This controller is soft IP that is deployed
in a FPGA.  As such, this component/driver can be used in wide range of
use cases.  The controller could be used to update EPCQ/EPCS flash
stores containing bit streams, but this component could be used for
flash for filesystems or any non-volatile data store.  My hope is that
all possible use cases should be covered by this driver.

How does this particular case where you have to reverse the bits look
like ?

The use case for reversing the bits involves a processor updating
EPCQ/EPCS flash whose contents are read by the FPGA on power up.  The
processor and Altera Quadspi component, inside the configured FPGA,
access the bits in one way serially, but the hardware that accesses the
flash during power accesses the bits in the opposite way serially.

So it's the same crap Xilinx does, they have some tool to do this with
their bitstream before they write it into flash.

But then, you only have to do it with your bitstream. If you put ie. UBI
after the bitstream part, the UBI can be in normal bit ordering.
So instead of polluting the DT bindings with this, make a similar tool
to what Xilinx has, do the bit shuffling using that tool and then write
the bitstream into the flash in the correct order.

quoted

quoted

quoted

quoted

quoted

quoted

Thinking about this binding more, I wonder if the binding name(s)
should be (read|write)-bit8-reverse to indicate reversings the bits
in a byte as opposed to reversing the bits in a 32 bit word?

I don't think bit reversal is specific to Altera/Intel components.
I see
a nand driver performing bit reversal, and I think I've recently
seen
other FPGA based drivers requiring bit reversal.

$ git grep bit.reverse Documentation/devicetree/ | wc -l
0

So we don't have such a generic binding . It's up to Rob (I guess) to
decide whether this is SoC specific and should've altr, prefix or
not.
IMO it is.

I agree there is no generic binding at this time, and I look forward
to any input from Rob and anyone else on this issue.  I think it is
worth pointing out that this really isn't an issue of an SoC, but
rather
it is an
issue of how data in the flash chip is accessed.I think what makes
this issue
"weird" is that we have different hardware accessing the data in the
flash with a different perspective.  The FPGA looks at the data
from one
perspective on power up, and a processor trying to update the flash
has
a different perspective.

Another thing I'd ask here is, is that bit-reverse a hardware property
or is that some software configuration thing ?

I would say the bit reversal is a property of the FPGA that is reading
the flash at power up.

So it's not a property of the block, but rather of the bus somewhere ?

You are correct, it is not a property of the Altera Quadspi component, but
a property of the fpga and external hardware that access the flash on
power up.

So yes, it's a property of that small thing which loads the bitstream
from the EPCS/EPCQ and programs the cells in the FPGA. This shouldn't be
in this driver nor it's bindings, see above.

-- 
Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html