devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Eugeniu Rosca <erosca@de.adit-jv.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/3] pinctrl: sh-pfc: Add r8a77961 support
Date: Wed, 23 Oct 2019 14:29:52 +0200	[thread overview]
Message-ID: <20191023122955.12420-1-geert+renesas@glider.be> (raw)

	Hi all,

This patch series adds support for the Pin Function Controller in the
Renesas R-Car M3-W+ (R8A77961) SoC.  As R-Car M3-W+ is very similar to
R-Car M3-W (R8A77960), the existing driver for R-Car M3-W is updated to
handle both.

To avoid confusion between R-Car M3-W and M3-W+, the existing config
symbol for M3-W is renamed to PINCTRL_PFC_R8A77960 in a dependency-free
way, and references to r8a7796 are updated.

Changes compared to v1[1]:
  - Split in per-subsystem series,
  - Add Reviewed-by, Tested-by,
  - Rename PINCTRL_PFC_R8A7796,
  - Update r8a7796 references,

I intend to queue this series in sh-pfc-for-v5.5.

Thanks for your comments!

[1] "[PATCH/RFC 00/19] arm64: dts: renesas: Initial support for R-Car M3-W+"
    https://lore.kernel.org/linux-renesas-soc/20191007102332.12196-1-geert+renesas@glider.be/

Geert Uytterhoeven (3):
  dt-bindings: pinctrl: sh-pfc: Document r8a77961 support
  pinctrl: sh-pfc: Rename PINCTRL_PFC_R8A7796 to PINCTRL_PFC_R8A77960
  pinctrl: sh-pfc: r8a7796: Add R8A77961 PFC support

 .../bindings/pinctrl/renesas,pfc-pinctrl.txt  |  3 +-
 drivers/pinctrl/sh-pfc/Kconfig                |  8 +++--
 drivers/pinctrl/sh-pfc/Makefile               |  3 +-
 drivers/pinctrl/sh-pfc/core.c                 | 10 ++++--
 drivers/pinctrl/sh-pfc/pfc-r8a7796.c          | 33 +++++++++++++++++--
 drivers/pinctrl/sh-pfc/sh_pfc.h               |  3 +-
 6 files changed, 50 insertions(+), 10 deletions(-)

-- 
2.17.1

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2019-10-23 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 12:29 Geert Uytterhoeven [this message]
2019-10-23 12:29 ` [PATCH v2 1/3] dt-bindings: pinctrl: sh-pfc: Document r8a77961 support Geert Uytterhoeven
2019-10-26  0:20   ` Rob Herring
2019-10-23 12:29 ` [PATCH v2 2/3] pinctrl: sh-pfc: Rename PINCTRL_PFC_R8A7796 to PINCTRL_PFC_R8A77960 Geert Uytterhoeven
2019-10-25  2:46   ` Yoshihiro Shimoda
2019-10-23 12:29 ` [PATCH v2 3/3] pinctrl: sh-pfc: r8a7796: Add R8A77961 PFC 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=20191023122955.12420-1-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=devicetree@vger.kernel.org \
    --cc=erosca@de.adit-jv.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@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).