From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Reset controller API to reset IP modules on i.MX5 and i.MX6
Date: Wed, 13 Feb 2013 18:34:24 +0100 [thread overview]
Message-ID: <1360776872-18584-1-git-send-email-p.zabel@pengutronix.de> (raw)
The system reset controller (SRC) on i.MX51, i.MX53, and i.MX6q controls
reset lines to the GPU, VPU, IPU, and OpenVG IP modules.
The following patches add a simple API for devices to request being reset
by separate reset controller hardware and implements the reset signal
device tree binding proposed by Stephen Warren. Contrary to Tegra hardware,
the i.MX SRC contains self-deasserting reset registers, so I've included
both ops to manually assert/deassert a reset line, as well as a "reset"
operation that is supposed to assert the reset line and wait for it to
deassert.
The i.MX SRC is enhanced to provide a reset controller and the IPU driver
is made to request being reset by calling the device_reset(&pdev->dev)
convenience wrapper during probing.
Changes since v1:
- Fixed issues from comments
- Added reset controller driver for GPIO controlled resets
regards
Philipp
---
.../devicetree/bindings/reset/fsl,imx-src.txt | 49 ++++
Documentation/devicetree/bindings/reset/reset.txt | 75 ++++++
.../bindings/staging/imx-drm/fsl-imx-drm.txt | 3 +
arch/arm/boot/dts/imx51.dtsi | 7 +
arch/arm/boot/dts/imx53.dtsi | 7 +
arch/arm/boot/dts/imx6q.dtsi | 5 +-
arch/arm/mach-imx/Kconfig | 2 +
arch/arm/mach-imx/mm-imx5.c | 2 +
arch/arm/mach-imx/src.c | 58 ++++-
drivers/Kconfig | 2 +
drivers/Makefile | 3 +
drivers/reset/Kconfig | 22 ++
drivers/reset/Makefile | 2 +
drivers/reset/core.c | 238 ++++++++++++++++++++
drivers/reset/gpio-reset.c | 188 ++++++++++++++++
drivers/staging/imx-drm/ipu-v3/ipu-common.c | 12 +-
include/linux/reset-controller.h | 39 ++++
include/linux/reset.h | 17 ++
18 files changed, 726 insertions(+), 5 deletions(-)
next reply other threads:[~2013-02-13 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 17:34 Philipp Zabel [this message]
2013-02-13 17:34 ` [PATCH v2 1/8] dt: describe base reset signal binding Philipp Zabel
2013-02-17 13:05 ` Shawn Guo
2013-02-19 11:33 ` Philipp Zabel
2013-02-13 17:34 ` [PATCH v2 2/8] reset: Add reset controller API Philipp Zabel
2013-02-17 14:51 ` Shawn Guo
2013-02-13 17:34 ` [PATCH v2 3/8] ARM i.MX6q: Add GPU, VPU, IPU, and OpenVG resets to System Reset Controller (SRC) Philipp Zabel
2013-02-17 14:57 ` Shawn Guo
2013-02-18 1:56 ` Shawn Guo
2013-02-13 17:34 ` [PATCH v2 4/8] ARM i.MX6q: Link system reset controller (SRC) to IPU in DT Philipp Zabel
2013-02-13 17:34 ` [PATCH v2 5/8] staging: drm/imx: Use SRC to reset IPU Philipp Zabel
2013-02-13 17:34 ` [PATCH v2 6/8] ARM i.MX5: Add System Reset Controller (SRC) support for i.MX51 and i.MX53 Philipp Zabel
2013-02-13 17:34 ` [PATCH v2 7/8] ARM i.MX5: Add system reset controller (SRC) to i.MX51 and i.MX53 device tree Philipp Zabel
2013-02-13 17:34 ` [PATCH v2 8/8] reset: Add driver for gpio-controlled reset pins Philipp Zabel
2013-02-14 10:56 ` Russell King - ARM Linux
2013-02-15 9:27 ` Philipp Zabel
2013-02-18 2:22 ` Shawn Guo
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=1360776872-18584-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@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).