From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <robh+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] Add R8A77980/Condor/V3HSK LVDS/HDMI support
Date: Fri, 08 Jun 2018 17:27:19 +0300 [thread overview]
Message-ID: <4069170.tduNOXLj45@avalon> (raw)
In-Reply-To: <390fabf0-4caf-1600-3780-1893207d94f7@cogentembedded.com>
Hi Sergei,
On Thursday, 7 June 2018 23:17:03 EEST Sergei Shtylyov wrote:
> Hello!
>
> Here's the set of 5 patches against Simon Horman's 'renesas.git' repo's
> 'renesas-devel-20180604-v4.17' tag. We're adding the R8A77980 FCPVD/VSPD/
> DU/LVDS device nodes and then describing the LVDS decoder and HDMI encoder
> connected to the LVDS output. These patches depend on the Thine THC63LVD1024
> driver and the R8A77980 LVDS support patch in order to work, and R8A77980
> GPIO DT patches in order to apply/compile...
>
> [1/5] arm64: dts: renesas: r8a77980: add FCPVD support
> [2/5] arm64: dts: renesas: r8a77980: add VSPD support
> [3/5] arm64: dts: renesas: r8a77980: add DU support
> [4/5] arm64: dts: renesas: r8a77980: add LVDS support
Based on the recent request of the ARM SoC maintainers to avoid a plethora of
small patches, I think you can squash 1/5 to 4/5 all together.
> [5/5] arm64: dts: renesas: condor/v3hsk: add DU/LVDS/HDMI support
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-06-08 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 20:17 [PATCH v2 0/5] Add R8A77980/Condor/V3HSK LVDS/HDMI support Sergei Shtylyov
2018-06-07 20:19 ` [PATCH v2 1/5] arm64: dts: renesas: r8a77980: add FCPVD support Sergei Shtylyov
2018-06-08 8:56 ` Simon Horman
2018-06-08 14:22 ` Laurent Pinchart
2018-06-07 20:20 ` [PATCH v2 2/5] arm64: dts: renesas: r8a77980: add VSPD support Sergei Shtylyov
2018-06-08 13:54 ` Simon Horman
2018-06-08 14:01 ` Laurent Pinchart
2018-06-07 20:21 ` [PATCH v2 3/5] arm64: dts: renesas: r8a77980: add DU support Sergei Shtylyov
2018-06-08 14:21 ` Laurent Pinchart
2018-06-07 20:23 ` [PATCH v2 4/5] arm64: dts: renesas: r8a77980: add LVDS support Sergei Shtylyov
2018-06-08 14:24 ` Laurent Pinchart
2018-06-07 20:24 ` [PATCH v2 5/5] arm64: dts: renesas: condor/v3hsk: add DU/LVDS/HDMI support Sergei Shtylyov
2018-06-08 8:21 ` [PATCH v2 0/5] Add R8A77980/Condor/V3HSK LVDS/HDMI support Simon Horman
2018-06-08 8:51 ` Sergei Shtylyov
2018-06-08 14:27 ` Laurent Pinchart [this message]
2018-06-11 8:15 ` Simon Horman
2018-06-13 19:07 ` Sergei Shtylyov
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=4069170.tduNOXLj45@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=will.deacon@arm.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).