public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Felipe Balbi <felipebalbi@users.sourceforge.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix usb gadget related compile errors and typo
Date: Mon, 29 Oct 2007 15:42:44 -0700	[thread overview]
Message-ID: <200710291542.45173.david-b@pacbell.net> (raw)
In-Reply-To: <31e679430710291445m72bbff1btc79308599af157ff@mail.gmail.com>

On Monday 29 October 2007, Felipe Balbi wrote:
> On 10/29/07, David Brownell <david-b@pacbell.net> wrote:
> > > is there any plans on upgrading isp1301 driver to the new style i2c
> > > driver also?? how could i help you with that?
> >
> > ISTR sending some code like that to the I2C list a while back, but
> > it's not yet been merged.
> 
> I see...
> 
> >
> > You could finish that, if it's not already sitting in Jean's I2C queue.
> > And if it is, you could maybe get it into the OMAP tree before 2.6.25
> > merges begin.  :)
> 
> do Jean have a gittree in kernel.org, couldn't find search the name...

He's got a quilt patch tree.  I have it bookmarked as:

  http://khali.linux-fr.org/devel/linux-2.6/jdelvare-i2c/?M=A

Seems not to have the isp1301 driver stuff ... that should be in
the i2c list archives.


> it would be easier just git-pull from there.. but if there isn't I'll
> do it manually and test with omap h2 and omap h3 boards once I'm back
> in brazil (next week).

... And it'd be nice if someone could update the H3 support to
include the IRQ used to hook up the tps65013 chip.  ;)


> well, in any case, I'll try to get these in sync between i2c/mainline
> and linux-omap tree.

Not straightforward, as I recall.  Or it'd be working already.
The issue is that the OTG state machine changed, so that various
transitions (I forget which ones!) behave incompatibly.

> >
> > > tps65010 driver is really better with that i2c_board_info structure in
> > > board files and there's a note to make isp1301 driver work the same
> > > way.
> >
> > Yep.  In fact, all the I2C code that OMAP uses should switch
> > over to new-style drivers ...
> >
> > That includes the pcf875x i/o expanders found on many TI devel
> > boards.  Making that change involves some updates to the GPIO
> > framework.  I've got some code to address all that, which I'll
> > be posting in a few days.
> 
> ok.. that'll help, could you please cc me so I can get those as soon
> as you publish them to apply on linux and test/validate with omap
> boards ?

What I'll do is forward the OMAP patches to this list ... both the
generic stuff (affecting the plat-omap/gpio.c code), and board-specific
stuff (affecting debug boards, tps6501x, etc).  The board-specific
stuff will need more work, it's not all that current.

- Dave

  reply	other threads:[~2007-10-29 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 19:55 [PATCH] ARM: OMAP: Fix usb gadget related compile errors and typo Dirk Behme
2007-10-29 20:11 ` David Brownell
2007-10-29 20:44   ` Felipe Balbi
2007-10-29 21:33     ` David Brownell
2007-10-29 21:45       ` Felipe Balbi
2007-10-29 22:42         ` David Brownell [this message]
2007-10-29 22:52           ` Felipe Balbi
2007-10-30 16:37   ` Dirk Behme
2007-10-30 17:00     ` David Brownell
2007-11-01  9:00       ` Tony Lindgren
2007-11-01 16:28         ` Dirk Behme
2007-11-15 20:40           ` Tony Lindgren

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=200710291542.45173.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=felipebalbi@users.sourceforge.net \
    --cc=linux-omap-open-source@linux.omap.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