public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: Tony Lindgren <tony@atomide.com>,
	David Brownell <david-b@pacbell.net>,
	linux-omap-open-source@linux.omap.com
Subject: How to port the musb to a new processor?
Date: Wed, 29 Aug 2007 17:27:14 +0800	[thread overview]
Message-ID: <1188379634.5910.8.camel@roc-desktop> (raw)

Hi Tony and David,

There days, I am trying to enable musb stack in my Blackfin Linux tree.
After comparing the musb_regs.h with the BF54x USB register layout, I
found it is not very easy to use the musb_regs.h for the porting.

1. Offset of the musb_regs.h is different with the BF54x
2. Some musb_regs are 8-bit wide, while on BF54x most of them are 16-bit
or 32-bit.
3. Some register not in BF54x and some BF54x register is not in
musb_reg.h

But most BF54x USB register can found one in musb_regs.h

I just wondering how to abstract this definition to BF54x hardware as
Davinci or OMAP does.

Thanks a lot
Best Regards,

- Bryan Wu

             reply	other threads:[~2007-08-29  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  9:27 Bryan Wu [this message]
2007-08-29 17:37 ` How to port the musb to a new processor? David Brownell
2007-08-30  9:52   ` Bryan Wu

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=1188379634.5910.8.camel@roc-desktop \
    --to=bryan.wu@analog.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tony@atomide.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