On Sat, Jul 29, 2017 at 11:05:50PM +0300, Laurent Pinchart wrote:
> Hi Simon,
>
> On Monday 17 Jul 2017 10:07:33 Geert Uytterhoeven wrote:
> > On Thu, Jul 13, 2017 at 2:17 PM, Laurent Pinchart wrote:
> > > The DU LVDS output is on port 3 on R8A7795 but on port 2 on R8A7796. The
> > > lvds_connecto
Hi Simon,
On Monday 17 Jul 2017 10:07:33 Geert Uytterhoeven wrote:
> On Thu, Jul 13, 2017 at 2:17 PM, Laurent Pinchart wrote:
> > The DU LVDS output is on port 3 on R8A7795 but on port 2 on R8A7796. The
> > lvds_connector label thus can't be defined in salvator-common.dtsi,
> > common to the two S
On Thu, Jul 13, 2017 at 2:17 PM, Laurent Pinchart
wrote:
> The DU LVDS output is on port 3 on R8A7795 but on port 2 on R8A7796. The
> lvds_connector label thus can't be defined in salvator-common.dtsi,
> common to the two SoCs.
>
> The lvds_connector label is meant for convience to be referenced f
The DU LVDS output is on port 3 on R8A7795 but on port 2 on R8A7796. The
lvds_connector label thus can't be defined in salvator-common.dtsi,
common to the two SoCs.
The lvds_connector label is meant for convience to be referenced from
panel device tree files, such as r8a77xx-aa104xd12-panel.dtsi o
