From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX EHCI initialization
Date: Mon, 17 May 2010 11:36:52 +0200 [thread overview]
Message-ID: <20100517093652.GP31199@pengutronix.de> (raw)
Hi Daniel et all,
I see an increasing number of patches trying to change the
initialization sequence of the i.MX ehci controller. It's getting harder
and harder to keep track what the changes are, what other boards
and SoCs a single patch affects and whether it just reverts another
patch.
I thought about making the initialization completely board specific and
creating a set of helper functions which the board can call if it wants
to to prevent too much code duplication.
What do you think?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next reply other threads:[~2010-05-17 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 9:36 Sascha Hauer [this message]
2010-05-17 9:59 ` i.MX EHCI initialization Daniel Mack
2010-05-18 8:40 ` Sascha Hauer
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=20100517093652.GP31199@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).