public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Gadiyar, Anand" <gadiyar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Query: MUSB clock management code
Date: Tue, 25 Aug 2009 12:05:04 +0300	[thread overview]
Message-ID: <20090825090503.GO25331@nokia.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0309E9CEF2@dbde02.ent.ti.com>

On Mon, Aug 24, 2009 at 01:09:43PM +0200, ext Gadiyar, Anand wrote:
> Hi all,
> 
> Is there a reason to have a wrapper code around the clock
> enable/disable code in arch/arm/mach-omap2/usb-musb.c?
> Is it not okay for the glue-layer code in
> drivers/usb/musb/omap2430.c to do this?

most likely, not anymore, but we needed that as means not to pass clock
name to musb driver. Once all other users of musb move to clkdev, we can
remove that and use plain clk fw calls.

-- 
balbi

      reply	other threads:[~2009-08-25  9:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 11:09 Query: MUSB clock management code Gadiyar, Anand
2009-08-25  9:05 ` Felipe Balbi [this message]

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=20090825090503.GO25331@nokia.com \
    --to=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.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