linux-renesas-soc.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: Ulrich Hecht <uli+renesas@fpond.eu>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>,
	linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/4] pinctrl: sh-pfc: rcar-gen3: Deduplicate remaining VIN pin definitions
Date: Fri, 11 Jan 2019 13:27:01 +0100	[thread overview]
Message-ID: <20190111122705.32365-1-geert+renesas@glider.be> (raw)

	Hi,

As of commit 50f3f2d73e3426ba ("pinctrl: sh-pfc: Reduce kernel size for
narrow VIN channels"), the infrastructure is available to avoid
duplication of pin definitions for narrow Video IN (VIN) channels.
Make use of his to deduplicate the remaining VIN pin definitions on
R-Car Gen3 SoCS.

This is similar to what was done before for the wide VIN channels e.g.
commit 9942a5b52990b8d5 ("pinctrl: sh-pfc: r8a7795: Deduplicate VIN4 pin
definitions").

This reduces kernel size for an R-Car Gen3 kernel by almost 1 KiB.

I plan to queue these in sh-pfc-for-v5.1.

Thanks!

Geert Uytterhoeven (4):
  pinctrl: sh-pfc: r8a7795: Deduplicate VIN5 pin definitions
  pinctrl: sh-pfc: r8a7796: Deduplicate VIN5 pin definitions
  pinctrl: sh-pfc: r8a77970: Deduplicate VIN[01] pin definitions
  pinctrl: sh-pfc: r8a77980: Deduplicate VIN1 pin definitions

 drivers/pinctrl/sh-pfc/pfc-r8a7795.c  |  90 ++++++------------
 drivers/pinctrl/sh-pfc/pfc-r8a7796.c  |  90 ++++++------------
 drivers/pinctrl/sh-pfc/pfc-r8a77970.c | 128 +++++++++-----------------
 drivers/pinctrl/sh-pfc/pfc-r8a77980.c |  64 +++++--------
 4 files changed, 115 insertions(+), 257 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-01-11 12:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 12:27 Geert Uytterhoeven [this message]
2019-01-11 12:27 ` [PATCH 1/4] pinctrl: sh-pfc: r8a7795: Deduplicate VIN5 pin definitions Geert Uytterhoeven
2019-01-11 12:27 ` [PATCH 2/4] pinctrl: sh-pfc: r8a7796: " Geert Uytterhoeven
2019-01-11 12:27 ` [PATCH 3/4] pinctrl: sh-pfc: r8a77970: Deduplicate VIN[01] " Geert Uytterhoeven
2019-01-11 12:27 ` [PATCH 4/4] pinctrl: sh-pfc: r8a77980: Deduplicate VIN1 " Geert Uytterhoeven
2019-01-11 12:45 ` [PATCH 0/4] pinctrl: sh-pfc: rcar-gen3: Deduplicate remaining VIN " Jacopo Mondi
2019-01-11 14:08 ` Simon Horman
2019-01-14 14:39 ` Niklas Söderlund

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=20190111122705.32365-1-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=uli+renesas@fpond.eu \
    /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).