[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170530060851.29923-1-joel@jms.id.au>
Date: Tue, 30 May 2017 15:38:49 +0930
From: Joel Stanley <joel@....id.au>
To: Philipp Zabel <p.zabel@...gutronix.de>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Andrew Jeffery <andrew@...id.au>
Subject: [PATCH v2 0/2] reset: Basic reset controller
Hello,
This is v2 of the basic reset controller, which addresses the points that
Philipp made. See the individual patches for changelogs. The original cover
letter follows:
In the Aspeed SoCs we have some reset registers spread out in various parts of
the soc: in the system controller IP, as well as other peripherals. I need to be
able to deassert those resets before other drivers work.
In writing a driver to do this I realised it was very generic. So instead I've
sent a generic driver that can be used by the device tree to clear reset lines
described by single bits in a register.
I've tested this driver on our SoC to release the UART reset.
Joel Stanley (2):
dt-bindings: reset: Add bindings for basic reset controller
reset: Add basic single-register reset driver
.../devicetree/bindings/reset/reset-basic.txt | 43 ++++++++
drivers/reset/Kconfig | 7 ++
drivers/reset/Makefile | 1 +
drivers/reset/reset-basic.c | 113 +++++++++++++++++++++
4 files changed, 164 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/reset-basic.txt
create mode 100644 drivers/reset/reset-basic.c
--
2.11.0
Powered by blists - more mailing lists