linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: imx6: add ZII RDU2 boards
Date: Wed, 08 Mar 2017 18:32:37 +0100	[thread overview]
Message-ID: <1488994357.9636.3.camel@pengutronix.de> (raw)
In-Reply-To: <20170308171445.GG19934@x250>

Am Mittwoch, den 08.03.2017, 18:14 +0100 schrieb Shawn Guo:
> On Fri, Feb 10, 2017 at 04:39:28PM +0100, Lucas Stach wrote:
> > This adds support for the Zodiac Inflight Innovations RDU2 board,
> > which has both a Quad and a QuadPlus variant.
> > 
> > The board supports different panels, with the bootloader patching
> > in the correct compatible, depending on the hardware configuration.
> > 
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > Tested-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
> 
[...]
>   +	panel {
> > +		power-supply = <&reg_3p3v_display>;
> > +		status = "disabled";
> 
> Why does it get disabled?

The LVDS panel node as well as several other display related nodes are
disabled by default, as this is a generic DT with multiple possible
display configurations. The bootloader (Barebox) knows about the
specific connected display and will enable the correct nodes, as well
as patch in the correct compatible for the panel.

> 
> > +
> > +		port {
> > +			panel_in: endpoint {
> > +				remote-endpoint = <&lvds0_out>;
> > +			};
> > +		};
> > +	};
[...]

Regards,
Lucas

      reply	other threads:[~2017-03-08 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 15:39 [PATCH v2] ARM: imx6: add ZII RDU2 boards Lucas Stach
2017-02-11 18:37 ` Chris Healy
2017-03-08 17:14 ` Shawn Guo
2017-03-08 17:32   ` Lucas Stach [this message]

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=1488994357.9636.3.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).