Re: [PATCH 2/2] mv_ddr: ddr3: Update {min,max}_read_sample calculation

2020-05-26 Thread Stefan Roese
On 27.05.20 03:31, Chris Packham wrote: From: Chris Packham Measurements on actual hardware shown that the read ODT is early by 3 clocks. Adjust the calculation to avoid this. Signed-off-by: Chris Packham [upstream https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell/pull/22] Signed-o

Re: [PATCH 2/2] mv_ddr: ddr3: Update {min, max}_read_sample calculation

2020-05-26 Thread Baruch Siach
Hi Chris, On Wed, May 27 2020, Chris Packham wrote: > From: Chris Packham > > Measurements on actual hardware shown that the read ODT is early by 3 > clocks. Adjust the calculation to avoid this. > > Signed-off-by: Chris Packham > > [upstream https://github.com/MarvellEmbeddedProcessors/mv-ddr-

[PATCH 2/2] mv_ddr: ddr3: Update {min,max}_read_sample calculation

2020-05-26 Thread Chris Packham
From: Chris Packham Measurements on actual hardware shown that the read ODT is early by 3 clocks. Adjust the calculation to avoid this. Signed-off-by: Chris Packham [upstream https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell/pull/22] Signed-off-by: Chris Packham --- drivers/ddr/ma