public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Trilok Soni <soni.trilok@gmail.com>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: video4linux-list@redhat.com, linux-omap@vger.kernel.org,
	davinci-linux-open-source-bounces@linux.davincidsp.com
Subject: Re: [PATCH 2/2] TVP514x V4L int device driver support
Date: Sun, 23 Nov 2008 22:32:31 -0800	[thread overview]
Message-ID: <200811232232.31646.david-b@pacbell.net> (raw)
In-Reply-To: <5d5443650811232216x6c9a77a4p2945f87e1ab65a67@mail.gmail.com>

On Sunday 23 November 2008, Trilok Soni wrote:
> > 2) Please use the media/v4l2-i2c-drv.h or media/v4l2-i2c-drv-legacy.h
> > header to hide some of the i2c complexity (again, see e.g. saa7115.c).
> > The i2c API tends to change a lot (and some changes are upcoming) so

What "changes" do you mean?  Since this is not a legacy-style
driver (yay!), the upcoming changes won't affect it at all.


> > using this header will mean that i2c driver changes will be minimal in
> > the future. In addition it will ensure that this driver can be compiled
> > with older kernels as well once it is part of the v4l-dvb repository.
> 
> I don't agree with having support to compile with older kernels.

Right.  Folk wanting legacy tvp5146 and tvp5140 support could
try to use the legacy drivers from the DaVinci tree.


> Even though I2C APIs change as lot it is for good, and creating
> abstractions doesn't help as saa7xxx is family of chips where I don't
> see the case here. Once this driver is mainlined if someone does i2c
> subsystem change which breaks this driver from building then he/she
> has to make changes to all the code affecting it.

And AFAIK no such change is anticipated.  The conversion from
legacy style I2C drivers to "new style" driver-model friendly
drivers is progressing fairly well, so that legacy support can
be completely removed.


> I am not in favour of adding support to compile with older kernels.

My two cents:  I'm not in favor either.  In fact that's the
general policy for mainline drivers, and I'm surprised to hear
any maintainer suggest it be added.

- Dave

  reply	other threads:[~2008-11-24  6:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hvaibhav@ti.com>
2008-11-21 15:22 ` [PATCH 2/2] TVP514x V4L int device driver support hvaibhav
2008-11-21 16:16   ` Hans Verkuil
2008-11-21 18:12   ` Trilok Soni
2008-11-21 19:07     ` Hiremath, Vaibhav
2008-11-21 19:11     ` David Brownell
2008-11-23 22:00   ` Hans Verkuil
2008-11-23 22:04     ` Koen Kooi
2008-11-24  6:16     ` Trilok Soni
2008-11-24  6:32       ` David Brownell [this message]
2008-11-24  7:53         ` Hans Verkuil
2008-11-24  8:53           ` Hiremath, Vaibhav
2008-11-24  8:04       ` Hans Verkuil
2008-11-24  8:43         ` Trilok Soni
2008-11-24  8:59           ` Hiremath, Vaibhav
2008-11-24 10:06   ` David Brownell
2008-11-26 17:05 ` [PATCH 2/2] TVP514x Driver with Review comments fixed hvaibhav
2008-11-26 17:48   ` Hans Verkuil
2008-12-02 15:35 ` [PATCH 2/2] TVP514x Driver with Review comments fixed [V4] hvaibhav
2008-12-02 17:20   ` Hans Verkuil
2008-12-03  3:58     ` Hiremath, Vaibhav
2008-12-02 19:29   ` David Brownell
2008-12-02 19:44   ` David Brownell
2009-05-06 18:31 ` [PATCH (V2)] TVP514x: Migration to sub-device framework hvaibhav
2009-06-14 10:14   ` Hans Verkuil
2009-06-14 12:44     ` Hans Verkuil
2009-06-14 14:32       ` tcm825x.c: migrating to sub-device framework? (was: TVP514x: Migration to sub-device framework) Hans Verkuil
2009-06-15  8:45         ` tcm825x.c: migrating to sub-device framework? Sakari Ailus
     [not found]     ` <200906141214.38355.hverkuil-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2009-06-14 19:50       ` [PATCH (V2)] TVP514x: Migration to sub-device framework David Brownell
2008-11-24 11:23 [PATCH 2/2] TVP514x V4L int device driver support Hans Verkuil
  -- strict thread matches above, loose matches on Subject: below --
2008-11-24 10:22 Hans Verkuil
2008-11-24  9:32 Hans Verkuil
2008-11-24 10:46 ` Hiremath, Vaibhav

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=200811232232.31646.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=davinci-linux-open-source-bounces@linux.davincidsp.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-omap@vger.kernel.org \
    --cc=soni.trilok@gmail.com \
    --cc=video4linux-list@redhat.com \
    /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