From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
frowand.list@gmail.com, ckeepax@opensource.wolfsonmicro.com,
ldewangan@nvidia.com, Ryan Chen <ryan_chen@aspeedtech.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] gpio: aspeed: Add support for reset tolerance
Date: Tue, 7 Nov 2017 15:31:39 +1030 [thread overview]
Message-ID: <CACPK8XcTU84w4e4qtbUxsqBNpv2ucNu4AcicHWb7NRrVM3Dveg@mail.gmail.com> (raw)
In-Reply-To: <20171101040457.1200-3-andrew@aj.id.au>
On Wed, Nov 1, 2017 at 2:34 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> Use the new pinconf parameter for state persistence to expose the
> associated capability of the Aspeed GPIO controller.
>
> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
I took a look and checked the offsets against the datasheet. LGTM.
Reviewed-by: Joel Stanley <joel@jms.id.au>
Cheers,
Joel
prev parent reply other threads:[~2017-11-07 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 4:04 [PATCH v3 0/2] gpio: Generalise state persistence Andrew Jeffery
[not found] ` <20171101040457.1200-1-andrew-zrmu5oMJ5Fs@public.gmane.org>
2017-11-01 4:04 ` [PATCH v3 1/2] gpio: gpiolib: Generalise state persistence beyond sleep Andrew Jeffery
[not found] ` <20171101040457.1200-2-andrew-zrmu5oMJ5Fs@public.gmane.org>
2017-11-01 10:09 ` Charles Keepax
2017-11-02 0:15 ` Rob Herring
2017-11-24 9:50 ` Linus Walleij
2017-11-01 4:04 ` [PATCH v3 2/2] gpio: aspeed: Add support for reset tolerance Andrew Jeffery
2017-11-07 5:01 ` Joel Stanley [this message]
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=CACPK8XcTU84w4e4qtbUxsqBNpv2ucNu4AcicHWb7NRrVM3Dveg@mail.gmail.com \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.com \
/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).