From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 4/6] ARM: tegra: Add clk_tegra structure and helper functions
Date: Mon, 02 Jul 2012 19:31:05 -0600 [thread overview]
Message-ID: <4FF24B59.1060508@wwwdotorg.org> (raw)
In-Reply-To: <CAJOA=zMt-HWKrgQ-pD-wH0s_Nao5sJA13+ESJSBkHQ_3OBurtg@mail.gmail.com>
On 07/02/2012 06:09 PM, Turquette, Mike wrote:
> On Fri, Jun 29, 2012 at 1:34 AM, Prashant Gaikwad <pgaikwad@nvidia•com> wrote:
>> On Thursday 28 June 2012 11:58 PM, Mike Turquette wrote:
>>> We had some discussions in the past on your clock reset and external
>>> line request operations which you've had to put into struct clk_tegra.
>>>
>>> Do you need to expose those ops to code in drivers/*? I consider that a
>>> reasonable litmus test to start considering if something should be moved
>>> into the generic clk.h api.
>>
>>
>> Yes, we need these ops in drivers. Peter has sent a patch proposing to move
>> these ops to generic clk.
>>
>> In addition, we also need mechanism/ops to change rate and parent from
>> clk_ops implementation. There was some discussion but I do not know the
>> latest status.
>>
>
> Hi Prashant,
>
> OK, that is good to know. I haven't forgotten about this topic. I'm
> still trying to think of the best way to expose less-common operations
> to drivers...
>
> Based on Stephen's feedback in patch 0 I'll be waiting for another
> version of this series before taking into clk-next.
Oh, does this series depend on stuff in clk-next? I was intending to
take it through the Tegra tree, since it definitely depends on (in
complex ways through context if nothing else due to to large
split/rename patches) a bunch of commits in Tegra's for-3.6/common-clk
branch.
next prev parent reply other threads:[~2012-07-03 1:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 10:37 [PATCH 0/6] Port Tegra to generic clk framework Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 1/6] ARM: tegra30: Separate out clk ops and clk data Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 2/6] ARM: tegra20: " Prashant Gaikwad
2012-06-28 17:37 ` Stephen Warren
2012-06-29 2:06 ` Prashant G
2012-06-28 10:37 ` [PATCH 3/6] ARM: tegra: Rename tegra20 clock file Prashant Gaikwad
2012-06-28 10:37 ` [PATCH 4/6] ARM: tegra: Add clk_tegra structure and helper functions Prashant Gaikwad
2012-06-28 18:28 ` Mike Turquette
2012-06-29 8:34 ` Prashant Gaikwad
2012-07-03 0:09 ` Turquette, Mike
2012-07-03 1:31 ` Stephen Warren [this message]
2012-07-03 1:49 ` Turquette, Mike
2012-06-28 10:37 ` [PATCH 5/6] ARM: tegra: Port tegra to generic clock framework Prashant Gaikwad
2012-06-28 17:29 ` Prashant G
2012-06-28 10:37 ` [PATCH 6/6] ARM: tegra: Remove duplicate code Prashant Gaikwad
2012-06-28 17:39 ` [PATCH 0/6] Port Tegra to generic clk framework Stephen Warren
2012-06-29 17:24 ` Stephen Warren
2012-07-02 18:12 ` Stephen Warren
2012-07-03 11:29 ` Prashant Gaikwad
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=4FF24B59.1060508@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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