From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/6] OMAP4: clocks: Update the clock tree with 4460 clock nodes
Date: Fri, 08 Jul 2011 00:09:12 -0700 [thread overview]
Message-ID: <4E16AD18.7040402@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107080044270.24181@utopia.booyaka.com>
On 7/7/2011 11:49 PM, Paul Walmsley wrote:
> On Sat, 2 Jul 2011, Rajendra Nayak wrote:
>
>> Add the new clock nodes (bandgap_ts_fclk, div_ts_ck) for omap4460.
>> Handle these nodes using the clock flags (CK_*).
>>
>> Signed-off-by: Rajendra Nayak<rnayak@ti.com>
>> Signed-off-by: Nishanth Menon<nm@ti.com>
>> Signed-off-by: Benoit Cousson<b-cousson@ti.com>
>> Reviewed-by: Kevin Hilman<khilman@ti.com>
>
> Is this data coming from autogenerator scripts that have been checked into
> that repository, or have these been hand-edited?
They have been hand edited to create a diff from the 4430 autogen output
and 4460 autogen output.
>
> Also, this isn't the complete set of clock changes needed for full 4460
> support, right? I'm thinking of the duty cycle correction changes
> described in TRM 3.6.3.7.2 "Tactical Clocking Adjustment".
> Are those planned to go into a future patch?
Yes, this series was targeted at providing basic boot support. I was
planning to add the DCC changes as part of the next series.
regards,
Rajendra
>
>
> - Paul
next prev parent reply other threads:[~2011-07-08 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 2:30 [PATCH v2 0/6] OMAP4: Add 4460 base support Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 1/6] OMAP: ID: introduce chip detection for OMAP4460 Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 2/6] OMAP4: ID: add omap_has_feature for max freq supported Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 3/6] OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 4/6] OMAP4: clocks: Update the clock tree with 4460 clock nodes Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 5/6] OMAP4: powerdomain: Reuse on 4460 using CHIP_IS_44XX Rajendra Nayak
2011-07-02 2:30 ` [PATCH v2 6/6] OMAP4: clockdomain: " Rajendra Nayak
2011-07-08 6:51 ` Paul Walmsley
2011-07-08 6:51 ` [PATCH v2 5/6] OMAP4: powerdomain: " Paul Walmsley
2011-07-08 6:49 ` [PATCH v2 4/6] OMAP4: clocks: Update the clock tree with 4460 clock nodes Paul Walmsley
2011-07-08 7:09 ` Rajendra Nayak [this message]
2011-07-08 7:35 ` Paul Walmsley
2011-07-08 10:52 ` Tony Lindgren
2011-07-08 6:30 ` [PATCH v2 3/6] OMAP4: PRCM: OMAP4460 specific PRM and CM register bitshifts Paul Walmsley
2011-07-08 7:01 ` Rajendra Nayak
2011-07-08 7:34 ` Paul Walmsley
2011-07-08 10:51 ` Tony Lindgren
2011-07-08 6:42 ` [PATCH v2 2/6] OMAP4: ID: add omap_has_feature for max freq supported Paul Walmsley
2011-08-04 23:33 ` Menon, Nishanth
2011-07-08 6:39 ` [PATCH v2 1/6] OMAP: ID: introduce chip detection for OMAP4460 Paul Walmsley
2011-07-08 10:49 ` Tony Lindgren
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=4E16AD18.7040402@ti.com \
--to=rnayak@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).