public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Dmitry Baryshkov <dbaryshkov@gmail.com>
Cc: Felipe Balbi <me@felipebalbi.com>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/4] Hook start_hnp into ohci struct
Date: Sun, 6 Jul 2008 16:00:11 -0700	[thread overview]
Message-ID: <200807061600.11926.david-b@pacbell.net> (raw)
In-Reply-To: <20080706103332.GA28505@doriath.ww600.siemens.net>

On Sunday 06 July 2008, Dmitry Baryshkov wrote:
> > > +           ohci->start_hnp = start_hnp;
> > 
> > Why? It's part of struct otg_transceiver.
> > 
> 
> Actually the ohci-omap.c:start_hnp does a bit more than just
> otg_start_hnp(tranceiver). Maybe it should be merged. I dunno.

I'm fine with it staying the way it is.  It starts HNP ...
that job is split between several components, and the
transceiver doesn't handle them all.

- Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-07-06 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080706102630.GA29934@doriath.ww600.siemens.net>
     [not found] ` <20080706103050.GB20019@kedavra.cpe.vivax.com.br>
     [not found]   ` <20080706103050.GB20019-4vvIQG7NF+ITKvXZea5imILpUPVTGn5w@public.gmane.org>
2008-07-06 10:33     ` [PATCH 3/4] Hook start_hnp into ohci struct Dmitry Baryshkov
     [not found]       ` <20080706103332.GA28505-nIupHZaCssqR2kOLt6zJ8ErlnG4Plg33XqFh9Ls21Oc@public.gmane.org>
2008-07-06 11:05         ` Felipe Balbi
2008-07-06 11:55           ` Dmitry Baryshkov
2008-07-06 23:00       ` David Brownell [this message]
2008-07-06 10:26 Dmitry Baryshkov

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=200807061600.11926.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=me@felipebalbi.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