From: linux@arm.linux.org.uk (Russell King - ARM Linux)
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 15:36:02 +0100 [thread overview]
Message-ID: <20100502143602.GA4233@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1272810162-14858-4-git-send-email-saeed@marvell.com>
On Sun, May 02, 2010 at 05:22:40PM +0300, Saeed Bishara wrote:
> @@ -110,6 +111,9 @@ struct usb_hcd {
> u64 rsrc_start; /* memory/io resource start */
> u64 rsrc_len; /* memory/io resource length */
> unsigned power_budget; /* in mA, 0 = no limit */
> +#if defined(CONFIG_HAVE_CLK)
> + struct clk *clk;
> +#endif
We have other hci's using the clk API, why do we need to add this for
them too? In other words, why can't the orion HCI driver work like
the other HCI drivers such as ohci-pxa27x.c or ehci-omap.c ?
next prev parent reply other threads:[~2010-05-02 14:36 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 ` Russell King - ARM Linux [this message]
2010-05-02 15:05 ` [PATCH 3/5] USB: add clk structure for systems that support clkdev framework 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
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=20100502143602.GA4233@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).