From: Linus Walleij <linus.walleij@linaro.org>
To: Andrei.Stefanescu@microchip.com
Cc: Rob Herring <robh+dt@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Nicolas Ferre <Nicolas.Ferre@microchip.com>,
Mark Rutland <mark.rutland@arm.com>,
Ludovic Desroches <Ludovic.Desroches@microchip.com>,
Cristian.Birsan@microchip.com,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: atmel: describe SECUMOD usage as a GPIO controller
Date: Fri, 21 Dec 2018 10:55:09 +0100 [thread overview]
Message-ID: <CACRpkdY+u0jiPNwbFR6pnaFm4VyXmw3q6JTBS+HNUniDuWaOXA@mail.gmail.com> (raw)
In-Reply-To: <1544615784-29331-2-git-send-email-andrei.stefanescu@microchip.com>
On Wed, Dec 12, 2018 at 12:57 PM <Andrei.Stefanescu@microchip.com> wrote:
> This patch describes the Security Module's usage as a GPIO
> controller for its PIOBU pins. These pins have the special
> property of maintaining their voltage during suspend-to-mem.
>
> Signed-off-by: Andrei Stefanescu <andrei.stefanescu@microchip.com>
Patch applied with Rob's ACK.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-12-21 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:56 [PATCH v4 0/2] add SAMA5D2 PIOBU GPIO driver Andrei.Stefanescu
2018-12-12 11:57 ` [PATCH v4 1/2] dt-bindings: arm: atmel: describe SECUMOD usage as a GPIO controller Andrei.Stefanescu
2018-12-17 21:47 ` Rob Herring
2018-12-21 9:55 ` Linus Walleij [this message]
2018-12-12 11:57 ` [PATCH v4 2/2] gpio: add driver for SAMA5D2 PIOBU pins Andrei.Stefanescu
2018-12-21 9:57 ` Linus Walleij
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=CACRpkdY+u0jiPNwbFR6pnaFm4VyXmw3q6JTBS+HNUniDuWaOXA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Andrei.Stefanescu@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).