From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH 0/4] pinctrl: sh-pfc: Add VIN stf8 pins
Date: Tue, 15 Sep 2020 01:37:40 +0200 [thread overview]
Message-ID: <20200914233744.468175-1-niklas.soderlund+renesas@ragnatech.se> (raw)
Hello,
This series upports pinctrl configuration for VIN4 and VIN5 SFT8 pins
from the Renesas BSP. All patches are are based on work from Takeshi
Kihara.
Niklas Söderlund (2):
pinctrl: sh-pfc: r8a77990: Add VIN stf8 pins
pinctrl: sh-pfc: r8a77965: Add VIN stf8 pins
Takeshi Kihara (2):
pinctrl: sh-pfc: r8a77951: Add VIN pins, groups and functions
pinctrl: sh-pfc: r8a7796: Add VIN pins, groups and functions
drivers/pinctrl/sh-pfc/pfc-r8a77951.c | 28 +++++++++++++++++++++++
drivers/pinctrl/sh-pfc/pfc-r8a7796.c | 28 +++++++++++++++++++++++
drivers/pinctrl/sh-pfc/pfc-r8a77965.c | 32 +++++++++++++++++++++++++++
drivers/pinctrl/sh-pfc/pfc-r8a77990.c | 32 +++++++++++++++++++++++++++
4 files changed, 120 insertions(+)
--
2.28.0
next reply other threads:[~2020-09-14 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 23:37 Niklas Söderlund [this message]
2020-09-14 23:37 ` [PATCH 1/4] pinctrl: sh-pfc: r8a77951: Add VIN pins, groups and functions Niklas Söderlund
2020-09-15 8:23 ` Sergei Shtylyov
2020-09-23 9:57 ` Geert Uytterhoeven
2020-09-14 23:37 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7796: " Niklas Söderlund
2020-09-15 8:24 ` Sergei Shtylyov
2020-09-14 23:37 ` [PATCH 3/4] pinctrl: sh-pfc: r8a77990: Add VIN stf8 pins Niklas Söderlund
2020-09-15 8:17 ` Sergei Shtylyov
2020-09-14 23:37 ` [PATCH 4/4] pinctrl: sh-pfc: r8a77965: " Niklas Söderlund
2020-09-15 8:18 ` Sergei Shtylyov
2020-09-15 8:50 ` Geert Uytterhoeven
2020-09-15 9:12 ` Sergei Shtylyov
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=20200914233744.468175-1-niklas.soderlund+renesas@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=geert@linux-m68k.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).