From: Sekhar Nori <nsekhar@ti.com>
To: Philip Avinash <avinashphilip@ti.com>
Cc: <linux@arm.linux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<prakash.pm@ti.com>
Subject: Re: [PATCH 2/3] ARM: davinci: da850: Enable EHRPWM TBCLK from CFG_CHIP1
Date: Thu, 14 Mar 2013 18:31:52 +0530 [thread overview]
Message-ID: <5141CA40.9010005@ti.com> (raw)
In-Reply-To: <1363257453-24747-3-git-send-email-avinashphilip@ti.com>
On 3/14/2013 4:07 PM, Philip Avinash wrote:
> da850 platforms require TBCLK synchronization in CFG_CHIP1 register for
> TBCLK enable in EHRPWM modules. Enabling of TBCLK is done only if EHRPWM
> DT node status is set to "okay" DT blob.
> Also adds macro definitions for DA8XX_EHRPWM_TBCLKSYNC and
> DA8XX_CFGCHIP1_REG.
So there is actually a TBCLK in DA850 - it's just not modeled as a clock
similar to the way it is done on AM335x? If yes, then instead of adding
a dummy clock node and doing the TBCLK enable as part of init, why not
model TBCLK in clock tree even on DA850?
Thanks,
Sekhar
next prev parent reply other threads:[~2013-03-14 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:37 [PATCH 0/3] Platform support for EHRPWM & ECAP devices in Davinci Philip Avinash
2013-03-14 10:37 ` [PATCH 1/3] arm: davinci: clock node support for ECAP & EHRPWM Philip Avinash
2013-03-14 12:36 ` Sekhar Nori
2013-03-14 10:37 ` [PATCH 2/3] ARM: davinci: da850: Enable EHRPWM TBCLK from CFG_CHIP1 Philip Avinash
2013-03-14 13:01 ` Sekhar Nori [this message]
2013-03-15 4:57 ` Philip, Avinash
2013-03-15 5:08 ` Sekhar Nori
2013-03-15 5:21 ` Philip, Avinash
2013-03-15 5:43 ` Sekhar Nori
2013-03-14 10:37 ` [PATCH 3/3] ARM: davinci: da850: add EHRPWM & ECAP DT node Philip Avinash
2013-03-14 15:49 ` Peter Korsgaard
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=5141CA40.9010005@ti.com \
--to=nsekhar@ti.com \
--cc=avinashphilip@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=prakash.pm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox