From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Simon Horman <horms@verge.net.au>
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>,
linux-renesas-soc@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/5] Add R8A77970/V3MSK LVDS/HDMI support
Date: Fri, 2 Mar 2018 13:29:56 +0300 [thread overview]
Message-ID: <4e37c0d9-b619-1b3e-01b2-8cf762efb604@cogentembedded.com> (raw)
In-Reply-To: <20180302102106.enyb2ldmylgklqom@verge.net.au>
On 3/2/2018 1:21 PM, Simon Horman wrote:
>>>>>>> Here's the set of 5 patches against Simon Horman's 'renesas.git' repo's
>>>>>>> 'renesas-devel-20180227-v4.16-rc3' tag. We're adding the R8A77970 FCPVD/VSPD/
>>>>>>> DU/LVDS device nodes and then describing the HDMI encoder connected to the LVDS
>>>>>>> output (we're omitting the LVDS decoder for now). These patches depend on
>>>>>>> the recent R8A77970 DU/LVDS rework patches by Laurent in order to work...
>>>>>>
>>>>>> Need to mention that the DU driver silently fails to probe now. I do
>>>>>> hope that this is not due to my updates. :-)
>>>>>
>>>>> Please test that theory.
>>>>
>>>> Yeah, after sucking in the recent versions of the DU/LVDS patches and uncommenting
>>>> and fixing rejects in a couple patches here, the graphical console works again. :-)
>>>
>>> Ok, but does this patchset cause a regression? If so it seems
>>
>> Sorry, somehow missed that question. No regression is possible as the display just
>> doesn't work before these patches are applied. It's just that it doesn't start to work
>> until the recent DU/LVDS driver updates are applied.
>
> Ok, but my question remains: does the display work before these patches?
No, there are no FCPVD/VSPD/DU/LVDS device nodes in R8A77970 TDs.
MBR, Sergei
next prev parent reply other threads:[~2018-03-02 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 20:06 [PATCH v2 0/5] Add R8A77970/V3MSK LVDS/HDMI support Sergei Shtylyov
2018-02-27 20:08 ` [PATCH v2 1/5] arm64: dts: renesas: r8a77970: add FCPVD support Sergei Shtylyov
2018-02-27 20:09 ` [PATCH v2 2/5] arm64: dts: renesas: r8a77970: add VSPD support Sergei Shtylyov
2018-02-27 20:10 ` [PATCH v2 3/5] arm64: dts: renesas: r8a77970: add DU support Sergei Shtylyov
2018-02-27 20:11 ` [PATCH v2 4/5] arm64: dts: renesas: r8a77970: add LVDS support Sergei Shtylyov
2018-02-27 20:12 ` [PATCH v2 5/5] arm64: dts: renesas: v3msk: add DU/LVDS/HDMI support Sergei Shtylyov
2018-02-27 20:23 ` [PATCH v2 0/5] Add R8A77970/V3MSK LVDS/HDMI support Sergei Shtylyov
2018-02-28 13:27 ` Simon Horman
2018-02-28 17:57 ` Sergei Shtylyov
2018-03-01 9:54 ` Simon Horman
2018-03-01 10:20 ` Sergei Shtylyov
2018-03-01 15:28 ` Sergei Shtylyov
2018-03-02 10:21 ` Simon Horman
2018-03-02 10:29 ` Sergei Shtylyov [this message]
2018-04-23 20:45 ` [PATCH v3] arm64: dts: renesas: v3msk: add DU/LVDS/HDMI support Sergei Shtylyov
2018-05-01 6:00 ` 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=4e37c0d9-b619-1b3e-01b2-8cf762efb604@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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=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).