linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Gaignard <benjamin.gaignard@linaro.org>
To: linus.walleij@linaro.org, robh+dt@kernel.org, alexandre.torgue@st.com
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH 0/3] make pin-controller use hwspinlock
Date: Tue, 13 Nov 2018 10:51:39 +0100	[thread overview]
Message-ID: <20181113095142.32015-1-benjamin.gaignard@st.com> (raw)

This series allow to protect pin controller configuration registers
with a hwspinlock to avoid conflicting accesses between processors.

Benjamin Gaignard (3):
  dt-bindings: pinctrl: stm32: Document hwlocks properties
  pinctrl: stm32: protect configuration registers with a hwspinlock
  ARM: dts: stm32: Add hwlock for pinctrl

 .../bindings/pinctrl/st,stm32-pinctrl.txt          |  1 +
 arch/arm/boot/dts/stm32mp157-pinctrl.dtsi          |  1 +
 drivers/pinctrl/stm32/pinctrl-stm32.c              | 71 +++++++++++++++++++++-
 3 files changed, 72 insertions(+), 1 deletion(-)

-- 
2.15.0


             reply	other threads:[~2018-11-13  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  9:51 Benjamin Gaignard [this message]
2018-11-13  9:51 ` [PATCH 1/3] dt-bindings: pinctrl: stm32: Document hwlocks properties Benjamin Gaignard
2018-11-19 12:16   ` Linus Walleij
2018-11-13  9:51 ` [PATCH 2/3] pinctrl: stm32: protect configuration registers with a hwspinlock Benjamin Gaignard
2018-11-13 10:40   ` Alexandre Torgue
2018-11-19 12:20   ` Linus Walleij
2018-11-20  8:38     ` Benjamin Gaignard
2018-11-13  9:51 ` [PATCH 3/3] ARM: dts: stm32: Add hwlock for pinctrl Benjamin Gaignard
2018-11-13  9:58   ` Alexandre Torgue

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=20181113095142.32015-1-benjamin.gaignard@st.com \
    --to=benjamin.gaignard@linaro.org \
    --cc=alexandre.torgue@st.com \
    --cc=benjamin.gaignard@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=robh+dt@kernel.org \
    --subject='Re: [PATCH 0/3] make pin-controller use hwspinlock' \
    /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

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).