From: Paul Walmsley <paul@pwsan.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, b-cousson@ti.com
Cc: balbi@ti.com, tony@atomide.com, linux@arm.linux.org.uk,
arnd@arndb.de, gregkh@linuxfoundation.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm: omap: hwmod: make *phy_48m* as the main_clk of ocp2scp
Date: Tue, 11 Sep 2012 22:28:22 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.00.1209112218440.9444@utopia.booyaka.com> (raw)
In-Reply-To: <1347008955-21310-1-git-send-email-kishon@ti.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1436 bytes --]
Hi Kishon, Benoît,
On Fri, 7 Sep 2012, Kishon Vijay Abraham I wrote:
> Made *ocp2scp_usb_phy_phy_48m* as the main_clk for ocp2scp. Since this
> ocp2scp module does not have any fck but does have a single opt_clock,
> it is added as the main_clk for ocp2scp. Also removed phy_48m as the
> optional clock since it is now made as the main clock. By this the
> driver need not enable/disable phy_48m clk separately and
> runtime_get/runtime_put will take care of that.
Looking at this patch, it doesn't seem to make sense from a hardware point
of view. If you look at the OMAP4430 TRM Rev. AE, Table 23-1166 "Clocks
and Resets", the 48MHz clock input is listed as an "Optional functional
clock". The main functional clock is listed as "INIT_960M_FCLK", which
according to the same TRM, Section 3.6.3.9.1 "Overview", is an alias for
the clock we call "dpll_usb_clkdcoldo_ck".
So if any clock should be the main functional clock in the hwmod data,
shouldn't it be dpll_usb_clkdcoldo_ck? The goal with the hwmod data
is/was to have it match the hardware.
...
More to the point, I guess I don't see what the problem is with
adding a few lines to the ocp2scp driver to control the "phy_48m" optional
clock via the clock framework. Is there some reason why you
couldn't prepare & enable it after the pm_runtime_get_*(),
and disable and unprepare it before the pm_runtime_put_*() ?
- Paul
next prev parent reply other threads:[~2012-09-11 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 9:09 Kishon Vijay Abraham I
2012-09-11 22:28 ` Paul Walmsley [this message]
2012-09-12 6:36 ` ABRAHAM, KISHON VIJAY
2012-09-13 16:16 ` Benoit Cousson
2012-09-13 17:10 ` Paul Walmsley
2012-09-13 19:53 ` Paul Walmsley
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=alpine.DEB.2.00.1209112218440.9444@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®