public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "David Lanzendörfer"
	<david.lanzendoerfer-Z7Kmv9EsliU@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Laurent Pinchart"
	<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
Subject: Re: Naming convention DSI + device tree
Date: Fri, 17 May 2013 14:36:34 +0900	[thread overview]
Message-ID: <5195C1E2.4020009@nvidia.com> (raw)
In-Reply-To: <519522C1.5010107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 05/17/2013 03:17 AM, Stephen Warren wrote:
>> Is this upcoming CDF included within your "linux-next_common"
>> branch?
>
> 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.
>
> 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.

Current version is RFC v2 - I know Laurent is working on a v3, but it is 
taking some time. It will probably differ considerably from v2, so be 
warned if you use it.

Still, if you want to play around with the CDF, you can have a look at 
the tegra-cdf branch of my github repo: 
https://github.com/Gnurou/linux/commits/tegra-cdf

It was kind of old so I rebased it on top of 3.10rc1. It includes the 
CDF v2 patch, adds CDF support to the tegra-drm driver, and also 
implements a driver for the Tegra 2-based Ventana panel. It's pretty 
straightforward to read so I guess you can use that as a guide.

I checked whether the rebase worked and it does - you just need to 
enable host1x/tegradrm support on top of the default settings (Stephen, 
why aren't these enabled by default?)

So long story short, CDF works well and is small enough to be easy to 
maintain out-of-tree. A proper panel framework is desperately needed in 
the kernel, so I hope it will move forward soon.

Hope this helps,
Alex.

  parent reply	other threads:[~2013-05-17  5:36 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
     [not found]         ` <519522C1.5010107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-17  5:36           ` Alex Courbot [this message]
     [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=5195C1E2.4020009@nvidia.com \
    --to=acourbot-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=david.lanzendoerfer-Z7Kmv9EsliU@public.gmane.org \
    --cc=laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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