All of lore.kernel.org
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] clk: add DT clock binding support
Date: Mon, 14 May 2012 08:40:01 -0500	[thread overview]
Message-ID: <4FB10B31.7080207@gmail.com> (raw)
In-Reply-To: <20120501225900.GC17311@gmail.com>

On 05/01/2012 05:59 PM, Mike Turquette wrote:
> On 20120409-15:25, Rob Herring wrote:
>> From: Grant Likely <grant.likely@secretlab.ca>
> snip
>> ---
>>  .../devicetree/bindings/clock/clock-bindings.txt   |  117 ++++++++++++++++
>>  .../devicetree/bindings/clock/fixed-clock.txt      |   22 +++
>>  drivers/clk/clk.c                                  |  140 ++++++++++++++++++++
>>  drivers/clk/clkdev.c                               |   77 +++++++++++
>>  include/linux/clk-provider.h                       |   14 ++
>>  include/linux/clk.h                                |   19 +++
>>  6 files changed, 389 insertions(+), 0 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/clock/clock-bindings.txt
>>  create mode 100644 Documentation/devicetree/bindings/clock/fixed-clock.txt
> 
> Hi Rob,
> 
> Patches 1 & 2 are trivial and certainly aimed at clk-next, so I've taken
> them in.  This patch is a bit more difficult as it touches the common
> clk code, clkdev/clk.h and some DT docs.
> 
> Are you looking for me to take this patch into clk-next?  I'm just
> trying to avoid any more clk dependency issues than we already have...
> 

I think that makes the most sense as it appears I'm dependent on
clk-next now. I'm rebasing my patches on clk-next now.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mike Turquette <mturquette-l0cyMroinI0@public.gmane.org>
Cc: Mike Turquette
	<mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/4] clk: add DT clock binding support
Date: Mon, 14 May 2012 08:40:01 -0500	[thread overview]
Message-ID: <4FB10B31.7080207@gmail.com> (raw)
In-Reply-To: <20120501225900.GC17311-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 05/01/2012 05:59 PM, Mike Turquette wrote:
> On 20120409-15:25, Rob Herring wrote:
>> From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
> snip
>> ---
>>  .../devicetree/bindings/clock/clock-bindings.txt   |  117 ++++++++++++++++
>>  .../devicetree/bindings/clock/fixed-clock.txt      |   22 +++
>>  drivers/clk/clk.c                                  |  140 ++++++++++++++++++++
>>  drivers/clk/clkdev.c                               |   77 +++++++++++
>>  include/linux/clk-provider.h                       |   14 ++
>>  include/linux/clk.h                                |   19 +++
>>  6 files changed, 389 insertions(+), 0 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/clock/clock-bindings.txt
>>  create mode 100644 Documentation/devicetree/bindings/clock/fixed-clock.txt
> 
> Hi Rob,
> 
> Patches 1 & 2 are trivial and certainly aimed at clk-next, so I've taken
> them in.  This patch is a bit more difficult as it touches the common
> clk code, clkdev/clk.h and some DT docs.
> 
> Are you looking for me to take this patch into clk-next?  I'm just
> trying to avoid any more clk dependency issues than we already have...
> 

I think that makes the most sense as it appears I'm dependent on
clk-next now. I'm rebasing my patches on clk-next now.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2@gmail.com>
To: Mike Turquette <mturquette@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org,
	Thierry Reding <thierry.reding@avionic-design.de>,
	Mike Turquette <mturquette@linaro.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Grant Likely <grant.likely@secretlab.ca>,
	shawn.guo@linaro.org, Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 3/4] clk: add DT clock binding support
Date: Mon, 14 May 2012 08:40:01 -0500	[thread overview]
Message-ID: <4FB10B31.7080207@gmail.com> (raw)
In-Reply-To: <20120501225900.GC17311@gmail.com>

On 05/01/2012 05:59 PM, Mike Turquette wrote:
> On 20120409-15:25, Rob Herring wrote:
>> From: Grant Likely <grant.likely@secretlab.ca>
> snip
>> ---
>>  .../devicetree/bindings/clock/clock-bindings.txt   |  117 ++++++++++++++++
>>  .../devicetree/bindings/clock/fixed-clock.txt      |   22 +++
>>  drivers/clk/clk.c                                  |  140 ++++++++++++++++++++
>>  drivers/clk/clkdev.c                               |   77 +++++++++++
>>  include/linux/clk-provider.h                       |   14 ++
>>  include/linux/clk.h                                |   19 +++
>>  6 files changed, 389 insertions(+), 0 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/clock/clock-bindings.txt
>>  create mode 100644 Documentation/devicetree/bindings/clock/fixed-clock.txt
> 
> Hi Rob,
> 
> Patches 1 & 2 are trivial and certainly aimed at clk-next, so I've taken
> them in.  This patch is a bit more difficult as it touches the common
> clk code, clkdev/clk.h and some DT docs.
> 
> Are you looking for me to take this patch into clk-next?  I'm just
> trying to avoid any more clk dependency issues than we already have...
> 

I think that makes the most sense as it appears I'm dependent on
clk-next now. I'm rebasing my patches on clk-next now.

Rob


  reply	other threads:[~2012-05-14 13:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 20:24 [PATCH 0/4] DT clock binding support Rob Herring
2012-04-09 20:24 ` Rob Herring
2012-04-09 20:24 ` Rob Herring
2012-04-09 20:24 ` [PATCH 1/4] clk: select CLKDEV_LOOKUP for COMMON_CLK Rob Herring
2012-04-09 20:24   ` Rob Herring
2012-04-09 20:24   ` Rob Herring
2012-04-15  3:18   ` Rob Herring
2012-04-15  3:18     ` Rob Herring
2012-04-17 22:13   ` Turquette, Mike
2012-04-17 22:13     ` Turquette, Mike
2012-04-18  7:07     ` Sascha Hauer
2012-04-18  7:07       ` Sascha Hauer
2012-04-19 14:59       ` Rob Herring
2012-04-19 14:59         ` Rob Herring
2012-04-19 14:59         ` Rob Herring
2012-04-19 20:01         ` Turquette, Mike
2012-04-19 20:01           ` Turquette, Mike
2012-04-09 20:24 ` [PATCH 2/4] clk: remove trailing whitespace from clk.h Rob Herring
2012-04-09 20:24   ` Rob Herring
2012-04-19 20:06   ` Turquette, Mike
2012-04-19 20:06     ` Turquette, Mike
2012-04-09 20:25 ` [PATCH 3/4] clk: add DT clock binding support Rob Herring
2012-04-09 20:25   ` Rob Herring
2012-04-10  2:19   ` Shawn Guo
2012-04-10  2:19     ` Shawn Guo
2012-04-10  2:19     ` Shawn Guo
2012-04-10  4:27   ` Fabio Estevam
2012-04-10  4:27     ` Fabio Estevam
2012-04-10  4:27     ` Fabio Estevam
2012-04-10 12:57     ` Rob Herring
2012-04-10 12:57       ` Rob Herring
2012-05-01 22:59   ` Mike Turquette
2012-05-01 22:59     ` Mike Turquette
2012-05-14 13:40     ` Rob Herring [this message]
2012-05-14 13:40       ` Rob Herring
2012-05-14 13:40       ` Rob Herring
2012-04-09 20:25 ` [PATCH 4/4] clk: add DT fixed-clock " Rob Herring
2012-04-09 20:25   ` 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=4FB10B31.7080207@gmail.com \
    --to=robherring2@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.