From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/3] media: davinci: vpss: enable vpss clocks
Date: Mon, 8 Apr 2013 17:18:46 +0530 [thread overview]
Message-ID: <5162AE9E.9030404@ti.com> (raw)
In-Reply-To: <CA+V-a8swx0LB0eK0bZwcuFhVCW2UB8Bvm3ebwMQifo=-TB6ASA@mail.gmail.com>
On 4/8/2013 5:08 PM, Prabhakar Lad wrote:
> Sekhar,
>
> On Mon, Apr 8, 2013 at 3:56 PM, Sekhar Nori <nsekhar@ti•com> wrote:
>> On 4/2/2013 5:14 PM, Prabhakar lad wrote:
>>> From: Lad, Prabhakar <prabhakar.csengg@gmail•com>
>>>
>>> By default the VPSS clocks were enabled in capture driver
>>> for davinci family which creates duplicates for dm355/dm365/dm644x.
>>> This patch adds support to enable the VPSS clocks in VPSS driver,
>>> which avoids duplication of code and also adding clock aliases.
>>>
>>> This patch uses PM runtime API to enable/disable instead common clock
>>> framework. con_ids for master and slave clocks of vpss is added in pm_domain
>>
>> Common clock framework in not (yet) used on DaVinci, so this is misleading.
>>
> OK, I'll make it 'This patch uses PM runtime API to enable/disable
> clock, instead
> of Davinci specific clock framework. con_ids for master and slave
may be just call it "DaVinci clock framework"
Thanks,
Sekhar
next prev parent reply other threads:[~2013-04-08 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 11:44 [PATCH v2 0/3] davinci: vpss: clock cleanup Prabhakar lad
2013-04-02 11:44 ` [PATCH v2 1/3] media: davinci: vpss: enable vpss clocks Prabhakar lad
2013-04-08 10:26 ` Sekhar Nori
2013-04-08 11:38 ` Prabhakar Lad
2013-04-08 11:48 ` Sekhar Nori [this message]
2013-04-02 11:44 ` [PATCH v2 2/3] media: davinci: vpbe: venc: move the enabling of vpss clocks to driver Prabhakar lad
2013-04-02 11:44 ` [PATCH v2 3/3] davinic: vpss: trivial cleanup Prabhakar lad
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=5162AE9E.9030404@ti.com \
--to=nsekhar@ti$(echo .)com \
--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