From: gabriel.fernandez@st.com (gabriel.fernandez at st.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] Introduce STM32MP1 Reset driver
Date: Mon, 19 Mar 2018 08:25:49 +0100 [thread overview]
Message-ID: <1521444351-29550-1-git-send-email-gabriel.fernandez@st.com> (raw)
From: Gabriel Fernandez <gabriel.fernandez@st.com>
v3:
remove unused includes
fix status ops
fix from Fengguang Wu
for Kbuild test robot: symbol 'stm32_reset_ops' was not declared. Should it be static?
use 'builtin_platform_driver' instead 'postcore_initcall'
v2:
Don't use reset-simple driver but a custom reset driver.
add dt-binding documentation.
This patch-set enables the reset of STM32MP1.
STM32MP1 reset IP has a register to assert by writing '1' and another
register to de-assert by writing '1'.
The patch 'dt-bindings: reset: add STM32MP1 resets' could be squashed
with the patch:
'dt-bindings: Document STM32MP1 Reset Clock Controller (RCC) bindings'
commit 3830681d354f
Gabriel Fernandez (2):
dt-bindings: reset: add STM32MP1 resets
reset: stm32mp1: Enable stm32mp1 reset driver
.../devicetree/bindings/reset/st,stm32mp1-rcc.txt | 6 ++
drivers/reset/Kconfig | 6 ++
drivers/reset/Makefile | 1 +
drivers/reset/reset-stm32mp1.c | 115 +++++++++++++++++++++
include/dt-bindings/reset/stm32mp1-resets.h | 108 +++++++++++++++++++
5 files changed, 236 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt
create mode 100644 drivers/reset/reset-stm32mp1.c
create mode 100644 include/dt-bindings/reset/stm32mp1-resets.h
--
1.9.1
next reply other threads:[~2018-03-19 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 7:25 gabriel.fernandez at st.com [this message]
2018-03-19 7:25 ` [PATCH v3 1/2] dt-bindings: reset: add STM32MP1 resets gabriel.fernandez at st.com
2018-03-19 9:02 ` Philipp Zabel
2018-03-19 9:28 ` Gabriel FERNANDEZ
2018-03-19 7:25 ` [PATCH v3 2/2] reset: stm32mp1: Enable stm32mp1 reset driver gabriel.fernandez at st.com
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=1521444351-29550-1-git-send-email-gabriel.fernandez@st.com \
--to=gabriel.fernandez@st.com \
--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).