mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Felipe Balbi <balbi@ti.com>, Yuan-Hsin Chen <yuanlmm@gmail.com>,
	<gregkh@linuxfoundation.org>, <sarah.a.sharp@linux.intel.com>,
	<Julia.Lawall@lip6.fr>, <linux-usb@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Yuan-Hsin Chen <yhchen@faraday-tech.com>,
	<john453@faraday-tech.com>
Subject: Re: [PATCH] usb host: Faraday FUSBH200 HCD driver.
Date: Mon, 18 Mar 2013 20:23:17 +0200	[thread overview]
Message-ID: <20130318182316.GA13371@arwen.pp.htv.fi> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1303181010540.1922-100000@iolanthe.rowland.org>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

Hi,

On Mon, Mar 18, 2013 at 10:16:56AM -0400, Alan Stern wrote:
> > > it would cause copious modification and duplication of ehci hcd
> > > driver. For example, there is no "configured_flag" register in
> > > fusbh200 controller, yet, ehci hcd driver accesses "configured_flag"
> > > in function ehci_run which would cause compile errors. Therefore,
> > > maybe my first patch which refers to oxu210hp-hcd is a better
> > > solution?
> > 
> > why don't you just add a quirk flag to ehci struct so that it knows it
> > shouldn't access CONFIGFLAG register when that's non-existent ?
> > 
> > There are only 5 uses of configured_flag in ehci-hcd.c, so it should be
> > easy to wrap that around a flag check.
> 
> Two of those uses turn configured_flag on and two of them turn it off.  
> However, one of the uses tests its value (the first one in
> ehci_resume).  How would that be handled if configured_flag doesn't
> exist?

perhaps they don't use it because they have a root-hub TT ? In that case
you assume EHCI *always* owns the port. Would that work ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-03-18 18:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 11:24 Yuan-Hsin Chen
2013-02-06 15:46 ` Alan Stern
2013-02-06 16:38 ` Felipe Balbi
2013-02-07  3:03   ` Yuan-Hsin Chen
2013-03-18 10:06     ` Yuan-Hsin Chen
2013-03-18 10:18       ` Felipe Balbi
2013-03-18 14:16         ` Alan Stern
2013-03-18 18:23           ` Felipe Balbi [this message]
2013-03-18 18:47             ` Alan Stern
2013-03-19 10:14           ` Yuan-Hsin Chen
2013-03-19 15:48             ` Alan Stern
2013-03-20  5:50               ` Yuan-Hsin Chen
2013-03-20 13:24               ` Yuan-Hsin Chen
2013-03-20 14:26                 ` Alan Stern
2013-03-21  6:35                   ` Yuan-Hsin Chen
2013-04-01  7:53 ` [PATCH v2] " Yuan-Hsin Chen
2013-04-16 12:43 ` [PATCH v3] usb host: Faraday USB2.0 FUSBH200-HCD driver Yuan-Hsin Chen
2013-04-26  9:37 ` [PATCH v4] " Yuan-Hsin Chen
2013-05-08 12:39   ` Yuan-Hsin Chen
2013-05-08 14:40     ` Alan Stern
2013-05-08 15:11       ` Yuan-Hsin Chen
2013-05-08 15:39       ` Greg KH
2013-05-17  0:45   ` Greg KH
2013-05-17 10:03     ` Yuan-Hsin Chen
2013-05-17 10:14     ` [PATCH v5] " Yuan-Hsin Chen

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=20130318182316.GA13371@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=Julia.Lawall@lip6.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=john453@faraday-tech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=yhchen@faraday-tech.com \
    --cc=yuanlmm@gmail.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

all inboxes | Powered by JetHome®