All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] usb: change the dependency chain for LPC32XX and ISP1301
Date: Thu, 23 Aug 2012 10:59:00 +0200	[thread overview]
Message-ID: <5035F0D4.9020001@antcom.de> (raw)
In-Reply-To: <5035E9D0.9020107@linutronix.de>

On 08/23/2012 10:29 AM, Sebastian Andrzej Siewior wrote:
>> For the PNX4008 removal - should I already post a patch to build the
>> respective changes on top of, without PNX4008 references?
> 
> If nobody cares about PNX4008 and nobody tested if it actually works in
> the OHCI mode I don't see the point in keeping it around especially if
> there are rumors to remove the arch.
> 
> It would be nice, if you could manage to compile this thingy without
> I2C. In the end one could attach something different than isp1301, no?
> So I think, in the perfect world you would probe for your phy and
> notice that it is not there and print a message: "Dude! Select isp1301
> for OHCI, aight?!"

Currently, we really need I2C for OHCI on LPC32XX, so actually need to
depend on it. Removing the I2C calls in ohci-nxp.c is waiting for the
phy framework so that I don't need to introduce new API in isp1301.c at
this point.

And right, in the ideal world, we have no I2C dependency and can control
a phy in an abstract way, even without depending on ISP1301, which could
be replaced by sth. else (not sure if this will be done/soldered
practically, though).

For now, will post patches for the current I2C dependency and the
PNX4008 removal.

Roland

      reply	other threads:[~2012-08-23  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.1208221537260.1328-100000@iolanthe.rowland.org>
2012-08-22 22:16 ` [PATCH 1/2] usb: change the dependency chain for LPC32XX and ISP1301 Roland Stigge
2012-08-23  7:21   ` Sebastian Andrzej Siewior
2012-08-23  8:18     ` Roland Stigge
2012-08-23  8:29       ` Sebastian Andrzej Siewior
2012-08-23  8:59         ` Roland Stigge [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=5035F0D4.9020001@antcom.de \
    --to=stigge@antcom.de \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.