All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<mturquette@baylibre.com>, <sboyd@codeaurora.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/3] ARM: dts: am43xx: add support for clkout1 clock
Date: Wed, 13 Apr 2016 15:52:19 +0300	[thread overview]
Message-ID: <570E4103.2060301@ti.com> (raw)
In-Reply-To: <20160412210538.GB5995@atomide.com>

On 04/13/2016 12:05 AM, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [160316 12:55]:
>> clkout1 clock node and its generation tree was missing. Add this based
>> on the data on TRM and PRCM functional spec.
>
> Can I pick this one separately?

Yes it has no dependencies towards the other patches.

-Tero

>
> Tony
>

WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
	mturquette@baylibre.com, sboyd@codeaurora.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: dts: am43xx: add support for clkout1 clock
Date: Wed, 13 Apr 2016 15:52:19 +0300	[thread overview]
Message-ID: <570E4103.2060301@ti.com> (raw)
In-Reply-To: <20160412210538.GB5995@atomide.com>

On 04/13/2016 12:05 AM, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [160316 12:55]:
>> clkout1 clock node and its generation tree was missing. Add this based
>> on the data on TRM and PRCM functional spec.
>
> Can I pick this one separately?

Yes it has no dependencies towards the other patches.

-Tero

>
> Tony
>


WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: am43xx: add support for clkout1 clock
Date: Wed, 13 Apr 2016 15:52:19 +0300	[thread overview]
Message-ID: <570E4103.2060301@ti.com> (raw)
In-Reply-To: <20160412210538.GB5995@atomide.com>

On 04/13/2016 12:05 AM, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [160316 12:55]:
>> clkout1 clock node and its generation tree was missing. Add this based
>> on the data on TRM and PRCM functional spec.
>
> Can I pick this one separately?

Yes it has no dependencies towards the other patches.

-Tero

>
> Tony
>

  reply	other threads:[~2016-04-13 12:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 19:54 [PATCH 0/3] ARM: AMx3xx: misc clock fixes Tero Kristo
2016-03-16 19:54 ` Tero Kristo
2016-03-16 19:54 ` Tero Kristo
2016-03-16 19:54 ` [PATCH 1/3] clk: ti: dpll: add support for specifying max rate for DPLLs Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-04-01 19:27   ` Stephen Boyd
2016-04-01 19:27     ` Stephen Boyd
2016-04-16  0:26   ` Stephen Boyd
2016-04-16  0:26     ` Stephen Boyd
2016-03-16 19:54 ` [PATCH 2/3] clk: ti: amx3xx: limit the maximum frequency of DPLLs based on spec Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-04-01 19:28   ` Stephen Boyd
2016-04-01 19:28     ` Stephen Boyd
2016-04-13 12:51     ` Tero Kristo
2016-04-13 12:51       ` Tero Kristo
2016-04-13 12:51       ` Tero Kristo
2016-04-16  0:23       ` Stephen Boyd
2016-04-16  0:23         ` Stephen Boyd
2016-04-16  0:27   ` Stephen Boyd
2016-04-16  0:27     ` Stephen Boyd
2016-03-16 19:54 ` [PATCH 3/3] ARM: dts: am43xx: add support for clkout1 clock Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-03-16 19:54   ` Tero Kristo
2016-04-12 21:05   ` Tony Lindgren
2016-04-12 21:05     ` Tony Lindgren
2016-04-13 12:52     ` Tero Kristo [this message]
2016-04-13 12:52       ` Tero Kristo
2016-04-13 12:52       ` Tero Kristo
2016-04-13 19:07       ` Tony Lindgren
2016-04-13 19:07         ` Tony Lindgren
2016-03-16 22:33 ` [PATCH 0/3] ARM: AMx3xx: misc clock fixes Nishanth Menon
2016-03-16 22:33   ` Nishanth Menon
2016-03-16 22:33   ` Nishanth Menon

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=570E4103.2060301@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=tony@atomide.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 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.