public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Wu <bryan.wu@analog.com>
To: David Brownell <dbrownell@users.sourceforge.net>,
	Tony Lindgren <tony@atomide.com>,
	linux-omap-open-source@linux.omap.com
Subject: Some musb Blackfin porting issues
Date: Thu, 06 Sep 2007 14:52:25 +0800	[thread overview]
Message-ID: <1189061545.8833.11.camel@roc-desktop> (raw)

Dear David and Tony:

I almost imported the musb stack to our Blackfin tree. But there are
some code highly coupled with ARM Linux architecture. Please give me
some idea about following issues:

1. Clock framework is not available in Blackfin Linux arch currently. Is
it possible to skip it?

2. Registers layout in musb-regs.h is different with BF54x processor. I
plan to write a musb-bf54x.h to replace the whole definition in
musb-regs.h. Is that possible or do it conflict with current musb
design?
in musb-regs.h:
---
#ifdef CONFIG_BF54x
#include "musb-bf54x.h"
#else
..... /* original code from musb-regs.h */
#endif
--

Thanks a lot
- Bryan Wu

             reply	other threads:[~2007-09-06  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  6:52 Bryan Wu [this message]
2007-09-06 14:43 ` Some musb Blackfin porting issues Tony Lindgren
2007-09-06 18:44   ` David Brownell

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=1189061545.8833.11.camel@roc-desktop \
    --to=bryan.wu@analog.com \
    --cc=dbrownell@users.sourceforge.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