All of lore.kernel.org
 help / color / mirror / Atom feed
From: paulius.zaleckas@gmail.com (Paulius Zaleckas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Common struct clk implementation, v7
Date: Wed, 15 Sep 2010 11:15:55 +0300	[thread overview]
Message-ID: <4C9080BB.3090703@gmail.com> (raw)
In-Reply-To: <1284522014.516876.675872472687.0.gpush@pororo>

On 09/15/2010 06:40 AM, Jeremy Kerr wrote:
> Hi all,
>
> These patches are an attempt to allow platforms to share clock code. At
> present, the definitions of 'struct clk' are local to platform code,
> which makes allocating and initialising cross-platform clock sources
> difficult, and makes it impossible to compile a single image containing
> support for two ARM platforms with different struct clks.
>
> The two patches are for the architecture-independent kernel code,
> introducing the common clk infrastructure. The changelog for the first
> patch includes details about the new clock definitions.
>
> As requested by rmk, I've put together a small series of patches
> illustrating the usage of the common struct clock on the ARM imx51
> platform. These are available in my git tree:
>
>   git://kernel.ubuntu.com/jk/dt/linux-2.6
>
> in the clk-common-mx51 branch (clk-common..clk-common-mx51). There is
> also a port  for versatile (clk-common-versatile) in this tree too.
>
> The approach I've taken with the imx51 port is to temporarly duplicate
> the platform-common clock code (ie, for all mxc-based boards) to enable
> usage of the common struct clk on one machine (imx51), while leaving the
> others as-is. For a proper platform-wide usage of the common struct clk,
> we'd be better off doing the whole platform at once. However, mx51 is
> the only mxc-based HW I have, hence the duplicated example port.
>
> In the example port, the first change simply converts the mxc's struct
> clk to a struct clk_mxc, using the new API.  The subsequent patches move
> certain clocks to more specific data structures (eg clk_fixed and
> clk_pll) where possible.
>
> Ben Herrenschmidt is looking at using common struct clk code for powerpc
> too, hence the kernel-wide approach.
>
> Many thanks to the following for their input:
>   * Ben Dooks<ben-linux@fluff.org>
>   * Baruch Siach<baruch@tkos.co.il>
>   * Russell King<linux@arm.linux.org.uk>
>   * Uwe Kleine-K?nig<u.kleine-koenig@pengutronix.de>
>   * Lorenzo Pieralisi<Lorenzo.Pieralisi@arm.com>

Funny enough, this morning on my way to work I was thinking exactly
about the same issue! I was very surprised to discover that you just
did it :)

Acked-by: Paulius Zaleckas <paulius.zaleckas@gmail.com>

  parent reply	other threads:[~2010-09-15  8:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15  3:40 [PATCH 0/3] Common struct clk implementation, v7 Jeremy Kerr
2010-09-15  3:40 ` [PATCH 1/3] Add a common struct clk Jeremy Kerr
2010-09-16 13:09   ` Jassi Brar
2010-09-17  0:24     ` Jeremy Kerr
2010-09-17  0:55       ` Jassi Brar
2010-09-17  2:16         ` Jassi Brar
2010-11-27 15:56   ` Jassi Brar
2010-11-29  7:59     ` Jeremy Kerr
2010-12-07 14:31       ` Uwe Kleine-König
2010-12-08  1:02         ` Jeremy Kerr
2010-12-08  8:45           ` Uwe Kleine-König
2010-12-08 16:48           ` Ben Dooks
2010-12-09  2:16             ` Jeremy Kerr
2010-12-10 15:09               ` Richard Zhao
2010-12-11  2:21                 ` Jassi Brar
2010-09-15  3:40 ` [PATCH 3/3] arm/clkdev: Allow common struct clk usage Jeremy Kerr
2010-09-15  3:40 ` [PATCH 2/3] clk: Generic support for fixed-rate clocks Jeremy Kerr
2010-09-15  5:53 ` [PATCH 0/3] Common struct clk implementation, v7 Jean-Christophe PLAGNIOL-VILLARD
2010-09-15  5:53   ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-15  6:08   ` Jeremy Kerr
2010-09-15  6:08     ` Jeremy Kerr
2010-09-16  1:51     ` Paul Mundt
2010-09-16  1:51       ` Paul Mundt
2010-09-15  8:15 ` Paulius Zaleckas [this message]
2010-09-15 23:15 ` Colin Cross
2010-09-15 23:15   ` Colin Cross
2010-09-16  8:19   ` Jeremy Kerr
2010-09-16  8:19     ` Jeremy Kerr
2010-09-26 23:57   ` Ben Dooks
2010-09-26 23:57     ` Ben Dooks

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=4C9080BB.3090703@gmail.com \
    --to=paulius.zaleckas@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.