All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
	linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
	Simon Horman <horms@verge.net.au>,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>
Subject: [PATCH 0/4] Improve pinctrl support for the RZ/G1C
Date: Mon,  8 Oct 2018 10:30:15 +0100	[thread overview]
Message-ID: <1538991019-18577-1-git-send-email-fabrizio.castro@bp.renesas.com> (raw)

Dear All,

this series adds support for I2C[0123], DU1, VIN[01], and QSPI1
to the pinctrl driver of the RZ/G1C (a.k.a. R8A77470).

This series applies on top of next-20181005, and depends on:
https://patchwork.kernel.org/patch/10630259/

Thanks,
Fab

Fabrizio Castro (4):
  pinctrl: sh-pfc: r8a77470: Add remaining I2C pin groups
  pinctrl: sh-pfc: r8a77470: Add DU1 pin groups
  pinctrl: sh-pfc: r8a77470: Add VIN pin groups
  pinctrl: sh-pfc: r8a77470: Add QSPI1 pin groups

 drivers/pinctrl/sh-pfc/pfc-r8a77470.c | 516 ++++++++++++++++++++++++++++++++++
 1 file changed, 516 insertions(+)

-- 
2.7.4

             reply	other threads:[~2018-10-08 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  9:30 Fabrizio Castro [this message]
2018-10-08  9:30 ` [PATCH 1/4] pinctrl: sh-pfc: r8a77470: Add remaining I2C pin groups Fabrizio Castro
2018-10-09 12:08   ` Simon Horman
2018-10-10  7:57   ` Geert Uytterhoeven
2018-10-08  9:30 ` [PATCH 2/4] pinctrl: sh-pfc: r8a77470: Add DU1 " Fabrizio Castro
2018-10-09 12:14   ` Simon Horman
2018-10-10  8:01   ` Geert Uytterhoeven
2018-10-08  9:30 ` [PATCH 3/4] pinctrl: sh-pfc: r8a77470: Add VIN " Fabrizio Castro
2018-10-09 12:23   ` Simon Horman
2018-10-10  8:09   ` Geert Uytterhoeven
2018-10-08  9:30 ` [PATCH 4/4] pinctrl: sh-pfc: r8a77470: Add QSPI1 " Fabrizio Castro
2018-10-09 12:27   ` Simon Horman
2018-10-10  8:17   ` 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=1538991019-18577-1-git-send-email-fabrizio.castro@bp.renesas.com \
    --to=fabrizio.castro@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --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 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.