From: Daniel Mack <daniel@caiaq.de>
To: Nguyen Dinh-R00091 <R00091@freescale.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
amit.kucheria@canonical.com, linux@arm.linux.org.uk,
Herring Robert-RA7055 <RA7055@freescale.com>,
Zhang Lily-R58066 <R58066@freescale.com>,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
Li Jun-R65092 <R65092@freescale.com>,
valentin.longchamp@epfl.ch, bryan.wu@canonical.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 2.6.34-rc4 5/7] mxc: Add generic USB HWinitialization for MX51
Date: Mon, 19 Apr 2010 19:04:35 +0200 [thread overview]
Message-ID: <20100419170435.GC30807@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100419165939.GB30807@buzzloop.caiaq.de>
On Mon, Apr 19, 2010 at 06:59:39PM +0200, Daniel Mack wrote:
> Think about what's necessary to add support for a new board. You don't
> want to copy all the register accessing functions again but re-use and
> share generic code. All you need to have in the board specific support
> code are flags which are passed to the generic driver core. Just like
> all other board support code does it as well. Not just for USB btw. but
> for all sorts of other drivers as wel. Have a look at code which is
> already there to get the idea.
>
> [Btw - your mail client is broken as it wraps quoted lines (see above).
> See Documentation/email-clients.txt]
Sorry, I messed up the To/Cc fields in my reply. The above was directed
to Nguyen Dinh of course, not to Sascha.
next prev parent reply other threads:[~2010-04-19 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 19:16 [PATCHv4 2.6.34-rc4 1/7] mxc: Update GPIO for USB support on Freescale MX51 Babbage HW Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 2/7] mx5: Add USB device definitions for " Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 3/7] mxc: Add new defines for USB HW register bits on Freescale SoCs Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 4/7] mx5: Enable board specific functions for enabling USB host on Babbage Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 5/7] mxc: Add generic USB HW initialization for MX51 Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 6/7] mxc-usb: Add call to initialize MXC USB HW registers Dinh.Nguyen
2010-04-16 19:16 ` [PATCHv4 2.6.34-rc4 7/7] mx5: Add USB to Freescale MX51 defconfig Dinh.Nguyen
2010-04-17 17:07 ` [PATCHv4 2.6.34-rc4 5/7] mxc: Add generic USB HW initialization for MX51 Daniel Mack
2010-04-19 1:03 ` Amit Kucheria
2010-04-19 7:38 ` Daniel Mack
2010-04-18 2:07 ` Sascha Hauer
2010-04-19 15:40 ` [PATCHv4 2.6.34-rc4 5/7] mxc: Add generic USB HWinitialization " Nguyen Dinh-R00091
2010-04-19 15:58 ` Sascha Hauer
2010-04-19 16:59 ` Daniel Mack
2010-04-19 17:04 ` Daniel Mack [this message]
2010-04-19 0:32 ` [PATCHv4 2.6.34-rc4 2/7] mx5: Add USB device definitions for Freescale MX51 Babbage HW Amit Kucheria
2010-04-19 14:48 ` Nguyen Dinh-R00091
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=20100419170435.GC30807@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=R00091@freescale.com \
--cc=R58066@freescale.com \
--cc=R65092@freescale.com \
--cc=RA7055@freescale.com \
--cc=amit.kucheria@canonical.com \
--cc=bryan.wu@canonical.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=valentin.longchamp@epfl.ch \
/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