From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ranjith Lohithakshan <ranjithl@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] AM35xx: Clock table updates for AM3505/17
Date: Wed, 11 Nov 2009 13:43:04 -0800 [thread overview]
Message-ID: <87iqdg20wn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1257417540-21120-1-git-send-email-ranjithl@ti.com> (Ranjith Lohithakshan's message of "Thu\, 5 Nov 2009 16\:09\:00 +0530")
Ranjith Lohithakshan <ranjithl@ti.com> writes:
> AM3505/17 though a OMAP3530 derivative have the following
> main differences
>
> - Removal of the following OMAP3 modules
> - IVA
> - ISP/CAM
> - Modem and D2D components (MAD2D, SAD2D)
> - USIM
> - SSI
> - Mailboxes
> - USB OTG
> - ICR
> - MSPRO
> - SmartReflex
> - SDRC replaced with EMIF4 Controller in the SDRC subsystem
> thus adding support for DDR2 memory devices
> - Addition of the following new modules
> - Ethernet MAC (CPGMAC)
> - CAN Controller (HECC)
> - New USB OTG Controller with integrated Phy
> - Video Processing Front End (VPFE)
> - Additional UART (UART4)
> - All security accelerators disabled on GP devices and not to
> be accessed or configured
>
> This patch defines CPU flags for AM3505/17 and update the clock table.
> Clock support for new modules will be added by subsequent patches.
>
> Signed-off-by: Ranjith Lohithakshan <ranjithl@ti.com>
A question on the approach here, as I'm wondering if this approach is
really needed.
Rather than handling these details in the clock tree, why not handle
the special cases using the feature checks: omap_has_*().
Kevin
next prev parent reply other threads:[~2009-11-11 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 10:39 [PATCH] AM35xx: Clock table updates for AM3505/17 Ranjith Lohithakshan
2009-11-05 16:24 ` Menon, Nishanth
2009-11-05 16:26 ` Gadiyar, Anand
2009-11-06 11:19 ` Lohithakshan, Ranjith
2009-11-06 9:22 ` Lohithakshan, Ranjith
2009-11-12 12:08 ` Paul Walmsley
2009-11-11 21:43 ` Kevin Hilman [this message]
2009-11-12 5:06 ` Lohithakshan, Ranjith
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=87iqdg20wn.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=ranjithl@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