public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/7] OMAP3+: Clock: Adding ehci clock enabling
Date: Mon, 06 Feb 2012 14:17:13 +0200	[thread overview]
Message-ID: <4F2FC4C9.9010209@compulab.co.il> (raw)
In-Reply-To: <CAAL8m4zS9GLszbteAiVrWyRQP0JwvG2qHZM-NFcMcgzZvENdjA@mail.gmail.com>

On 02/06/12 13:57, Govindraj wrote:
> On Mon, Feb 6, 2012 at 5:12 PM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> On 02/03/12 15:38, Govindraj.R wrote:
>>> From: "Govindraj.R" <govindraj.raja@ti.com>
>>>
>>> Adding ehci clock enabling mechanism part of clock framework.
>>> When essential clocks are enabled during init phase usb host
>>> clocks can also be enabled from clock framework.
>>>
>>> Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
>>
>> Acked-by: Igor Grinberg <grinberg@compulab.co.il>
>>
>>> ---
>>>  arch/arm/cpu/armv7/omap3/board.c            |    4 ++++
>>>  arch/arm/cpu/armv7/omap3/clock.c            |   20 ++++++++++++++++++++
>>>  arch/arm/cpu/armv7/omap4/clocks.c           |    5 +++++
>>>  arch/arm/include/asm/arch-omap3/sys_proto.h |    1 +
>>>  4 files changed, 30 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/arch/arm/cpu/armv7/omap3/board.c b/arch/arm/cpu/armv7/omap3/board.c
>>> index 871aa37..054e9c4 100644
>>> --- a/arch/arm/cpu/armv7/omap3/board.c
>>> +++ b/arch/arm/cpu/armv7/omap3/board.c
>>> @@ -228,6 +228,10 @@ void s_init(void)
>>>
>>>       per_clocks_enable();
>>>
>>> +#ifdef CONFIG_USB_EHCI_OMAP
>>> +     ehci_clocks_enable();
>>> +#endif
>>
>> Just a question (not blocking):
>> I would really like to see this being a part of "usb start" call some day...
>> Can't this be called from omap_ehci_hcd_init()?
> 
> But its better to have it part of clock framework.
> 
> on omap4 I have added this part of enabling essential
> clocks done part of clock framework.
> 
> "arch/arm/cpu/armv7/omap[4/5]/clocks.c" =>
> "arch/arm/cpu/armv7/omap-common/clocks-common.c"
> 
> but on omap3 we don't seem to use clocks common.
> so I have just used this function.
> 
> on omap4/5 clocks.c makes things simpler for us.
> (re-use the same rather to complicate with our funcs)

Yes, I understand, it is indeed simpler.
I'm trying also to see this from the final product POV,
where things like power consumption and supermarket principle
(pay only for what you buy) can meter.
Again, this is fine (I already acked the patch), just wanted to know
how difficult would it be to get it fine tuned for "usb start/stop".

Thanks


-- 
Regards,
Igor.

  reply	other threads:[~2012-02-06 12:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 13:38 [U-Boot] [PATCH v3 0/7] Clean up ehci-omap and extend support for omap3/4 socs Govindraj.R
2012-02-03 13:38 ` [U-Boot] [PATCH v3 1/7] ehci-omap: driver for EHCI host on OMAP3 Govindraj.R
2012-02-03 13:38 ` [U-Boot] [PATCH v3 2/7] ehci-omap: Clean up added ehci-omap.c Govindraj.R
2012-02-06 11:26   ` Igor Grinberg
2012-02-03 13:38 ` [U-Boot] [PATCH v3 3/7] OMAP3+: Clock: Adding ehci clock enabling Govindraj.R
2012-02-06 11:42   ` Igor Grinberg
2012-02-06 11:57     ` Govindraj
2012-02-06 12:17       ` Igor Grinberg [this message]
2012-02-03 13:38 ` [U-Boot] [PATCH v3 4/7] OMAP4: clock-common: Move the usb dppl configuration to new func Govindraj.R
2012-02-03 13:38 ` [U-Boot] [PATCH v3 5/7] OMAP3+: ehci-omap: enable usb host ports for beagle/panda Govindraj.R
2012-02-06 12:03   ` Igor Grinberg
2012-02-03 13:38 ` [U-Boot] [PATCH v3 6/7] usb: ulpi: Extend the existing ulpi framework Govindraj.R
2012-02-06  8:55   ` Igor Grinberg
2012-02-06  9:38     ` Govindraj
2012-02-06 10:03       ` Igor Grinberg
2012-02-08 17:42   ` SUBHASHINI MANNE
2012-02-09  6:32     ` Govindraj
2012-02-03 13:38 ` [U-Boot] [PATCH v3 7/7] usb: ulpi: Add omap-ulpi-view port support Govindraj.R
2012-02-06  9:10   ` Igor Grinberg
2012-02-03 15:25 ` [U-Boot] [PATCH v3 0/7] Clean up ehci-omap and extend support for omap3/4 socs Tom Rini

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=4F2FC4C9.9010209@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=u-boot@lists.denx.de \
    /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