From: Wolfram Sang <wsa@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Ulrich Hecht <uli+renesas@fpond.eu>,
Phong Hoang <phong.hoang.wz@renesas.com>
Subject: Re: [PATCH/RFC v2 2/2] gpio: rcar: Add R-Car V3U (R8A7799A) support
Date: Wed, 30 Dec 2020 17:06:28 +0100 [thread overview]
Message-ID: <20201230160628.GG23641@kunai> (raw)
In-Reply-To: <20201030081522.2297074-3-geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
On Fri, Oct 30, 2020 at 09:15:22AM +0100, Geert Uytterhoeven wrote:
> Add support for the GPIO controller block in the R-Car V3U (R8A779A0)
> SoC, which is very similar to the block found on other R-Car Gen3 SoCs.
> However, this block has a new General Input Enable Register (INEN),
> whose reset state is to have all inputs disabled.
>
> Enable input for all available pins in probe and resume, to support the
> use of the General Input Register (INDT) for reading pin state at all
> times. This preserves backwards compatibility with other R-Car Gen3
> SoCs, as recommended by the Hardware Manual.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-12-30 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 8:15 [PATCH/RFC v2 0/2] R-Car V3U GPIO support Geert Uytterhoeven
2020-10-30 8:15 ` [PATCH/RFC v2 1/2] gpio: rcar: Optimize GPIO pin state read on R-Car Gen3 Geert Uytterhoeven
2020-11-04 5:23 ` Yoshihiro Shimoda
2020-11-04 10:51 ` Geert Uytterhoeven
2020-12-30 16:06 ` Wolfram Sang
2020-10-30 8:15 ` [PATCH/RFC v2 2/2] gpio: rcar: Add R-Car V3U (R8A7799A) support Geert Uytterhoeven
2020-11-04 5:41 ` Yoshihiro Shimoda
2020-12-30 16:06 ` Wolfram Sang [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=20201230160628.GG23641@kunai \
--to=wsa@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=phong.hoang.wz@renesas.com \
--cc=uli+renesas@fpond.eu \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.