From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/5] ESDHC xload: Prepare for Layerscape support
Date: Mon, 4 Mar 2019 14:18:48 +0100 [thread overview]
Message-ID: <20190304131853.30864-1-s.hauer@pengutronix.de> (raw)
The i.MX ESDHC xload support needs some preparations before Layerscape
support can be added. These are done here, the actual Layerscape support
comes in a later series.
Sascha
Sascha Hauer (5):
esdhc-xload: Move to drivers/mci
esdhc-xload: move some register defines to header file
esdhc-xload: Use static inline io wrappers
esdhc-xload: Add bigendian support
esdhc-xload: check for PRSSTAT_BREN only after each block
arch/arm/mach-imx/Kconfig | 2 +
arch/arm/mach-imx/Makefile | 2 +-
drivers/mci/Kconfig | 3 +
drivers/mci/Makefile | 1 +
.../mci/imx-esdhc-pbl.c | 105 +++++++++++-------
drivers/mci/imx-esdhc.c | 9 --
drivers/mci/imx-esdhc.h | 8 ++
7 files changed, 79 insertions(+), 51 deletions(-)
rename arch/arm/mach-imx/xload-esdhc.c => drivers/mci/imx-esdhc-pbl.c (79%)
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-03-04 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 13:18 Sascha Hauer [this message]
2019-03-04 13:18 ` [PATCH 1/5] esdhc-xload: Move to drivers/mci Sascha Hauer
2019-03-04 13:18 ` [PATCH 2/5] esdhc-xload: move some register defines to header file Sascha Hauer
2019-03-04 13:18 ` [PATCH 3/5] esdhc-xload: Use static inline io wrappers Sascha Hauer
2019-03-04 13:18 ` [PATCH 4/5] esdhc-xload: Add bigendian support Sascha Hauer
2019-03-04 13:18 ` [PATCH 5/5] esdhc-xload: check for PRSSTAT_BREN only after each block 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=20190304131853.30864-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@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