From mboxrd@z Thu Jan 1 00:00:00 1970 From: david.lanzendoerfer@o2s.ch (David =?iso-8859-1?Q?Lanzend=F6rfer?=) Date: Thu, 16 May 2013 21:50:49 +0200 Subject: Naming convention DSI + device tree In-Reply-To: <519522C1.5010107@wwwdotorg.org> References: <20130514181745.GA2762@mail.o2s.ch> <51940C22.4050802@wwwdotorg.org> <20130516071537.GA13573@mail.o2s.ch> <519522C1.5010107@wwwdotorg.org> Message-ID: <20130516195049.GA17092@mail.o2s.ch> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org > 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: