From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv4 0/6] arm: Initial TI-Nspire support
Date: Fri, 31 May 2013 09:43:30 +0200 [thread overview]
Message-ID: <2266847.DGUdOCUR2h@avalon> (raw)
In-Reply-To: <1369738372.3148.7.camel@hornet>
Hi Pawel,
Sorry for the late reply, I'm currently attending LinuxCon Japan, my mail
backlog is growing.
On Tuesday 28 May 2013 11:52:52 Pawel Moll wrote:
> On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote:
> > On Monday 27 May 2013, Daniel Tang wrote:
> > > > The one remaining bit that sticks out is the clcd platform data. As I
> > > > said before, I won't require you to convert that to DT in order to
> > > > get your code merged, but I'd also really like to see that happen,
> > > > as we will also need that to get rid of auxdata on the ARM reference
> > > > platforms (integrator, versatile, realview, vexpress).
> > >
> > > How would you like me to convert the platform data to DT? AFAIK, the
> > > clcd driver isn't aware of DT so the only way is to use the AUXDATA
> > > right now.
> >
> > Linus Walleij mentioned on IRC that Pawel Moll already posted a series
> > that adds DT support for clcd:
> >
> > http://lists.freedesktop.org/archives/dri-devel/2013-April/037519.html
> >
> > The series does a few more things, but you can probbly split out the
> > parts you need and base on that.
>
> The main "issue" with the series is its dependency on Laurent Pinchart's
> Common Display Framework (or rather on the progress of its upstreaming).
> I'm planning to discuss this in details in during the Linaro Connect in
> Dublin, but generally, if it's not getting merged in the next window,
> I'll spin the series to use the standard video modes bindings instead of
> CDF. This will make me hurt on Versatile Express, but should work for
> others.
I've met with Tomi Valkeinen (TI), Alexandre Courbot (NVidia) and Tomasz Figa
(Samsung) recently, For the first time the meetings helped narrowing the
options *down*. It seems a path is slowly unfolding, and I would like to
target v3.13 for a first (possibly limited) version.
Regarding the DT bindings, Alexandre and Tomasz will look into the V4L2 DT
bindings to see whether/how they can be reused/leveraged for the CDF bindings.
In both case we need to describe a graph of connected entities, and there's
not much in the V4L2 DT bindings that is V4L2-specific in that regard.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-05-31 7:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 11:08 [RFC PATCHv4 0/6] arm: Initial TI-Nspire support Daniel Tang
2013-05-25 11:08 ` [RFC PATCHv4 1/6] arm: TI-Nspire platform code Daniel Tang
2013-05-26 20:46 ` Arnd Bergmann
2013-05-27 4:07 ` Daniel Tang
2013-05-27 6:56 ` Arnd Bergmann
[not found] ` <CAPnH9dnA22C3ZS9jgJNytnmKM_8Vfk7OxNRB1Mg03=q7KhHZBA@mail.gmail.com>
[not found] ` <201305271715.02385.arnd@arndb.de>
2013-05-29 5:14 ` Daniel Tang
2013-05-29 7:58 ` Arnd Bergmann
2013-05-25 11:08 ` [RFC PATCHv4 2/6] arm: TI-Nspire device trees Daniel Tang
2013-05-25 11:08 ` [RFC PATCHv4 3/6] clk: TI-Nspire clock drivers Daniel Tang
2013-05-31 1:16 ` Mike Turquette
2013-05-25 11:08 ` [RFC PATCHv4 4/6] clocksource: TI-Nspire timer support Daniel Tang
2013-05-27 10:53 ` Linus Walleij
2013-05-27 10:56 ` Daniel Tang
2013-05-27 12:28 ` Thomas Gleixner
2013-05-25 11:08 ` [RFC PATCHv4 5/6] input: TI-Nspire keypad support Daniel Tang
2013-05-25 11:08 ` [RFC PATCHv4 6/6] irqchip: TI-Nspire irqchip support Daniel Tang
2013-05-30 21:29 ` Grant Likely
2013-05-26 21:23 ` [RFC PATCHv4 0/6] arm: Initial TI-Nspire support Arnd Bergmann
2013-05-27 2:23 ` Daniel Tang
2013-05-27 10:31 ` Arnd Bergmann
2013-05-28 10:52 ` Pawel Moll
2013-05-31 7:43 ` Laurent Pinchart [this message]
2013-05-29 5:18 ` Daniel Tang
2013-05-29 12:46 ` Arnd Bergmann
2013-05-27 10:32 ` Arnd Bergmann
2013-05-28 10:54 ` Pawel Moll
2013-05-28 14:16 ` Linus Walleij
2013-05-28 14:21 ` Pawel Moll
2013-05-28 14:52 ` Arnd Bergmann
2013-05-28 15:10 ` Andy Shevchenko
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=2266847.DGUdOCUR2h@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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).