public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx
Date: Fri, 5 Sep 2008 10:52:01 -0700	[thread overview]
Message-ID: <20080905175200.GO24202@atomide.com> (raw)
In-Reply-To: <5e088bd90809051023t6aab7d93jd04d18d6843cb4e6@mail.gmail.com>

* Steve Sakoman <sakoman@gmail.com> [080905 10:24]:
> > At least the first patch needs to be updated for phys_pbase instead of
> > virt_base.
> 
> Yes it does, mcbsp is likely still working by the same accident of fate.
> 
> > Hmm, is the musb broken now?
> 
> It is on Overo if I base my patches against current top of tree
> (a376251519ced5831ed07ed234430725230ed93a)
> 
> Doesn't crash, just quietly doesn't work.  I hear from Beagle folk
> that musb doesn't work there either.   I have it configured as a host
> port, and IIRC so do the Beagle folks
> 
> If I base my patches against the state of the tree just prior to the
> move to rc5 (81c893795c2e1fbe0bf5f638ed6ae1e500b80a2d), musb works as
> well as it ever has.

Well with -rc5 we switched to the drivers/usb/musb code from mainline
kernel. Maybe try to diff musb code with:

$ git-diff 81c893795c2e1fbe0bf5f638ed6ae1e500b80a2d.. drivers/usb/musb

And see if there are any clues?

Tony

  reply	other threads:[~2008-09-05 17:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 11:55 [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Jarkko Nikula
2008-08-21 11:55 ` [RFC] ARM: OMAP: Add support for OMAP2430 in McBSP Jarkko Nikula
2008-08-21 11:55 ` [RFC] ASoC: OMAP: Add support for OMAP2430 and OMAP34xx in McBSP DAI driver Jarkko Nikula
2008-08-21 21:51 ` [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Steve Sakoman
2008-08-22  7:57   ` Jarkko Nikula
2008-08-25 19:19     ` Steve Sakoman
2008-08-25 19:29       ` Felipe Balbi
2008-08-25 21:35       ` Felipe Balbi
2008-08-25 21:39         ` Felipe Balbi
2008-08-25 21:50         ` Steve Sakoman
2008-08-25 21:53           ` Felipe Balbi
2008-08-25 22:13             ` Steve Sakoman
2008-08-25 22:30             ` Steve Sakoman
2008-08-25 22:40               ` Felipe Balbi
2008-08-25 22:54                 ` Felipe Balbi
2008-08-25 23:34                   ` Steve Sakoman
2008-08-26  0:08                     ` Felipe Balbi
2008-08-26 13:19       ` Jarkko Nikula
2008-08-26 14:23         ` Steve Sakoman
2008-08-26 17:18         ` Steve Sakoman
2008-08-27  6:38           ` Jarkko Nikula
2008-08-27 13:39             ` Steve Sakoman
2008-08-27 20:57               ` Steve Sakoman
2008-08-27 21:25                 ` Koen Kooi
2008-08-27 22:14                   ` Steve Sakoman
2008-08-28 11:03                 ` Jarkko Nikula
2008-08-23 11:32 ` Arun KS
2008-09-05  1:12 ` Tony Lindgren
2008-09-05  6:18   ` Steve Sakoman
2008-09-05 16:56     ` Tony Lindgren
2008-09-05 17:23       ` Steve Sakoman
2008-09-05 17:52         ` Tony Lindgren [this message]
2008-09-08 10:29       ` [RFC 0/2 rev2] " Jarkko Nikula
2008-09-09  0:48         ` Tony Lindgren
2008-09-08 10:29       ` [RFC rev2] ARM: OMAP: Add support for OMAP2430 in McBSP Jarkko Nikula
2008-09-08 10:29       ` [RFC rev2] ASoC: OMAP: Add support for OMAP2430 and OMAP34xx in McBSP DAI driver Jarkko Nikula
2008-09-20 11:22     ` [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Arun KS
2008-09-20 11:41       ` Koen Kooi
2008-09-20 12:03         ` Arun KS
     [not found]         ` <dfeb90390809200453i35da7891lcea6d620dbb0e46a@mail.gmail.com>
2008-09-20 12:21           ` Koen Kooi

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=20080905175200.GO24202@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@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