Thread (11 messages) 11 messages, 4 authors, 2018-11-20

Clock configuration for the SAMA5D2 NAND controller

From: Boris Brezillon <hidden>
Date: 2018-10-17 13:54:40

On Wed, 17 Oct 2018 15:36:17 +0200
Romain Izard [off-list ref] wrote:
Le mer. 17 oct. 2018 ? 15:03, Boris Brezillon [off-list ref]
a ?crit :
quoted
On Wed, 17 Oct 2018 14:49:27 +0200 Romain Izard
[off-list ref] wrote:
 
quoted
Le mer. 17 oct. 2018 ? 14:38, Boris Brezillon
[off-list ref] a ?crit :  
quoted
 
[...]
quoted
quoted
quoted
Is it 2 times slower or 2 times faster with the new approach? Is the
new calculation providing a working solution, or do you have data
corruption because of that? Is your NAND ONFI compliant?
 
- The number of clock cycles for each configured timing is larger, so
the access times are slower.  
Okay. When calculating the timings by hand, what was reference freq you
used? Did you compare it to the clk freq we have when the NAND controller
driver tweaks the timings?
 
I know that I did the calculations with a 83 MHz clock, but that the kernel
code used a 166 MHz clock instead. The only question is to know whether it
is me or the existing code that is right.
Actually, if you have a test point on the RE pin, there's an easy way
to know who's right: check the freq on RE and compare it to what you
expect it to be.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help