From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB
Date: Mon, 23 Feb 2009 14:30:40 +0200 [thread overview]
Message-ID: <49A296F0.4000509@gmail.com> (raw)
In-Reply-To: <6ed0b2680902230413o33f98059q7239cbba0114c2b3@mail.gmail.com>
Grazvydas Ignotas said the following on 02/23/2009 02:13 PM:
>>>> +#ifdef CONFIG_MUSB
>>>> + /* Enable the MUSB interface clock */
>>>> + sr32(&prcm_base->iclken1_core, 4, 1, 0x1);
>>>> +#endif
>>>>
>>> the design of u-boot is to enagle the IP only when he use it
>>> so please do not enable the clock every time just when you want to use
>>> (in the USB driver init)
>>>
>> This is already answered in
>>
>> http://lists.denx.de/pipermail/u-boot/2009-February/047452.html
>>
>
> He probably wants to say that clocks should be enabled only when "usb
> start" is issued, as you might have u-boot compiled with USB defines
> set, but never actually use USB.
>
Comparing having all clock initialization at a central point (clock.c) -
which seems simple vs having get-put kind of clock apis in U-boot : I
might go for the simple solution of all clocks in a single place..
u-boot is supposed to "keep it simple", enable/disable clocks on a need
basis is elegant, though could end up getting extended to i2c and other
peripherals too(if I were to stretch is pretty hard ;) ).. makes more
sense in kernel(which is already there) than here - my 2 cents..
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-02-23 12:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 18:55 [U-Boot] [PATCH 0/7 v2] OMAP3: Add some additional improvements and fixes Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 1/7 v2] OMAP3: Overo: Clean up pin mux and GPIO configuration Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 2/7 v2] OMAP3: Beagle: Add board revision detection Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 3/7 v2] OMAP3: Add OMAP3 auto detection Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 4/7 v2] OMAP3: Pandora: Update pin mux Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 5/7 v2] OMAP3: Add serial number based on die ID Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Dirk Behme
2009-02-12 18:55 ` [U-Boot] [PATCH 7/7 v2] OMAP3: Clean up MMC code Dirk Behme
2009-02-22 15:59 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Jean-Christophe PLAGNIOL-VILLARD
2009-02-22 16:22 ` Dirk Behme
2009-02-23 12:13 ` Grazvydas Ignotas
2009-02-23 12:30 ` Nishanth Menon [this message]
2009-02-23 19:31 ` Dirk Behme
2009-02-23 21:36 ` Wolfgang Denk
2009-02-23 23:03 ` [U-Boot] Clock handling (wasRe: [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB) Nishanth Menon
2009-02-24 17:01 ` Dirk Behme
2009-02-24 17:01 ` [U-Boot] [PATCH 6/7 v2] OMAP3: Add OMAP3 core changes for MUSB Dirk Behme
2009-02-24 21:22 ` Wolfgang Denk
2009-02-25 17:39 ` Dirk Behme
2009-03-01 14:26 ` Dirk Behme
2009-03-01 19:18 ` Wolfgang Denk
2009-03-11 14:46 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-11 18:25 ` Dirk Behme
2009-03-11 18:44 ` Wolfgang Denk
2009-02-22 16:01 ` [U-Boot] [PATCH 5/7 v2] OMAP3: Add serial number based on die ID Jean-Christophe PLAGNIOL-VILLARD
2009-02-22 16:40 ` Dirk Behme
2009-02-22 21:44 ` Wolfgang Denk
2009-03-01 14:20 ` Dirk Behme
2009-03-01 18:57 ` Wolfgang Denk
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=49A296F0.4000509@gmail.com \
--to=menon.nishanth@gmail.com \
--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