From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [patch v2] i.MX7 support
Date: Thu, 19 Jan 2017 16:23:50 +0100 [thread overview]
Message-ID: <20170119152355.2280-1-s.hauer@pengutronix.de> (raw)
This is the second round of i.MX7 patches. I send here only
the patches that have changed.
Changes since last round:
- Add pfuze driver
- Add support for 2nd iomux controller
- initialize architected timer so that it works under Linux
Sascha
----------------------------------------------------------------
Juergen Borleis (3):
ARM: i.MX: Add i.MX7 base architecture support
pinmmux: i.MX: add pin mux support for i.MX7
ARM: i.MX: Add WaRP7 board support
Sascha Hauer (2):
ARM: i.MX7: initialize architected timer
regulator: Add pfuze driver
Documentation/boards/imx.rst | 1 +
Documentation/boards/imx/Element14-WaRP7.rst | 54 +++++++
arch/arm/boards/Makefile | 1 +
arch/arm/boards/element14-warp7/Makefile | 2 +
arch/arm/boards/element14-warp7/board.c | 35 +++++
.../element14-warp7/flash-header-mx7-warp.imxcfg | 81 ++++++++++
arch/arm/boards/element14-warp7/lowlevel.c | 48 ++++++
arch/arm/dts/Makefile | 1 +
arch/arm/dts/imx7s-warp.dts | 62 ++++++++
arch/arm/mach-imx/Kconfig | 9 ++
arch/arm/mach-imx/Makefile | 1 +
arch/arm/mach-imx/boot.c | 70 +++++++++
arch/arm/mach-imx/cpu_init.c | 5 +
arch/arm/mach-imx/imx.c | 6 +
arch/arm/mach-imx/imx7.c | 110 ++++++++++++++
arch/arm/mach-imx/include/mach/debug_ll.h | 3 +
arch/arm/mach-imx/include/mach/generic.h | 16 ++
arch/arm/mach-imx/include/mach/imx7-regs.h | 24 +++
arch/arm/mach-imx/include/mach/imx7.h | 59 +++++++
arch/arm/mach-imx/include/mach/imx_cpu_types.h | 1 +
common/Kconfig | 8 +
drivers/pinctrl/imx-iomux-v3.c | 40 ++++-
drivers/regulator/Kconfig | 4 +
drivers/regulator/Makefile | 1 +
drivers/regulator/pfuze.c | 169 +++++++++++++++++++++
images/Makefile.imx | 5 +
include/mfd/pfuze.h | 6 +
include/serial/imx-uart.h | 5 +
scripts/imx/imx.c | 1 +
29 files changed, 820 insertions(+), 8 deletions(-)
create mode 100644 Documentation/boards/imx/Element14-WaRP7.rst
create mode 100644 arch/arm/boards/element14-warp7/Makefile
create mode 100644 arch/arm/boards/element14-warp7/board.c
create mode 100644 arch/arm/boards/element14-warp7/flash-header-mx7-warp.imxcfg
create mode 100644 arch/arm/boards/element14-warp7/lowlevel.c
create mode 100644 arch/arm/dts/imx7s-warp.dts
create mode 100644 arch/arm/mach-imx/imx7.c
create mode 100644 arch/arm/mach-imx/include/mach/imx7-regs.h
create mode 100644 arch/arm/mach-imx/include/mach/imx7.h
create mode 100644 drivers/regulator/pfuze.c
create mode 100644 include/mfd/pfuze.h
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2017-01-19 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 15:23 Sascha Hauer [this message]
2017-01-19 15:23 ` [PATCH 1/5] ARM: i.MX: Add i.MX7 base architecture support Sascha Hauer
2017-01-19 15:23 ` [PATCH 2/5] pinmmux: i.MX: add pin mux support for i.MX7 Sascha Hauer
2017-01-19 15:23 ` [PATCH 3/5] ARM: i.MX: Add WaRP7 board support Sascha Hauer
2017-01-19 15:23 ` [PATCH 4/5] ARM: i.MX7: initialize architected timer Sascha Hauer
2017-01-19 15:23 ` [PATCH 5/5] regulator: Add pfuze driver 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=20170119152355.2280-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