From: Sergei Shtylyov <sshtylyov-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
To: me-uiRdBs8odbtmTBlB0Cgj/Q@public.gmane.org
Cc: Felipe Balbi
<felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch-v2.6.34 7/9] usb: musb: use only clk framework for clk handling
Date: Wed, 30 Dec 2009 16:06:19 +0300 [thread overview]
Message-ID: <4B3B504B.4020602@ru.mvista.com> (raw)
In-Reply-To: <1262174012.28789.178.camel@gandalf>
Hello.
Felipe Balbi wrote:
>> Why always "ick"?! Do you think OMAPs are the only boards using MUSB
>> out there?
>>
>
> err, I'm afraid you have to read more about clock framework. The clock
> name should not matter when you issue clk_get().
It depends on the matching type determined from a clkdev matching
table -- see dm644x_clks[] in arch/mach-davinci/dm644x.c as an example:
'struct davinci_clk' incorporates 'struct clk_lookup', and where its 1st
member is initialized, the matching is done by device, where its second
member is initialized, the matching is done by clock name -- see
clk_find() in arch/arm/common/clkdev.c for the logic.
> I used the shortest
> name that came to my mind. could've been "usb", "usb_clock",
> "musb_otg_default_clock". It doesn't matter.
I know for sure that it still *can* matter with clkdev, and I do use
matching by clock name with DA8xx/OMAP-L1x glue layer. So I' strongly
against this patch.
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-30 13:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 22:59 [patch-v2.6.34 0/9] arm omap patches for -next merge window Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 2/9] arm: omap: musb: we can use clk framework Felipe Balbi
[not found] ` <1262127567-15202-1-git-send-email-felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2009-12-29 22:59 ` [patch-v2.6.34 1/9] arm: omap: musb: remove unused data Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 3/9] arm: omap: musb: remove unused soft_con field Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 5/9] arm: omap: musb: remove unnecessary return Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 7/9] usb: musb: use only clk framework for clk handling Felipe Balbi
[not found] ` <1262127567-15202-8-git-send-email-felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2009-12-30 11:18 ` Sergei Shtylyov
[not found] ` <4B3B3720.9070205-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-12-30 11:53 ` Felipe Balbi
2009-12-30 13:06 ` Sergei Shtylyov [this message]
[not found] ` <4B3B504B.4020602-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-12-30 13:14 ` Felipe Balbi
2009-12-30 13:20 ` Felipe Balbi
2009-12-30 13:25 ` Sergei Shtylyov
[not found] ` <4B3B54E1.9010600-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-12-30 13:29 ` Felipe Balbi
2009-12-30 13:43 ` Sergei Shtylyov
[not found] ` <4B3B58F0.2070903-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-12-30 13:46 ` Felipe Balbi
2009-12-30 14:45 ` Sergei Shtylyov
2009-12-29 22:59 ` [patch-v2.6.34 4/9] arm: omap: musb: remove unused dma data Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 6/9] arm: omap: gpmc: avoid section definitions on headers Felipe Balbi
2009-12-29 22:59 ` [patch-v2.6.34 8/9] arm: omap: musb: do not pass clock name to driver Felipe Balbi
2009-12-30 11:23 ` Sergei Shtylyov
2009-12-30 11:55 ` Felipe Balbi
2009-12-30 13:10 ` Sergei Shtylyov
2009-12-29 22:59 ` [patch-v2.6.34 9/9] arm: omap: musb: get rid of dyn_fifo Felipe Balbi
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=4B3B504B.4020602@ru.mvista.com \
--to=sshtylyov-hkdhdckh98+b+jhodadfcq@public.gmane.org \
--cc=felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=me-uiRdBs8odbtmTBlB0Cgj/Q@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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