From: Tony Prisk <linux@prisktech.co.nz>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/6] video: fb: vt8500: Convert framebuffer drivers to standardized binding
Date: Thu, 28 Mar 2013 05:04:41 +0000 [thread overview]
Message-ID: <1364447081.15039.5.camel@gitbox> (raw)
In-Reply-To: <5152D39F.1090104@ti.com>
On Wed, 2013-03-27 at 13:10 +0200, Tomi Valkeinen wrote:
> Hi,
>
> On 2013-03-27 10:47, Tony Prisk wrote:
> > Now that a display timing binding is available, convert our almost identical
> > binding to use the standard binding.
> >
> > This patch converts the vt8500 and wm8505 framebuffer drivers and
> > associated dts/dtsi files to use the standard binding as defined in
> > bindings/video/display-timing.txt.
> >
> > There are two side-effects of making this conversion:
> >
> > 1) The fb node should now be in the board file, rather than the soc file as
> > the display-timing node is a child of the fb node.
> >
> > 2) We still require a bits per pixel property to initialize the framebuffer
> > for the different lcd panels. Rather than including this as part of the
> > display timing, it is moved into the framebuffer node.
> >
> > I have also taken the opportunity to alphabetise the includes of each
> > driver to avoid double-ups.
>
> I don't think this is correct. I don't have that much experience with
> DT, but I think you should have, for example:
>
> wm8850.dtsi:
>
> fb: fb@d8051700 {
> compatible = "wm,wm8505-fb";
> reg = <0xd8051700 0x200>;
> };
>
> wm8850-w70v2.dts:
>
> &fb {
> bits-per-pixel = <16>;
>
> display-timings {
> native-mode = <&timing0>;
> timing0: 800x480 {
> clock-frequency = <0>;
> ...
> };
> };
> };
>
> So, the core fb part should be in the SoC's file, as it's part of the
> SoC. And the stuff that tells what kind of display is attached is in the
> board dts file.
>
> Also, just a word of warning, I think the videomode series I've sent for
> review will cause some breakage with this series if the videomode series
> is accepted. Nothing difficult to fix, though, but we'll need some extra
> management to avoid compilation failures.
>
> Tomi
>
>
Thanks for the feedback and the heads-up.
I believe you are correct about the DT info - it looks right when
described the way you did, so I have changed it.
If there is no other feedback, I will post a version 2 after Easter.
Regards
Tony P
prev parent reply other threads:[~2013-03-28 5:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 8:46 [PATCH 0/6] fb: vt8500: patches for 3.10 Tony Prisk
2013-03-27 8:46 ` [PATCH 1/6] video: vt8500: Make wmt_ge_rops optional Tony Prisk
2013-03-27 8:46 ` [PATCH 2/6] video: vt8500: Remove unused platform_data/video-vt8500lcdfb.h Tony Prisk
2013-03-27 8:46 ` [PATCH 3/6] video: vt8500: Correct descriptions in video/Kconfig Tony Prisk
2013-03-27 8:46 ` [PATCH 4/6] drivers/video/wm8505fb.c: use devm_ functions Tony Prisk
2013-03-27 8:47 ` [PATCH 5/6] video: vt8500: Adjust contrast in wm8505 framebuffer driver Tony Prisk
2013-03-27 8:47 ` [PATCH 6/6] video: fb: vt8500: Convert framebuffer drivers to standardized binding Tony Prisk
2013-03-27 11:10 ` Tomi Valkeinen
2013-03-28 5:04 ` Tony Prisk [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=1364447081.15039.5.camel@gitbox \
--to=linux@prisktech.co.nz \
--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).