From: Shawn Guo <shawn.guo@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Mike Turquette <mturquette@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>, <mturquette@linaro.org>,
<s.hauer@pengutronix.de>, <sboyd@codeaurora.org>,
Grant Likely <grant.likely@secretlab.ca>,
<skannan@codeaurora.org>
Subject: Re: [PATCH v3 0/4] DT clock bindings
Date: Thu, 14 Jun 2012 16:49:06 +0800 [thread overview]
Message-ID: <20120614084904.GF31565@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <4FD76CF6.8090801@gmail.com>
On Tue, Jun 12, 2012 at 11:23:18AM -0500, Rob Herring wrote:
> Right. This is why I have reposted and copied those whom commented on my
> pull request. I think at least some of Saravana's concerns boiled down
> to not requiring using DT clock bindings and not requiring driver
> changes to move to DT bindings. Both of these are met with this series.
> A platform can still use clkdev tables for binding clocks to devices and
> does not have to use DT for clocks. Drivers generally should not require
> any changes that I'm aware of, but if there are any concrete examples
> I'd like to know.
>
> Yes, I think this should go thru you.
>
I still have a little doubt about how this binding will best work for
imx clock. I'm trying to cook a RFC patch discussing.
--
Regards,
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Mike Turquette <mturquette@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, mturquette@linaro.org,
s.hauer@pengutronix.de, sboyd@codeaurora.org,
Grant Likely <grant.likely@secretlab.ca>,
skannan@codeaurora.org
Subject: Re: [PATCH v3 0/4] DT clock bindings
Date: Thu, 14 Jun 2012 16:49:06 +0800 [thread overview]
Message-ID: <20120614084904.GF31565@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <4FD76CF6.8090801@gmail.com>
On Tue, Jun 12, 2012 at 11:23:18AM -0500, Rob Herring wrote:
> Right. This is why I have reposted and copied those whom commented on my
> pull request. I think at least some of Saravana's concerns boiled down
> to not requiring using DT clock bindings and not requiring driver
> changes to move to DT bindings. Both of these are met with this series.
> A platform can still use clkdev tables for binding clocks to devices and
> does not have to use DT for clocks. Drivers generally should not require
> any changes that I'm aware of, but if there are any concrete examples
> I'd like to know.
>
> Yes, I think this should go thru you.
>
I still have a little doubt about how this binding will best work for
imx clock. I'm trying to cook a RFC patch discussing.
--
Regards,
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] DT clock bindings
Date: Thu, 14 Jun 2012 16:49:06 +0800 [thread overview]
Message-ID: <20120614084904.GF31565@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <4FD76CF6.8090801@gmail.com>
On Tue, Jun 12, 2012 at 11:23:18AM -0500, Rob Herring wrote:
> Right. This is why I have reposted and copied those whom commented on my
> pull request. I think at least some of Saravana's concerns boiled down
> to not requiring using DT clock bindings and not requiring driver
> changes to move to DT bindings. Both of these are met with this series.
> A platform can still use clkdev tables for binding clocks to devices and
> does not have to use DT for clocks. Drivers generally should not require
> any changes that I'm aware of, but if there are any concrete examples
> I'd like to know.
>
> Yes, I think this should go thru you.
>
I still have a little doubt about how this binding will best work for
imx clock. I'm trying to cook a RFC patch discussing.
--
Regards,
Shawn
next prev parent reply other threads:[~2012-06-14 8:49 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 14:41 [PATCH v3 0/4] DT clock bindings Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 1/4] clk: add DT clock binding support Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-15 3:17 ` Shawn Guo
2012-06-15 3:17 ` Shawn Guo
2012-06-15 3:17 ` Shawn Guo
2012-06-15 4:32 ` Rob Herring
2012-06-15 4:32 ` Rob Herring
2012-07-01 22:13 ` [PATCH v6] " Rob Herring
2012-07-01 22:13 ` Rob Herring
2012-07-01 22:13 ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 2/4] clk: add DT fixed-clock " Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-12 14:41 ` [PATCH v3 3/4] dt: add clock binding doc to primecell bindings Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-22 13:55 ` Ben Dooks
2012-06-22 14:23 ` Russell King - ARM Linux
2012-06-12 14:41 ` [PATCH v3 4/4] clk: add highbank clock support Rob Herring
2012-06-12 14:41 ` Rob Herring
2012-06-12 15:47 ` [PATCH v3 0/4] DT clock bindings Mike Turquette
2012-06-12 15:47 ` Mike Turquette
2012-06-12 16:23 ` Rob Herring
2012-06-12 16:23 ` Rob Herring
2012-06-14 8:49 ` Shawn Guo [this message]
2012-06-14 8:49 ` Shawn Guo
2012-06-14 8:49 ` Shawn Guo
2012-06-13 15:26 ` Peter De Schrijver
2012-06-13 15:26 ` Peter De Schrijver
2012-06-13 15:26 ` Peter De Schrijver
2012-06-13 18:09 ` Rob Herring
2012-06-13 18:09 ` Rob Herring
2012-06-13 18:09 ` Rob Herring
2012-06-15 8:39 ` Shawn Guo
2012-06-15 8:39 ` Shawn Guo
2012-06-15 8:39 ` Shawn Guo
2012-06-15 15:40 ` Stephen Warren
2012-06-15 15:40 ` Stephen Warren
2012-06-15 21:07 ` Rob Herring
2012-06-15 21:07 ` Rob Herring
2012-06-15 21:07 ` Rob Herring
2012-06-21 7:27 ` Chris Ball
2012-06-21 7:27 ` Chris Ball
2012-06-21 7:30 ` [PATCH 01/02] clk: Refactor of_clk_* into a new clk-of.c Chris Ball
2012-06-21 7:30 ` Chris Ball
2012-06-21 7:32 ` [PATCH 02/02] clk: clk-of: Use alloc_bootmem() instead of kzalloc() Chris Ball
2012-06-21 7:32 ` Chris Ball
2012-06-21 12:18 ` Paul Mundt
2012-06-21 12:18 ` Paul Mundt
2012-06-21 15:00 ` [PATCH v3 0/4] DT clock bindings Rob Herring
2012-06-21 15:00 ` Rob Herring
2012-06-21 17:54 ` Mike Turquette
2012-06-21 17:54 ` Mike Turquette
2012-06-27 12:54 ` Rob Herring
2012-06-27 12:54 ` Rob Herring
2012-07-03 1:30 ` Turquette, Mike
2012-07-03 1:30 ` Turquette, Mike
2012-07-03 2:37 ` Rob Herring
2012-07-03 2:37 ` Rob Herring
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=20120614084904.GF31565@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=mturquette@ti.com \
--cc=robherring2@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@codeaurora.org \
--cc=skannan@codeaurora.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.