From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: renesas: salvator-x: Configure pins for the DU RGB output
Date: Thu, 18 Aug 2016 09:12:07 +0200 [thread overview]
Message-ID: <20160818071204.GA3961@verge.net.au> (raw)
In-Reply-To: <3167228.fHu3sBnt6u@avalon>
On Wed, Aug 17, 2016 at 12:17:26PM +0300, Laurent Pinchart wrote:
> On Wednesday 17 Aug 2016 11:00:38 Geert Uytterhoeven wrote:
> > On Wed, Aug 17, 2016 at 9:13 AM, Simon Horman <horms@verge.net.au> wrote:
> > > On Fri, Aug 12, 2016 at 12:18:55PM +0300, Laurent Pinchart wrote:
> > >> Signed-off-by: Laurent Pinchart
> > >> <laurent.pinchart+renesas@ideasonboard.com>
> > >> ---
> > >>
> > >> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 7 +++++++
> > >> 1 file changed, 7 insertions(+)
> > >>
> > >> This patch depends on "[PATCH] pinctrl: sh-pfc: r8a7795: Add DU support"
> > >> posted a few minutes ago to the linux-renesas-soc mailing list, as well
> > >> as on the "[PATCH v2 0/4] R-Car Gen3 DU enablement on Salvator-X board"
> > >> series posted yesterday to the same list.
> > >>
> > >> As the boot loader configures the DU pins on Salvator-X we can safely
> > >> delay this patch by one kernel version to let the pinctrl dependency hit
> > >> mainling first.
> > >
> > > I'm not entirely sure it is necessary to defer this patch by a kernel
> > > release but if that is your wish then I'm happy to do so. If so
> > > please repost at the appropriate time.
> >
> > I believe applying this patch now means that the DU won't work in your
> > renesas-devel tree (unless you merge sh-pfc-for-v4.9).
> > Of course it should work in renesas-drivers.
>
> I haven't tested that, but I believe it would result in a probe failure
> as the device core won't be able to apply the request pinctrl settings.
Ok, in that case lets defer this patch as you suggested.
next prev parent reply other threads:[~2016-08-18 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 9:18 [PATCH] arm64: dts: renesas: salvator-x: Configure pins for the DU RGB output Laurent Pinchart
2016-08-16 8:24 ` Geert Uytterhoeven
2016-08-17 7:13 ` Simon Horman
2016-08-17 9:00 ` Geert Uytterhoeven
2016-08-17 9:17 ` Laurent Pinchart
2016-08-18 7:12 ` Simon Horman [this message]
2016-09-06 10:28 ` 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=20160818071204.GA3961@verge.net.au \
--to=horms@verge.net.au \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--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