linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxs: Change duart device to use amba-pl011
Date: Tue, 4 Jan 2011 13:41:54 +0800	[thread overview]
Message-ID: <20110104054153.GA13140@freescale.com> (raw)
In-Reply-To: <20110103103913.GE26785@n2100.arm.linux.org.uk>

Hi Russell,

On Mon, Jan 03, 2011 at 10:39:13AM +0000, Russell King - ARM Linux wrote:
> On Mon, Dec 27, 2010 at 07:49:40PM +0800, Shawn Guo wrote:
> > I did not see this problem. It's true that the clock is turned off
> > in amba_device_register. But later, the clock will be turned on
> > again by amba_probe -> amba_get_enable_pclk very soon.
> > 
> > But we should add something like below in mx28_clocks_init to reflect
> > the clock status and get usecount updated.
> > 
> > 	clk_enable(&uart_clk)
> > 
> > I ran into similar problem with fec driver, and would cover that in
> > fec patch set.
> 
> This sounds like entirely the wrong approach.  Please take some time to
> understand that there are different clocks which do different things.
> 
> The PCLK is the name ARM Ltd give to the APB bus clock.  This we name
> apb_pclk, and we expect platforms to provide it where possible.  This
> name will be looked up for every primecell device on the system.
> 
> If you don't provide an apb_pclk, it will find the device specific
> function clock.  This in itself is no bad thing, unless you use the
> device outside of the AMBA driver (iow, before probe or after remove)
> and helps identify when you've forgotten to provide an apb_pclk.
> 
I intended to let the amba bus driver get duart clock. But you are
right, I should provide an apb_pclk since it actually exists on mxs
processors. In case of duart, it is xbus (apbx) clock.

	_REGISTER_CLOCK("duart", "apb_pclk", xbus_clk)

Thanks for the comment. 

-- 
Regards,
Shawn

  reply	other threads:[~2011-01-04  5:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 14:57 [PATCH v8 00/15] ARM: mxs: Add initial support for MX23 and MX28 Shawn Guo
2010-12-20 14:57 ` [PATCH v8 05/15] ARM: mxs: Add low-level debug UART support Shawn Guo
2010-12-20 14:57 ` [PATCH v8 08/15] ARM: mxs: Add iomux support Shawn Guo
2010-12-20 14:57 ` [PATCH v8 13/15] ARM: mxs: Add initial mx23evk support Shawn Guo
2010-12-20 21:29 ` [PATCH v8 00/15] ARM: mxs: Add initial support for MX23 and MX28 Uwe Kleine-König
2010-12-21  8:45   ` Shawn Guo
2010-12-21 13:26   ` Shawn Guo
2010-12-21 13:12 ` [PATCH] ARM: mxs: Change duart device to use amba-pl011 Shawn Guo
2010-12-21 20:31   ` Wolfram Sang
2010-12-22  2:10     ` Shawn Guo
2010-12-22 11:41       ` Wolfram Sang
2010-12-22 20:25   ` Uwe Kleine-König
2010-12-27 11:49     ` Shawn Guo
2010-12-29  8:38       ` Uwe Kleine-König
2011-01-03 10:39       ` Russell King - ARM Linux
2011-01-04  5:41         ` Shawn Guo [this message]
2011-01-03 10:35     ` Russell King - ARM Linux
2010-12-28 15:23 ` [PATCH v2] " Shawn Guo
2010-12-29  9:12   ` Uwe Kleine-König
2010-12-31  5:16     ` Shawn Guo
2010-12-31  5:50 ` [PATCH v3] " Shawn Guo
2011-01-04  6:20 ` [PATCH v4] " Shawn Guo
2011-01-10 13:34   ` Wolfram Sang

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=20110104054153.GA13140@freescale.com \
    --to=shawn.guo@freescale.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).