From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, mturquette@linaro.org,
paul@pwsan.com, nm@ti.com, rnayak@ti.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCHv2 11/11] ARM: OMAP4: register DT clocks and remove old data
Date: Mon, 24 Jun 2013 00:50:16 -0700 [thread overview]
Message-ID: <20130624075015.GR5523@atomide.com> (raw)
In-Reply-To: <51C7F913.7070104@ti.com>
* Tero Kristo <t-kristo@ti.com> [130624 00:51]:
> On 06/21/2013 10:25 AM, Tony Lindgren wrote:
> >* Tero Kristo <t-kristo@ti.com> [130619 06:25]:
> >>Now that the OMAP4 PRCM clock data has been converted to device tree
> >>representation, it is no longer needed as static clock data. OMAP4
> >>clock init routine is also changed to register DT clocks first.
> >>
> >>Signed-off-by: Tero Kristo <t-kristo@ti.com>
> >>---
> >> arch/arm/mach-omap2/cclock44xx_data.c | 1674 +--------------------------------
> >> 1 file changed, 38 insertions(+), 1636 deletions(-)
> >
> >This is nice, thanks for working on this. While at it, can
> >you also keep your eyes open for the register defines in the
> >header files we can also drop?
> >
> >Some of those headers are quite huge.. and should eventually
> >be private to the related drivers if needed at all with DT.
>
> Yeah, I can take a look at this after this set is done. It seems
> like large portion of the headers can be dropped completely once
> this exercise is done.
OK great, thanks.
Tony
prev parent reply other threads:[~2013-06-24 7:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 13:18 [PATCHv2 00/11] ARM: OMAP4 clock data conversion to DT Tero Kristo
2013-06-19 13:18 ` [PATCHv2 01/11] CLK: clkdev: add support for looking up clocks from DT Tero Kristo
2013-06-19 13:18 ` [PATCHv2 02/11] CLK: use of_property_read_u32 instead of read_u8 Tero Kristo
[not found] ` <1371647942-4811-3-git-send-email-t-kristo-l0cyMroinI0@public.gmane.org>
2013-06-21 0:57 ` Mike Turquette
2013-06-21 12:45 ` Nishanth Menon
2013-06-21 16:21 ` Mike Turquette
2013-06-19 13:18 ` [PATCHv2 03/11] CLK: divider: fix table parsing logic for DT Tero Kristo
2013-06-19 13:18 ` [PATCHv2 04/11] clk: omap: introduce clock driver Tero Kristo
2013-06-19 13:18 ` [PATCHv2 05/11] CLK: OMAP4: Add DPLL clock support Tero Kristo
2013-06-19 13:18 ` [PATCHv2 06/11] CLK: omap: move part of the machine specific clock header contents to driver Tero Kristo
2013-06-21 7:32 ` Tony Lindgren
2013-06-24 7:42 ` Tero Kristo
2013-06-19 13:18 ` [PATCHv2 07/11] ARM: OMAP: clock: add DT duplicate clock registration mechanism Tero Kristo
2013-06-19 13:18 ` [PATCHv2 08/11] CLK: omap: add autoidle support Tero Kristo
2013-06-19 13:19 ` [PATCHv2 09/11] CLK: omap: add support for OMAP gate clock Tero Kristo
2013-06-19 13:19 ` [PATCHv2 10/11] ARM: dts: omap4 clock data Tero Kristo
2013-06-19 13:30 ` Nishanth Menon
2013-06-19 13:49 ` Tero Kristo
2013-06-19 13:56 ` Nishanth Menon
2013-06-21 1:24 ` Stephen Boyd
2013-06-24 7:39 ` Tero Kristo
2013-06-19 13:19 ` [PATCHv2 11/11] ARM: OMAP4: register DT clocks and remove old data Tero Kristo
2013-06-21 7:25 ` Tony Lindgren
2013-06-24 7:45 ` Tero Kristo
2013-06-24 7:50 ` Tony Lindgren [this message]
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=20130624075015.GR5523@atomide.com \
--to=tony@atomide.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=t-kristo@ti.com \
/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).