From: Minkyu Kang <mk7.kang@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] exynos: uart: Use generic api to the uart clk freq
Date: Tue, 04 Jun 2013 17:02:07 +0900 [thread overview]
Message-ID: <51AD9EFF.7090903@samsung.com> (raw)
In-Reply-To: <1364202173-13719-2-git-send-email-akshay.s@samsung.com>
On 25/03/13 18:02, Akshay Saraswat wrote:
> From: Padmavathi Venna <padma.v@samsung.com>
>
> Use generic api to get the uart clock frequency
>
> This patch depends on:
> http://permalink.gmane.org/gmane.comp.boot-loaders.u-boot/154930
>
> Signed-off-by: Padmavathi Venna <padma.v@samsung.com>
> Signed-off-by: Akshay Saraswat <akshay.s@samsung.com>
> ---
> drivers/serial/serial_s5p.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/serial/serial_s5p.c b/drivers/serial/serial_s5p.c
> index 3c41242..7058d55 100644
> --- a/drivers/serial/serial_s5p.c
> +++ b/drivers/serial/serial_s5p.c
> @@ -65,7 +65,7 @@ static const int udivslot[] = {
> void serial_setbrg_dev(const int dev_index)
> {
> struct s5p_uart *const uart = s5p_get_base_uart(dev_index);
> - u32 uclk = get_uart_clk(dev_index);
> + u32 uclk = clock_get_periph_rate(PERIPH_ID_UART0 + dev_index);
> u32 baudrate = gd->baudrate;
> u32 val;
>
>
Since clock_get_periph_rate did not implemented on exynos4, exynos4 will get zero.
So, I'll not accept this patch.
Thanks,
Minkyu Kang.
next prev parent reply other threads:[~2013-06-04 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 9:02 [U-Boot] [PATCH] exynos: i2c: Use generic api to get i2c clk freq Akshay Saraswat
2013-03-25 9:02 ` [U-Boot] [PATCH] exynos: uart: Use generic api to the uart " Akshay Saraswat
2013-06-04 8:02 ` Minkyu Kang [this message]
2013-06-04 7:53 ` [U-Boot] [PATCH] exynos: i2c: Use generic api to get i2c " Minkyu Kang
2013-06-04 8:01 ` Minkyu Kang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51AD9EFF.7090903@samsung.com \
--to=mk7.kang@samsung.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox