linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: "Simon Horman [Horms]" <horms@verge.net.au>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: r8a7791: link DU to VSPDs
Date: Wed, 1 Feb 2017 14:40:52 +0300	[thread overview]
Message-ID: <4bf0b27c-9641-391d-fc05-8cdc20ce4ec3@cogentembedded.com> (raw)
In-Reply-To: <CANqRtoSQTa0fHJSwAHbN3hXSZ=m1kuR2GsUWE5ojN5AN-9i6Bw@mail.gmail.com>

On 2/1/2017 2:13 PM, Magnus Damm wrote:

>>> Add the "vsps" property to the DU device node in order to link this node
>>> to
>>> the VSPD nodes.
>>>
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>
>>> ---
>>> Changes in version 2:
>>> - rebased the patch.
>>>
>>> This patch is against the 'renesas-devel-20170125-v4.10-rc5' of Simon
>>> Horman's
>>> 'renesas.git' repo.  It's  only meaningful if the DRM driver patches I've
>>> just
>>> posted are applied.
>>
>>
>>    Forgot to note that without this patch the DU driver fails to link to
>> VSPD and probe correctly, so there's no video signal. So it makes sense to
>> apply before the DU driver patch (once it's ACKed for merge)...
>
> Doesn't that translate to breaking the DT ABI? Is there someway we can
> avoid doing that?

    It doesn't -- if this patch is merged ahead of the DU patches.

> Thanks,
>
> / magnus

MBR, Sergei

  reply	other threads:[~2017-02-01 11:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 21:50 [PATCH 0/2] R8A7792 clock fixes Sergei Shtylyov
2016-07-11 21:51 ` [PATCH 1/2] ARM: dts: r8a7792: add PLL1 divided by 2 clock Sergei Shtylyov
2016-07-13  1:20   ` Geert Uytterhoeven
2016-07-11 21:52 ` [PATCH 2/2] ARM: dts: r8a7792: remove ADSP clock Sergei Shtylyov
2016-07-13  1:23   ` Geert Uytterhoeven
2016-07-12 20:30 ` [PATCH 0/2] R8A7792 clock fixes Sergei Shtylyov
2016-07-15  4:25   ` Simon Horman
2016-10-29 21:31 ` [PATCH] ARM: dts: r8a7794: remove Z clock Sergei Shtylyov
2016-11-01  9:21   ` Simon Horman
2016-11-02  8:50   ` Geert Uytterhoeven
2016-12-14 22:07 ` [PATCH] ARM: dts: r8a7791: link DU to VSPDs Sergei Shtylyov
2016-12-15  9:59   ` Magnus Damm
2017-01-03  9:24   ` Laurent Pinchart
2016-12-28 21:35 ` [PATCH] ARM: dts: r8a7794: link DU to VSPD Sergei Shtylyov
2017-01-03  9:24   ` Laurent Pinchart
2017-01-25 21:42 ` [PATCH v2] ARM: dts: r8a7791: link DU to VSPDs Sergei Shtylyov
2017-01-26 18:42   ` Sergei Shtylyov
2017-02-01 11:13     ` Magnus Damm
2017-02-01 11:40       ` Sergei Shtylyov [this message]
2017-02-01 12:01         ` Magnus Damm
2017-02-02 13:02           ` 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=4bf0b27c-9641-391d-fc05-8cdc20ce4ec3@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.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=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).