linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3 v2] clk: keystone: Add common clock drivers
Date: Wed, 25 Sep 2013 13:51:59 -0400	[thread overview]
Message-ID: <524322BF.5000407@ti.com> (raw)
In-Reply-To: <CAPtuhTg1z29+L8jjY4+putq6_-yX4G12UgMm7K3PnD4q5KZVjA@mail.gmail.com>

On Wednesday 25 September 2013 01:50 PM, Mike Turquette wrote:
> On Wed, Sep 25, 2013 at 9:13 AM, Santosh Shilimkar
> <santosh.shilimkar@ti.com> wrote:
>> Mike,
>>
>> On Thursday 29 August 2013 03:14 PM, Santosh Shilimkar wrote:
>>> v2:
>>> - Aligned the bindings as per the list discussion. Removed the additional
>>>       parameters by usage of reg-names and additional compatible fields.
>>> - Addressed all the comments from v1 on drivers.
>>> - Split the series into clock drivers($subject series) and
>>>       platform, dt updates. Will post that one separately.
>>>
>>> Special thanks to Mike and Mark for the detailed review on v1.
>>>
>>> Series is an attempt to add the clock drivers for Keystone SOCs
>>> based on common clock framework. A PLL drivers taking care of
>>> SOC PLLs and a gate control driver taking clock management for
>>> the IPs. The current Keystone based SOCs don' support dynamic power
>>> management usecases like DVFS, SOC ilde etc and hence most of the
>>> usage is limited to enabling clocks and finding the current clock
>>> rate etc.
>>>
>>> Based on to of Mike's dt binding series [1] and tested on Keystone2
>>> EVM.
>>>
>>> Cc: Mike Turquette <mturquette@linaro.org>
>>
>> As aligned off-list, I will revise the series to remove the
>> dependency with your DT bindings series which still seems to
>> be under discussion.
> 
> ACK. I plan to refresh my DT bindings and make them more concise, but
> I still think it is wise if you do not rely on them. As we discussed
> you can switch over to those bindings at any point in the future if
> you wish.
> 
Sounds good.

Regards,
Santosh

      reply	other threads:[~2013-09-25 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 19:14 [PATCH 0/3 v2] clk: keystone: Add common clock drivers Santosh Shilimkar
2013-08-29 19:14 ` [PATCH 1/3 v2] clk: keystone: add Keystone PLL clock driver Santosh Shilimkar
2013-08-29 19:14 ` [PATCH 2/3 v2] clk: keystone: Add gate control " Santosh Shilimkar
2013-08-29 19:14 ` [PATCH 3/3 v2] clk: keystone: Build Keystone clock drivers Santosh Shilimkar
2013-09-25 16:13 ` [PATCH 0/3 v2] clk: keystone: Add common " Santosh Shilimkar
2013-09-25 17:50   ` Mike Turquette
2013-09-25 17:51     ` Santosh Shilimkar [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=524322BF.5000407@ti.com \
    --to=santosh.shilimkar@ti.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 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).