public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Cc: linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
	koji.matsuoka.xm@renesas.com, linux-gpio@vger.kernel.org,
	horms@verge.net.au, geert@glider.be,
	laurent.pinchart@ideasonboard.com,
	Magnus Damm <magnus.damm@gmail.com>
Subject: [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support
Date: Tue, 17 Nov 2015 12:18:32 +0900	[thread overview]
Message-ID: <20151117031832.24924.60685.sendpatchset@little-apple> (raw)

pinctrl: sh-pfc: r8a7794: DU support

[PATCH 01/04] pinctrl: sh-pfc: r8a7794: Add DU pin groups
[PATCH 02/04] pinctrl: sh-pfc: r8a7794: Separate DU CDE and DISP
[PATCH 03/04] pinctrl: sh-pfc: r8a7794: Add missing dot clock signals
[PATCH 04/04] pinctrl: sh-pfc: r8a7794: Break out ODDF from sync

These patches take the r8a7794 PFC DU support code from the BSP
and reworks it to fit the r8a7794 ALT board. Tested with the ALT
VGA port - by default PFC is not used however enabling PFC using
an incremental (yet to be posted) patch works well.

It is worth noting that patch 2-4 modifies the pin groups. This
means that the upstream DT ABI for PFC DU will differ compared
to the unreviewed BSP code.

In general it is not considered good practice to change the pin
groups and break compatibility since they are part of the DT ABI.

For this particular case upstream never have had PFC DU support
for r8a7794, so treating the BSP bindings as experimental and
migrate away seems reasonable.

Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
---

 Written against v4.4-rc1

 drivers/pinctrl/sh-pfc/pfc-r8a7794.c |  282 ++++++++++++++++++++++++++++++----
 1 file changed, 252 insertions(+), 30 deletions(-)

             reply	other threads:[~2015-11-17  3:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  3:18 Magnus Damm [this message]
2015-11-17  3:18 ` [PATCH 01/04] pinctrl: sh-pfc: r8a7794: Add DU pin groups Magnus Damm
2015-11-29 21:25   ` Linus Walleij
2015-11-30  8:53     ` Geert Uytterhoeven
2015-11-17  3:18 ` [PATCH 02/04] pinctrl: sh-pfc: r8a7794: Separate DU CDE and DISP Magnus Damm
2015-11-17  3:19 ` [PATCH 03/04] pinctrl: sh-pfc: r8a7794: Add missing dot clock signals Magnus Damm
2015-12-21 22:01   ` Sergei Shtylyov
2015-11-17  3:19 ` [PATCH 04/04] pinctrl: sh-pfc: r8a7794: Break out ODDF from sync Magnus Damm
2015-11-20  2:46 ` [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support Laurent Pinchart
2015-11-20  7:16   ` Magnus Damm
2015-11-20 14:53     ` Laurent Pinchart
2015-11-25  0:16   ` Simon Horman

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=20151117031832.24924.60685.sendpatchset@little-apple \
    --to=magnus.damm@gmail.com \
    --cc=geert@glider.be \
    --cc=horms@verge.net.au \
    --cc=koji.matsuoka.xm@renesas.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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