From: Ranjith Lohithakshan <ranjithl@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/2] AM35xx: Clock table updates for AM3505/17
Date: Tue, 15 Dec 2009 17:22:06 +0530 [thread overview]
Message-ID: <4B277866.1070602@ti.com> (raw)
In-Reply-To: <20091214201638.370.60113.stgit@localhost.localdomain>
Hi Paul,
Two small changes wrt USB that came up when I reviewed the AM35XX
clock tree again.
On Tue, 15-Dec-09 1:46 AM +0530, Paul Walmsley wrote:
> From: Ranjith Lohithakshan <ranjithl@ti.com>
>
> AM3505/17 though a OMAP3530 derivative have the following
> main differences
...
> CLK("musb_hdrc", "ick", &hsotgusb_ick_3430es1, CK_3430ES1),
> - CLK("musb_hdrc", "ick", &hsotgusb_ick_3430es2, CK_3430ES2),
> - CLK(NULL, "sdrc_ick", &sdrc_ick, CK_343X),
> - CLK(NULL, "gpmc_fck", &gpmc_fck, CK_343X),
> + CLK("musb_hdrc", "ick", &hsotgusb_ick_3430es2, CK_3430ES2 | CK_AM35XX),
This musb clock is NOT used on AM35XX. I might have included it in
my original patch by mistake.
...
> - CLK(NULL, "usbhost_120m_fck", &usbhost_120m_fck, CK_3430ES2),
> + CLK(NULL, "usbhost_120m_fck", &usbhost_120m_fck, CK_3430ES2 | CK_AM35XX),
> CLK(NULL, "usbhost_48m_fck", &usbhost_48m_fck, CK_3430ES2),
The 48 MHz USB Host fclk is used and applicable on AM35XX as well.
Do you want me to issue another patch for these two changes or could
you update it when you commit? Please let me know.
- Ranjith
next prev parent reply other threads:[~2009-12-15 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 20:16 [PATCH 0/2] OMAP clock: new platform prep + AM35xx clock definitions Paul Walmsley
2009-12-14 20:16 ` [PATCH 1/2] OMAP3 clock: reorganize CK_* platform flags Paul Walmsley
2009-12-14 20:16 ` [PATCH 2/2] AM35xx: Clock table updates for AM3505/17 Paul Walmsley
2009-12-15 11:52 ` Ranjith Lohithakshan [this message]
2009-12-15 20:02 ` Paul Walmsley
2009-12-21 6:01 ` Sripathy, Vishwanath
2009-12-21 6:39 ` Ranjith Lohithakshan
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=4B277866.1070602@ti.com \
--to=ranjithl@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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