mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Paulraj, Sandeep" <s-paulraj@ti.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Grosen, Mark" <mgrosen@ti.com>
Subject: Re: New Driver for DaVinci DM355/DM365/DM6446
Date: Mon, 1 Jun 2009 15:58:54 -0300	[thread overview]
Message-ID: <20090601155854.38350ab5@pedra.chehab.org> (raw)
In-Reply-To: <C9D59C82B94F474B872F2092A87F2614817980B0@dlee07.ent.ti.com>

Em Mon, 1 Jun 2009 13:39:17 -0500
"Paulraj, Sandeep" <s-paulraj@ti.com> escreveu:

> > > [Sandeep] WE don't propose any API changes. This module for which we  
> > want to submit patches is a TI proprietary IP. We currently implement this
> > as a character device and have a few IOCTL's.  
> > > We do not follow the V4L2 framework and do not use any V4L2 IOCTLs.
> > >
> > > Can we continue to use it as a character driver?  
> > 
> > In this case, I don't see why you want it to be upstream.  
> [Sandeep] TI customers and TI itself want to see this driver part of open source trees. Considering this we would like to submit our patches to the linux-media mailing list.
> IS this OK?

If you're just providing a character API with some protocol protected by IP,
you're not providing the source code of the driver, but something else. 

It is not ok to provide such driver. 

Also, even if you disclosure your protocol, it makes no sense to create another
API for userspace communication, for features that already exists or can easily
expand to accommodate your needs. 

So, you should really use the V4L2 API for the driver, expanding it where
required, if you want it to be considered for upstream addition.



Cheers,
Mauro

  reply	other threads:[~2009-06-01 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 14:56 Paulraj, Sandeep
2009-06-01 16:34 ` Mauro Carvalho Chehab
2009-06-01 16:54   ` Paulraj, Sandeep
2009-06-01 17:57     ` Mauro Carvalho Chehab
2009-06-01 18:39       ` Paulraj, Sandeep
2009-06-01 18:58         ` Mauro Carvalho Chehab [this message]
2009-06-01 18:38 ` Aguirre Rodriguez, Sergio Alberto
2009-06-01 18:58   ` Karicheri, Muralidharan
2009-06-01 19:13     ` Aguirre Rodriguez, Sergio Alberto
2009-06-01 19:02   ` Mauro Carvalho Chehab

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=20090601155854.38350ab5@pedra.chehab.org \
    --to=mchehab@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mgrosen@ti.com \
    --cc=s-paulraj@ti.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

all inboxes | Powered by JetHome®