From: "David Lanzendörfer" <david.lanzendoerfer@o2s.ch>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Naming convention DSI + device tree
Date: Thu, 16 May 2013 21:50:49 +0200 [thread overview]
Message-ID: <20130516195049.GA17092@mail.o2s.ch> (raw)
In-Reply-To: <519522C1.5010107@wwwdotorg.org>
[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]
> No, we haven't yet posted DSI support upstream.
Ok.
> Honestly, I'm not sure. I assume (and it is just an assumption) that
> if you look at the CDF patches, you should find some examples of panel
> drivers that use it, although perhaps there aren't any yet...
Ok. If there's an API already flying around somewhere, which will
be posted to upstream at some point of time, and won't change drastically
anymore I can work with it.
> No. That branch of mine is basd on linux-next, so whatever is in
> linux-next is in my branch, and I certainly haven't applied the CDF
> locally.
Ok.
> I believe the CDF has been posted to various mailing lists a few
> times, but it isn't checked in yet since there isn't a final version.
> I CC'd Alex; he might know the status better than me.
Ok. Thank you very much!
The best would be a patchset for CDF against linux-next (which will most
likely be the case anyway) in order to track the changes and post my own
changes upstream as soon as CDF is in next.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2013-05-16 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130514181745.GA2762@mail.o2s.ch>
[not found] ` <51940C22.4050802@wwwdotorg.org>
[not found] ` <20130516071537.GA13573@mail.o2s.ch>
[not found] ` <20130516071537.GA13573-cEukqlNQfh4fv37vnLkPlQ@public.gmane.org>
2013-05-16 18:17 ` Naming convention DSI + device tree Stephen Warren
2013-05-16 19:50 ` David Lanzendörfer [this message]
[not found] ` <519522C1.5010107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-17 5:36 ` Alex Courbot
[not found] ` <5195C1E2.4020009-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-17 19:39 ` Stephen Warren
2013-05-22 6:24 ` Mark Zhang
2013-05-23 9:55 ` Alex Courbot
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=20130516195049.GA17092@mail.o2s.ch \
--to=david.lanzendoerfer@o2s.ch \
--cc=acourbot@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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