From: David Brownell <david-b@pacbell.net>
To: Felipe Balbi <me@felipebalbi.com>
Cc: Paul Walmsley <paul@pwsan.com>, linux-omap@vger.kernel.org
Subject: Re: [RFC PATCH] musb: fix "musb_hdrc: invalid ep 8" messages
Date: Thu, 10 Apr 2008 13:02:35 -0700 [thread overview]
Message-ID: <200804101302.35774.david-b@pacbell.net> (raw)
In-Reply-To: <9d815fa4ee93235dc9f6ed4feb29e74e@felipebalbi.com>
On Thursday 10 April 2008, Felipe Balbi wrote:
> > driver is limited to 8 endpoints by macros in hdrc_cnf.h.
> >
> > Anyway, I don't know much about MUSB. David or Felipe, maybe you could
> > take a quick look at this patch?
>
> I had this same patch queued for sending but i was waiting until i finished
> a whole series for musb driver. :-)
>
> It's acked, if dave doesn't have any comments i think it should be applied.
I don't know who added that hdrc_cnf.h ... it seems to not
match the 3430 hardware though. What *does* it match?
It claims to match DaVinci, but that's obviously wrong.
It would be good to confirm that the 2430, 34xx, and 35xx
all have the same silicon parameters for musb_hdrc, and
that they match that hdrc_cnf.h header ... that's something
which I suspect TI is in the best position to confirm. The
file is after all generated by compiling the Mentor core
for the OMAP chips. :)
- 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
next prev parent reply other threads:[~2008-04-10 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 17:45 [RFC PATCH] musb: fix "musb_hdrc: invalid ep 8" messages Paul Walmsley
2008-04-10 19:21 ` Felipe Balbi
2008-04-10 20:02 ` David Brownell [this message]
2008-04-11 4:34 ` Gadiyar, Anand
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=200804101302.35774.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=paul@pwsan.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