From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Philipp Zabel <philipp.zabel@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2] video: fbdev: add Marvell PXA framebuffer binding
Date: Tue, 06 Oct 2015 19:13:25 +0000 [thread overview]
Message-ID: <8737xnbyju.fsf@belgarion.home> (raw)
In-Reply-To: <CA+gwMcciuonC5Ektt3wdUcp7RW3E+caCuktYrhcYSqTrnVng9Q@mail.gmail.com> (Philipp Zabel's message of "Tue, 6 Oct 2015 08:58:08 +0200")
Philipp Zabel <philipp.zabel@gmail.com> writes:
> On Sun, Oct 4, 2015 at 12:31 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
>> + lcd-controller@40500000 {
>> + compatible = "marvell,pxa2xx-lcdc";
>> + reg = <0x44000000 0x10000>;
>> + interrupts = <17>;
>> + clocks = <&clks CLK_LCD>;
>> + interrupts = <23>;
>
> The interrupt line is duplicated in the example.
Indeed, I'll fix that.
>
>> + status = "okay";
>> +
>> + port {
>> + lcdc_out: endpoint {
>> + remote-endpoint = <&panel_in>;
>> + bus-width = <16>;
>> + };
>> + };
>> + };
>> +
>> +PXA LCDC Display
>> +----------------
>> +Required properties (as per of_videomode_helper):
>> + - lcd-type: either "mono-stn", "mono-dstn", "color-stn", "color-dstn",
>> + "color-tft", "smart-panel"
>
> Would it make sense to make this property optional and have the
> default be "color-tft"? That is probably the most common one by far.
Yes, sure, let's do it that way for v3.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-10-06 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 10:31 [PATCH v2] video: fbdev: add Marvell PXA framebuffer binding Robert Jarzmik
[not found] ` <1443954683-13126-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2015-10-06 6:58 ` Philipp Zabel
2015-10-06 19:13 ` Robert Jarzmik [this message]
2015-10-06 13:30 ` Rob Herring
2015-10-06 19:32 ` Robert Jarzmik
[not found] ` <87y4ffaj3m.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2015-10-08 6:49 ` Philipp Zabel
2015-10-08 13:30 ` Rob Herring
2015-10-08 19:15 ` Robert Jarzmik
2015-10-09 0:46 ` Rob Herring
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=8737xnbyju.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=philipp.zabel@gmail.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.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).