Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Jagan Teki
On Fri, Nov 25, 2016 at 9:23 PM, Marek Vasut wrote: > On 11/25/2016 04:19 PM, Phil Edworthy wrote: >> Hi Marek, >> >> On 25 November 2016 14:58 Marek Vasut wrote: >>> On 11/25/2016 03:38 PM, Phil Edworthy wrote: With the existing code, when the requested SPI clock rate is near

Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Phil Edworthy
Hi Jagan, On 25 November 2016 15:42 Jagan Teki wrote: > On Fri, Nov 25, 2016 at 8:08 PM, Phil Edworthy > wrote: > > With the existing code, when the requested SPI clock rate is near > > to the lowest that can be achieved by the hardware (max divider > > of the ref

Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Marek Vasut
On 11/25/2016 04:19 PM, Phil Edworthy wrote: > Hi Marek, > > On 25 November 2016 14:58 Marek Vasut wrote: >> On 11/25/2016 03:38 PM, Phil Edworthy wrote: >>> With the existing code, when the requested SPI clock rate is near >>> to the lowest that can be achieved by the hardware (max divider >>>

Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Jagan Teki
On Fri, Nov 25, 2016 at 8:08 PM, Phil Edworthy wrote: > With the existing code, when the requested SPI clock rate is near > to the lowest that can be achieved by the hardware (max divider > of the ref clock is 32), the generated clock rate is wrong. > For example, with

Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Phil Edworthy
Hi Marek, On 25 November 2016 14:58 Marek Vasut wrote: > On 11/25/2016 03:38 PM, Phil Edworthy wrote: > > With the existing code, when the requested SPI clock rate is near > > to the lowest that can be achieved by the hardware (max divider > > of the ref clock is 32), the generated clock rate is

Re: [U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Marek Vasut
On 11/25/2016 03:38 PM, Phil Edworthy wrote: > With the existing code, when the requested SPI clock rate is near > to the lowest that can be achieved by the hardware (max divider > of the ref clock is 32), the generated clock rate is wrong. > For example, with a 50MHz ref clock, when asked for

[U-Boot] [PATCH v2 2/8] spi: cadence_qspi: Fix baud rate calculation

2016-11-25 Thread Phil Edworthy
With the existing code, when the requested SPI clock rate is near to the lowest that can be achieved by the hardware (max divider of the ref clock is 32), the generated clock rate is wrong. For example, with a 50MHz ref clock, when asked for anything less than a 1.5MHz SPI clock, the code sets up