From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCHv3 0/2] pinctrl: sh-pfc: r8a7796: Add drive strength and bias support
Date: Thu, 17 Nov 2016 16:09:18 +0100 [thread overview]
Message-ID: <20161117150920.18748-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hi,
These patches add drive strength and bias support for both GPIO and none
GPIO pins to r8a7796. Similar to the none GPIO pins for r8a7795 the
system to derive unique pin numbers are the R-Car M3SiP pin layout.
Tested on M3-W and the series depends on the series '[PATCHv3 0/6]
pinctrl: sh-pfc: Fixups for bias handling and preparation for none GPIO
pins'.
Changes since v2
- Update DU_DOTCLKIN2 from physical pin AR7 to AR8.
- Dropped DU_DOTCLKIN3, this pin is not present on r8a7796.
- Renamed FSCLKST# to FSCLKST.
Changes since v1
- Update use of bias information helper function to match changes to the series
which this patch depend on
Niklas Söderlund (2):
pinctrl: sh-pfc: r8a7796: Add drive strength support
pinctrl: sh-pfc: r8a7796: Add bias pinconf support
drivers/pinctrl/sh-pfc/pfc-r8a7796.c | 635 ++++++++++++++++++++++++++++++++++-
1 file changed, 623 insertions(+), 12 deletions(-)
--
2.10.2
next reply other threads:[~2016-11-17 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:09 Niklas Söderlund [this message]
2016-11-17 15:09 ` [PATCHv3 1/2] pinctrl: sh-pfc: r8a7796: Add drive strength support Niklas Söderlund
2016-11-17 15:09 ` [PATCHv3 2/2] pinctrl: sh-pfc: r8a7796: Add bias pinconf support Niklas Söderlund
2016-11-30 7:58 ` [PATCHv3 0/2] pinctrl: sh-pfc: r8a7796: Add drive strength and bias support Geert Uytterhoeven
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=20161117150920.18748-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).