From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: vexpress: Add separate SP810 driver
Date: Mon, 18 Mar 2013 10:54:21 +0000 [thread overview]
Message-ID: <20130318105421.GB29353@arm.com> (raw)
In-Reply-To: <1363358409-5693-1-git-send-email-pawel.moll@arm.com>
On Fri, Mar 15, 2013 at 02:40:09PM +0000, Pawel Moll wrote:
> Factor out the SP810 clocking code into a separate driver,
> selecting better (faster) parent at clk_prepare() time.
> This is to avoid problems with clocking infrastructure
> initialisation order, in particular to avoid dependency
> of fixed clock being initialized before SP810. It also
> makes vexpress platform OF-based clock initialisation code
> unnecessary.
>
> Signed-off-by: Pawel Moll <pawel.moll@arm.com>
> ---
> arch/arm/mach-vexpress/v2m.c | 8 +-
> drivers/clk/versatile/Makefile | 2 +-
> drivers/clk/versatile/clk-sp810.c | 172 ++++++++++++++++++++++++++++++++++
> drivers/clk/versatile/clk-vexpress.c | 49 ----------
> 4 files changed, 180 insertions(+), 51 deletions(-)
> create mode 100644 drivers/clk/versatile/clk-sp810.c
>
> Hi Mike,
>
> I'd like to get this merged in 3.10. After this arm64
> will be able to avoid any platform clocking code. And
> in case of v7 this will happen once Rob's SP804 work
> is done.
FWIW, I'm using this patch on the ARMv8 model (arm64).
Tested-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2013-03-18 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 14:40 [PATCH] clk: vexpress: Add separate SP810 driver Pawel Moll
2013-03-18 10:54 ` Catalin Marinas [this message]
2013-04-10 10:25 ` Pawel Moll
2013-04-15 11:11 ` Pawel Moll
2013-04-17 22:26 ` Mike Turquette
2013-04-18 17:23 ` Pawel Moll
2013-04-18 20:22 ` Mike Turquette
2013-04-22 14:25 ` Russell King - ARM Linux
2013-04-22 14:34 ` Pawel Moll
2013-04-22 17:27 ` Mike Turquette
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=20130318105421.GB29353@arm.com \
--to=catalin.marinas@arm.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.