From: saeed.bishara@gmail.com (saeed bishara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] USB: add clk structure for systems that support clkdev framework
Date: Sun, 2 May 2010 18:54:15 +0300 [thread overview]
Message-ID: <i2ic70ff3ad1005020854l2738ace8l3c7c291cf07c9402@mail.gmail.com> (raw)
In-Reply-To: <20100502153157.GD4233@n2100.arm.linux.org.uk>
>> well, I think that those drivers that have more than one clk can be
>> redesigned by adding virtual clk for the the usb host, and the clk
>> implementation for that soc should manage all the underlying physical
>> clocks. I've looked at the omap,at91 and atmel, and it looks to me
>> that this is doable. you see can see that the clk stuff in those
>> driver has nothing to do with usb itself. what do you think?
>
> Not happy with this for two reasons:
> 1. You're assuming that they can be managed as one entity; that doesn't seem
> ? true for some of the drivers.
can you please give an example?
saeed
next prev parent reply other threads:[~2010-05-02 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 14:22 [PATCH 0/5] USB: orion ehci patches for 2.6.35 Saeed Bishara
2010-05-02 14:22 ` [PATCH 1/5] USB: add support for phy init for the Dove SoC Saeed Bishara
2010-05-02 14:22 ` [PATCH 2/5] ARM: use the Dove USB phy setup Saeed Bishara
2010-05-02 14:22 ` [PATCH 3/5] USB: add clk structure for systems that support clkdev framework Saeed Bishara
2010-05-02 14:22 ` [PATCH 4/5] USB: manage the orion ehci clock using the clkdev Saeed Bishara
2010-05-02 14:22 ` [PATCH 5/5] USB: add power management support for orion ehci Saeed Bishara
2010-05-02 14:36 ` [PATCH 3/5] USB: add clk structure for systems that support clkdev framework Russell King - ARM Linux
2010-05-02 15:05 ` saeed bishara
2010-05-02 15:14 ` Russell King - ARM Linux
2010-05-02 15:21 ` saeed bishara
2010-05-02 15:31 ` Russell King - ARM Linux
2010-05-02 15:54 ` saeed bishara [this message]
2010-05-02 16:05 ` Russell King - ARM Linux
2010-05-25 7:08 ` saeed bishara
2010-06-06 10:28 ` saeed bishara
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=i2ic70ff3ad1005020854l2738ace8l3c7c291cf07c9402@mail.gmail.com \
--to=saeed.bishara@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).