Re: [U-Boot] [PATCH v2 09/11] drivers: serial_sifive: Skip baudrate config if no input clock

On Mon, 2019-01-21 at 12:39 +, Auer, Lukas wrote: > On Sun, 2019-01-20 at 17:07 -0800, Atish Patra wrote: > > On 1/20/19 12:22 PM, Auer, Lukas wrote: > > > Hi Anup, > > > > > > On Fri, 2019-01-18 at 11:19 +, Anup Patel wrote: > > > > From: Atish Patra > > > > > > > > It is possible that

Re: [U-Boot] [PATCH v2 09/11] drivers: serial_sifive: Skip baudrate config if no input clock

On Sun, 2019-01-20 at 17:07 -0800, Atish Patra wrote: > On 1/20/19 12:22 PM, Auer, Lukas wrote: > > Hi Anup, > > > > On Fri, 2019-01-18 at 11:19 +, Anup Patel wrote: > > > From: Atish Patra > > > > > > It is possible that input clock is not available because clk > > > device was not availabl

Re: [U-Boot] [PATCH v2 09/11] drivers: serial_sifive: Skip baudrate config if no input clock

On 1/20/19 12:22 PM, Auer, Lukas wrote: Hi Anup, On Fri, 2019-01-18 at 11:19 +, Anup Patel wrote: From: Atish Patra It is possible that input clock is not available because clk device was not available and 'clock-frequency' DT property is also not available. Why would the clock device n

Re: [U-Boot] [PATCH v2 09/11] drivers: serial_sifive: Skip baudrate config if no input clock

Hi Anup, On Fri, 2019-01-18 at 11:19 +, Anup Patel wrote: > From: Atish Patra > > It is possible that input clock is not available because clk > device was not available and 'clock-frequency' DT property is > also not available. Why would the clock device not be available? I suspect the pro

[U-Boot] [PATCH v2 09/11] drivers: serial_sifive: Skip baudrate config if no input clock

From: Atish Patra It is possible that input clock is not available because clk device was not available and 'clock-frequency' DT property is also not available. In this case, instead of failing we should just skip baudrate config by returning zero. Signed-off-by: Atish Patra Signed-off-by: Anu