public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "linux-media" <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL FOR v3.6] Add adv7604/ad9389b drivers
Date: Mon, 23 Jul 2012 14:36:35 +0200	[thread overview]
Message-ID: <201207231436.35962.hverkuil@xs4all.nl> (raw)
In-Reply-To: <2229729.zs2QQjUUOH@avalon>

On Mon July 23 2012 14:25:38 Laurent Pinchart wrote:
> Hi Hans,
> 
> On Monday 23 July 2012 13:36:15 Hans Verkuil wrote:
> > Hi all!
> > 
> > There haven't been any comments since either RFCv1 or RFCv2.
> > 
> > (http://www.spinics.net/lists/linux-media/msg48529.html and
> > http://www.spinics.net/lists/linux-media/msg50413.html)
> > 
> > So I'm making this pull request now.
> > 
> > The only changes since RFCv2 are some documentation fixes:
> > 
> > - Add a note that the SUBDEV_G/S_EDID ioctls are experimental
> > - Add the proper revision/experimental references.
> > - Update the spec version to 3.6.
> 
> Jumping a bit late on this. Wouldn't it be good to submit the RFCs to the dri-
> devel mailing list before pushing them upstream ? They have been dealing with 
> EDID for ages and might offer good advices.

I've looked at DRM as well, but there is really nothing to share. This API is for
embedded systems: it does *not* parse the EDID, it just transports it from kernel
to userspace and vice versa.

The main difference is that DRM attempts to load all blocks from the EDID, whereas
this API allows you to load blocks on demand (actually, drivers can still decide
to load all blocks initially, but that's an implementation detail). This is more
efficient given the slow i2c bus.

Regards,

	Hans

  reply	other threads:[~2012-07-23 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23 11:36 [GIT PULL FOR v3.6] Add adv7604/ad9389b drivers Hans Verkuil
2012-07-23 12:25 ` Laurent Pinchart
2012-07-23 12:36   ` Hans Verkuil [this message]
2012-07-23 12:38     ` Laurent Pinchart
2012-08-09 22:06 ` Mauro Carvalho Chehab
2012-08-10  6:35   ` Hans Verkuil

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=201207231436.35962.hverkuil@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.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