linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: SH-Linux <linux-sh@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Koji Matsuoka <koji.matsuoka.xm@renesas.com>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	"Simon Horman [Horms]" <horms@verge.net.au>,
	geert@glider.be
Subject: Re: [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support
Date: Fri, 20 Nov 2015 16:53:10 +0200	[thread overview]
Message-ID: <7175557.3oSik5Zhyq@avalon> (raw)
In-Reply-To: <CANqRtoTMf4TP2gcEuF4y5qdRz0fdf9-sebS=ymg+4zAGMj8dSA@mail.gmail.com>

Hi Magnus,

On Friday 20 November 2015 16:16:15 Magnus Damm wrote:
> On Fri, Nov 20, 2015 at 11:46 AM, Laurent Pinchart wrote:
> > On Tuesday 17 November 2015 12:18:32 Magnus Damm wrote:
> >> 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.
> > 
> > If we start considering DT bindings that never went upstream as stable
> > we'll have a big problem. I mean even bigger than the upstream DT
> > bindings stability problem :-)
> 
> I'm not saying that local DT hacks should be considered stable, more
> that it as usual makes sense to follow upstream first with proper DT
> review process early on.
> 
> >> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> > 
> > Wouldn't it make sense to merge the 4 patches together ?
> 
> Yeah, I guess so. My feeling is also that it would be good to verify
> HDMI on ALT before commiting to DT bindings. Right now only one DU
> channel is tested.

I agree with that.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2015-11-20 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  3:18 [PATCH 00/04] pinctrl: sh-pfc: r8a7794: DU support Magnus Damm
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 [this message]
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=7175557.3oSik5Zhyq@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert@glider.be \
    --cc=horms@verge.net.au \
    --cc=koji.matsuoka.xm@renesas.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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).