linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL] pinctrl: renesas: Updates for v5.17
Date: Fri,  3 Dec 2021 13:33:40 +0100	[thread overview]
Message-ID: <cover.1638534672.git.geert+renesas@glider.be> (raw)

	Hi Linus,

The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:

  Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git tags/renesas-pinctrl-for-v5.17-tag1

for you to fetch changes up to 7c50a407b8687ae3589c740d2347d9ae73887889:

  pinctrl: renesas: Remove unneeded locking around sh_pfc_read() calls (2021-11-19 10:55:21 +0100)

----------------------------------------------------------------
pinctrl: renesas: Updates for v5.17

  - Add generic support for output impedance,
  - Add drive strength and output impedance support for the RZ/G2L SoC,
  - Miscellaneous fixes and improvements.

Thanks for pulling!
----------------------------------------------------------------
Geert Uytterhoeven (2):
      pinctrl: renesas: rza1: Fix kerneldoc function names
      pinctrl: renesas: Remove unneeded locking around sh_pfc_read() calls

Lad Prabhakar (8):
      dt-bindings: pincfg-node: Add "output-impedance-ohms" property
      pinctrl: pinconf-generic: Add support for "output-impedance-ohms" to be extracted from DT files
      dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Add output-impedance-ohms property
      pinctrl: renesas: rzg2l: Rename RZG2L_SINGLE_PIN_GET_PORT macro
      pinctrl: renesas: rzg2l: Add helper functions to read/write pin config
      pinctrl: renesas: rzg2l: Add support to get/set pin config for GPIO port pins
      pinctrl: renesas: rzg2l: Rename PIN_CFG_* macros to match HW manual
      pinctrl: renesas: rzg2l: Add support to get/set drive-strength and output-impedance-ohms

 .../devicetree/bindings/pinctrl/pincfg-node.yaml   |   3 +
 .../bindings/pinctrl/renesas,rzg2l-pinctrl.yaml    |   2 +
 drivers/pinctrl/pinconf-generic.c                  |   2 +
 drivers/pinctrl/renesas/pinctrl-rza1.c             |   6 +-
 drivers/pinctrl/renesas/pinctrl-rzg2l.c            | 310 ++++++++++++++-------
 drivers/pinctrl/renesas/pinctrl.c                  |   9 +-
 include/linux/pinctrl/pinconf-generic.h            |   3 +
 7 files changed, 224 insertions(+), 111 deletions(-)

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:[~2021-12-03 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 12:33 Geert Uytterhoeven [this message]
2021-12-05  0:37 ` [GIT PULL] pinctrl: renesas: Updates for v5.17 Linus Walleij

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=cover.1638534672.git.geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --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).