public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Ajay Kumar Gupta <ajay.gupta@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	felipe.balbi@nokia.com
Subject: Re: [PATCH] usb: musb: adding nop usb transceiver
Date: Thu, 22 Jan 2009 23:29:07 -0800	[thread overview]
Message-ID: <200901222329.07689.david-b@pacbell.net> (raw)
In-Reply-To: <1231411988-7330-1-git-send-email-ajay.gupta@ti.com>

On Thursday 08 January 2009, Ajay Kumar Gupta wrote:
> OP transceiver is used by all the usb transceiver which are mostly
> autonomous and doesn't require any programming or which are built
> into the usb ip itself.NOP transceiver only allocates the memory
> for struct xceiv and calls otg_set_transceiver() so function call
> to otg_get_transceiver() will return a valid ransceiver.
> 
> NOP transceiver device is required to be registered using
> platform_device_register() in platform files.
> 
> Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>

We'll need something like this, yes.

This one looks to need a bit of tweaking yet though ...
probably that could be done after merge.  The state can
need changing after one of the drivers is unregistered;
using __exit not __devexit is likely wrong (especially
given your MUSB patchlet); xceiv_to_nop() should be
an inline function; check otg_set_transceiver() value;
don't bother with dev_info(); and I'm not quite sure
of the methods.

Plus I think it's probably best to include a utility
that board init code can call to register the NOP
transceiver device ... instead of cloning that bit of
code (in your second patch) into every board-*.c file
that needs it.

- Dave

  parent reply	other threads:[~2009-01-23  7:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 10:53 [PATCH] usb: musb: adding nop usb transceiver Ajay Kumar Gupta
2009-01-12 22:27 ` Felipe Balbi
2009-01-23  7:29 ` David Brownell [this message]
     [not found]   ` <200901222329.07689.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-01-29  9:34     ` Gupta, Ajay Kumar
     [not found]       ` <19F8576C6E063C45BE387C64729E739403FA790059-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-01-29 20:41         ` David Brownell
     [not found]           ` <200901291241.19602.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-01-30 16:02             ` Gupta, Ajay Kumar

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=200901222329.07689.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=ajay.gupta@ti.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@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