linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 06/13] picoxcell: add support for system clks
Date: Wed, 8 Dec 2010 17:39:51 +0000	[thread overview]
Message-ID: <20101208173951.GH2716@pulham.picochip.com> (raw)
In-Reply-To: <20101208161807.GN9777@n2100.arm.linux.org.uk>

On Wed, Dec 08, 2010 at 04:18:07PM +0000, Russell King - ARM Linux wrote:
> On Tue, Nov 23, 2010 at 10:06:07AM +0000, Jamie Iles wrote:
> > The different picoXcell device variants have different numbers of clocks
> > and different capabilities (PC3X2 doesn't have any gateable or
> > controllable clocks). Add the infrastructure necessary for device
> > variants to provide their own clock implementation.
> 
> Fro the looks of this, you only allow one lookup per clk?  That's
> rather sub-optimal, and could cause you problems in the future when
> you may want to have aliases to cater for differences in the SoC
> clock layout.

Hmm, I hadn't thought of that. The number of clocks in our chips appears 
to be rapidly multiplying so that seems like a very good idea.

I guess for PC3X2 where we don't have any gateable or controllable 
clocks that means I can create one virtual clock then add a number of 
aliases where drivers require a struct clk.

Thanks,

Jamie

  reply	other threads:[~2010-12-08 17:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 10:06 ARM: add initial support for Picochip picoXcell SoC Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 01/13] picoxcell: add support for picoXcell Jamie Iles
2010-11-26 11:08   ` [PATCH] " Jamie Iles
2010-12-08 16:09   ` [RFC PATCH 01/13] " Russell King - ARM Linux
2010-12-08 16:52     ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 02/13] picoxcell: add support for AXI bus snoopers Jamie Iles
2010-12-08 16:10   ` Russell King - ARM Linux
2010-12-08 16:52     ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 03/13] picoxcell: add support for the system timers Jamie Iles
2010-11-26 11:11   ` [RFC PATCHv2] " Jamie Iles
2010-12-08 16:14     ` Russell King - ARM Linux
2010-12-08 17:26       ` Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 04/13] picoxcell: add a pin muxing infrastructure Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 05/13] picoxcell: add gpio infrastructure Jamie Iles
2010-11-30 18:08   ` [RFC PATCHv2 " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 06/13] picoxcell: add support for system clks Jamie Iles
2010-12-08 16:18   ` Russell King - ARM Linux
2010-12-08 17:39     ` Jamie Iles [this message]
2010-11-23 10:06 ` [RFC PATCH 07/13] picoxcell: add common SoC devices Jamie Iles
2010-11-26 11:13   ` [RFC PATCHv2] " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 08/13] picoxcell: add cpufreq support Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 09/13] picoxcell: add support for pm Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 10/13] picoxcell: add chained GPIO IRQ handlers Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 11/13] picoxcell: add support for pc3x2 devices Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 12/13] picoxcell: add support for pc3x3 devices Jamie Iles
2010-11-26 11:14   ` [RFC PATCHv2] " Jamie Iles
2010-11-23 10:06 ` [RFC PATCH 13/13] picoxcell: add support for the PC7302 development board Jamie Iles
2010-11-30 18:10 ` [RFC PATCHv2 10/13] picoxcell: add chained GPIO IRQ handlers Jamie Iles
2010-12-06 10:25 ` ARM: add initial support for Picochip picoXcell SoC Jamie Iles

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=20101208173951.GH2716@pulham.picochip.com \
    --to=jamie@jamieiles.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).