public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org
Subject: Re: [patch-v2.6.34 8/9] arm: omap: musb: do not pass clock name to driver
Date: Wed, 30 Dec 2009 14:23:04 +0300	[thread overview]
Message-ID: <4B3B3818.5030804@ru.mvista.com> (raw)
In-Reply-To: <1262127567-15202-9-git-send-email-felipe.balbi@nokia.com>

Hello.

Felipe Balbi wrote:

> we are using clkdev and the driver can use whatever
> name it wants.
>   

   It's not so actually. This depends on the matching mechanism 
established within clkdev: by device, by name, or by both. Not all 
implementations will match by device, e.g. DA8xx/OMAP-L1x will match by 
clock name.

WBR, Sergei



  reply	other threads:[~2009-12-30 11:23 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
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
     [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
     [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 8/9] arm: omap: musb: do not pass clock name to driver Felipe Balbi
2009-12-30 11:23   ` Sergei Shtylyov [this message]
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=4B3B3818.5030804@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony@atomide.com \
    /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