From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] ARM: shmobile: r8a7790: don't use external clock for SCIFs
Date: Wed, 26 Jun 2013 16:33:54 +0400 [thread overview]
Message-ID: <51CADFB2.8040800@cogentembedded.com> (raw)
In-Reply-To: <1372236787-23342-4-git-send-email-horms+renesas@verge.net.au>
Hello.
On 26-06-2013 12:53, Simon Horman wrote:
> From: Ulrich Hecht <ulrich.hecht@gmail.com>
> This is an external component and may or may not be there, while the
> internal clock always works.
> Signed-off-by: Ulrich Hecht <ulrich.hecht@gmail.com>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> arch/arm/mach-shmobile/setup-r8a7790.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/arch/arm/mach-shmobile/setup-r8a7790.c b/arch/arm/mach-shmobile/setup-r8a7790.c
> index 896d374..6531f3d 100644
> --- a/arch/arm/mach-shmobile/setup-r8a7790.c
> +++ b/arch/arm/mach-shmobile/setup-r8a7790.c
> @@ -64,7 +64,7 @@ void __init r8a7790_pinmux_init(void)
> [index] = { \
> SCIF_COMMON(PORT_SCIF, baseaddr, irq), \
> .scbrr_algo_id = SCBRR_ALGO_2, \
> - .scscr = SCSCR_RE | SCSCR_TE | SCSCR_CKE1, \
> + .scscr = SCSCR_RE | SCSCR_TE, \
Backslash should have been aligned with the others above...
WBR, Sergei
next prev parent reply other threads:[~2013-06-26 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 8:53 [PATCH v4 0/4] Renesas sh-sci updates for v3.11 Simon Horman
2013-06-26 8:53 ` [PATCH 1/4] serial: sh-sci: HSCIF support Simon Horman
2013-06-26 8:53 ` [PATCH 2/4] ARM: shmobile: r8a7790: " Simon Horman
2013-06-26 8:53 ` [PATCH 3/4] ARM: shmobile: r8a7790: don't use external clock for SCIFs Simon Horman
2013-06-26 12:33 ` Sergei Shtylyov [this message]
2013-06-26 8:53 ` [PATCH 4/4] serial: sh-sci: Initialise variables before access in sci_set_termios() Simon Horman
2013-06-27 13:01 ` [PATCH v4 0/4] Renesas sh-sci updates for v3.11 Arnd Bergmann
2013-06-27 13:57 ` Simon Horman
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=51CADFB2.8040800@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).