[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Device-drivers-devel] [RFCv1 PATCH 0/7] Add adv7604/ad9389b drivers



On Fri July 6 2012 10:10:15 Lars-Peter Clausen wrote:
> On 07/05/2012 04:26 PM, Hans Verkuil wrote:
> > Hi all,
> > 
> > This RFC patch series builds on an earlier RFC patch series (posted only to
> > linux-media) that adds support for DVI/HDMI/DP connectors to the V4L2 API.
> > 
> > This earlier patch series is here:
> > 
> > 	http://www.spinics.net/lists/linux-media/msg48529.html
> > 
> > The first 3 patches are effectively unchanged compared to that patch series,
> > patch 4 adds support for the newly defined controls to the V4L2 control framework
> > and patch 5 adds helper functions to v4l2-common.c to help in detecting VESA
> > CVT and GTF formats.
> > 
> > Finally, two Analog Devices drivers are added to actually use this new API.
> > The adv7604 is an HDMI/DVI receiver and the ad9389b is an HDMI transmitter.
> > 
> > Another tree of mine also contains preliminary drivers for the adv7842
> > and adv7511:
> 
> Hm, ok that's interesting I do have a DRM driver for the adv7511:
> https://github.com/lclausen-adi/linux-2.6/blob/adv7511_zynq/drivers/gpu/drm/i2c/adv7511_core.c
> 
> I wonder if it is possible to share some code on this.

That will be an interesting exercise. The V4L and DRM subsystems are trying to
improve their cooperation, but we are not yet at the stage that you can easily
share video encoders. This might be a good starting point, though.

> > 
> > 	http://git.linuxtv.org/hverkuil/media_tree.git/shortlog/refs/heads/hdmi
> > 
> > However, I want to start with adv7604 and ad9389b since those have had the most
> > testing.
> 
> I've also have some code which adds adv7611 support to your adv7604 driver.

Let's try and get this driver in first, before we start adding patches other
than fixes. The main purpose is to get the new API elements merged in the
kernel, after that the drivers can easily be expanded and improved (which is
so much easier once they are in the kernel).

Regards,

	Hans

> 
> > 
> > As the commit message of says these drivers do not implement the full
> > functionality of these devices, but that can be added later, either
> > by Cisco or by others.
> > 
> > A lot of work has been put into the V4L2 subsystem to reach this point,
> > particularly the control framework, the VIDIOC_G/S/ENUM/QUERY_DV_TIMINGS
> > ioctls, and the V4L2 event mechanism. So I'm very pleased to be able to finally
> > post this code.
> > 
> > Comments are welcome!
> > 
> > Regards,
> > 
> > 	Hans Verkuil
> > 
> > _______________________________________________
> > Device-drivers-devel mailing list
> > Device-drivers-devel@xxxxxxxxxxxxxxxxxxxx
> > https://blackfin.uclinux.org/mailman/listinfo/device-drivers-devel
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Linux Input]     [Video for Linux]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Photos]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Devices]     [Yosemite Backpacking]

Add to Google Powered by Linux