From: Fabrice Gasnier <fabrice.gasnier@st.com>
To: <lee.jones@linaro.org>, <alexandre.torgue@st.com>
Cc: <robh+dt@kernel.org>, <mcoquelin.stm32@gmail.com>,
<arnd@arndb.de>, <mark.rutland@arm.com>,
<gabriel.fernandez@st.com>, <fabrice.gasnier@st.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: [RESEND PATCH v2 0/3] mfd: syscon: Add optional clock support needed on stm32
Date: Mon, 7 Jan 2019 11:07:42 +0100 [thread overview]
Message-ID: <1546855665-26218-1-git-send-email-fabrice.gasnier@st.com> (raw)
STM32 syscfg registers are accessed using syscon. It needs syscfg clock
to be enabled while accessing registers.
This adds support for optional clock on syscon, and the relevant clock
in stm32mp157 device tree.
Changes in v2:
- move clocks to specific bindings using syscon as per Rob's comment
Fabrice Gasnier (3):
dt-bindings: stm32: syscon: add clock support
mfd: syscon: Add optional clock support
ARM: dts: stm32: Add clock on stm32mp157c syscfg
.../devicetree/bindings/arm/stm32/stm32-syscon.txt | 2 ++
arch/arm/boot/dts/stm32mp157c.dtsi | 1 +
drivers/mfd/syscon.c | 19 +++++++++++++++++++
3 files changed, 22 insertions(+)
--
1.9.1
next reply other threads:[~2019-01-07 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:07 Fabrice Gasnier [this message]
2019-01-07 10:07 ` [RESEND PATCH v2 1/3] dt-bindings: stm32: syscon: add clock support Fabrice Gasnier
2019-01-07 10:07 ` [RESEND PATCH v2 2/3] mfd: syscon: Add optional " Fabrice Gasnier
2019-01-07 10:07 ` [RESEND PATCH v2 3/3] ARM: dts: stm32: Add clock on stm32mp157c syscfg Fabrice Gasnier
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=1546855665-26218-1-git-send-email-fabrice.gasnier@st.com \
--to=fabrice.gasnier@st.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).