Re: [PATCH 08/24] omap4: clocks: Make Uart driver's clock calls OMAP4 compatible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Santosh Shilimkar <santosh.shilimkar@xxxxxx> [100216 07:55]:
> From: Abhijit Pagare <abhijitpagare@xxxxxx>
> 
> The uart driver has been adapted for the OMAP4 way of clock calls.
> 
> Signed-off-by: Abhijit Pagare <abhijitpagare@xxxxxx>
> ---
>  arch/arm/mach-omap2/serial.c |   24 ++++++++++++++++--------
>  1 files changed, 16 insertions(+), 8 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index b79bc89..97859b0 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -257,7 +257,8 @@ static inline void omap_uart_enable_clocks(struct omap_uart_state *uart)
>  		return;
>  
>  	clk_enable(uart->ick);
> -	clk_enable(uart->fck);
> +	if (!cpu_is_omap44xx())
> +		clk_enable(uart->fck);
>  	uart->clocked = 1;
>  	omap_uart_restore_context(uart);
>  }
> @@ -272,7 +273,8 @@ static inline void omap_uart_disable_clocks(struct omap_uart_state *uart)
>  	omap_uart_save_context(uart);
>  	uart->clocked = 0;
>  	clk_disable(uart->ick);
> -	clk_disable(uart->fck);
> +	if (!cpu_is_omap44xx())
> +		clk_disable(uart->fck);
>  }

As discussed outside the lists, the fck handling for omap4 should be
done with dummy_ck the same way as we're already doing for omap1. 

Regards,

Tony
  
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux