From: Joel Stanley <joel@jms.id.au>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [PATCH 0/2] reset: Basic reset controller
Date: Fri, 26 May 2017 13:32:12 +1000 [thread overview]
Message-ID: <20170526033214.8081-1-joel@jms.id.au> (raw)
Hello,
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.
Let me know what you think of the idea. 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 | 31 ++++++
drivers/reset/Kconfig | 6 ++
drivers/reset/Makefile | 1 +
drivers/reset/reset-basic.c | 109 +++++++++++++++++++++
4 files changed, 147 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/reset-basic.txt
create mode 100644 drivers/reset/reset-basic.c
--
2.11.0
next reply other threads:[~2017-05-26 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 3:32 Joel Stanley [this message]
2017-05-26 3:32 ` [PATCH 1/2] dt-bindings: reset: Add bindings for basic " Joel Stanley
2017-05-29 9:09 ` Philipp Zabel
2017-05-29 10:16 ` Joel Stanley
2017-05-26 3:32 ` [PATCH 2/2] reset: Add basic single-register reset driver Joel Stanley
2017-05-27 15:11 ` Andy Shevchenko
2017-05-29 10:24 ` Joel Stanley
2017-05-29 15:41 ` Andy Shevchenko
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=20170526033214.8081-1-joel@jms.id.au \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®