Hi Sergei, On Wed, Feb 1, 2017 at 8:40 PM, Sergei Shtylyov <sergei.shtylyov@xxxxxxxxxxxxxxxxxx> wrote: > 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@xxxxxxxxxxxxxxxxxx> >>>> >>>> --- >>>> 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. Perhaps I'm misunderstanding, but if you require a DTS patch to be merged before a driver change then doesn't this mean that older DTBs will stop working with newer kernels and the user is forced to update the DTB to avoid breakage? It would be nice if older DTBs could keep on working as before and the DU driver modification would work both with connected VSPs and also keep on working as before in case the VSP connection is not present in DT. Cheers, / magnus -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
