Re: [U-Boot] [PATCH 2/2] mv_ddr: ddr3: only use active chip-selects when tuning ODT

2019-03-19 Thread Stefan Roese
On 28.02.19 22:11, Chris Packham wrote: From: Chris Packham Inactive chip-selects will give invalid values for read_sample so don't consider them when trying to determine the overall min/max read sample. Signed-off-by: Chris Packham [https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvel

Re: [U-Boot] [PATCH 2/2] mv_ddr: ddr3: only use active chip-selects when tuning ODT

2019-03-03 Thread Baruch Siach
Hi Chris, On Thu, Feb 28 2019, Chris Packham wrote: > From: Chris Packham > > Inactive chip-selects will give invalid values for read_sample so don't > consider them when trying to determine the overall min/max read sample. > > Signed-off-by: Chris Packham > > [https://github.com/MarvellEmbedded

[U-Boot] [PATCH 2/2] mv_ddr: ddr3: only use active chip-selects when tuning ODT

2019-02-28 Thread Chris Packham
From: Chris Packham Inactive chip-selects will give invalid values for read_sample so don't consider them when trying to determine the overall min/max read sample. Signed-off-by: Chris Packham [https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell/pull/18] Signed-off-by: Chris Packham -