linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jdzheng@broadcom.com (Jiandong Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: BCMRING: Fix UART declaration and clk dev name mismatch
Date: Mon, 7 May 2012 12:34:28 -0700	[thread overview]
Message-ID: <4FA823C4.1070109@broadcom.com> (raw)

Fix bcmring UART declaration and clk dev name mismatch

With 888073d41680e8244232f3d850e0424a4e9de60f (ARM:
bcmring: fix UART declarations), it introduced clk dev name
mismatch and leads to UART initialization failure during boot.

Signed-off-by: Jiandong Zheng<jdzheng@broadcom.com  <http://lists.infradead.org/mailman/listinfo/linux-arm-kernel>>
---
   arch/arm/mach-bcmring/core.c |    4 ++--
   1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/mach-bcmring/core.c b/arch/arm/mach-bcmring/core.c
index adbfb19..5559857 100644
--- a/arch/arm/mach-bcmring/core.c
+++ b/arch/arm/mach-bcmring/core.c
@@ -110,10 +110,10 @@ static struct clk_lookup lookups[] = {
           .con_id = "apb_pclk",
           .clk =&dummy_apb_pclk,
       }, {            /* UART0 */
-        .dev_id = "uarta",
+        .dev_id = "uartA",
           .clk =&uart_clk,
       }, {            /* UART1 */
-        .dev_id = "uartb",
+        .dev_id = "uartB",
           .clk =&uart_clk,
       }, {            /* SP804 timer 0 */
           .dev_id = "sp804",
-- 
1.7.9.5

             reply	other threads:[~2012-05-07 19:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 19:34 Jiandong Zheng [this message]
2012-05-07 21:39 ` [PATCH] ARM: BCMRING: Fix UART declaration and clk dev name mismatch Paul Gortmaker
2012-05-07 21:50   ` Jiandong Zheng
2012-05-07 23:00     ` Paul Gortmaker
2012-05-07 23:14       ` Jiandong Zheng
  -- strict thread matches above, loose matches on Subject: below --
2012-05-01 19:44 Jiandong Zheng
2012-05-02 11:48 ` Sergei Shtylyov
2012-05-02 16:22   ` Jiandong Zheng

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=4FA823C4.1070109@broadcom.com \
    --to=jdzheng@broadcom.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).