public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Scott <rustys@ieee.org>
To: linux-media@vger.kernel.org
Subject: RFC - Locking resources between V4L and DVB interfaces
Date: Tue, 26 May 2009 13:51:15 -0600	[thread overview]
Message-ID: <1243367475.15846.19.camel@godzilla> (raw)

Hello all,
I talked to Mauro offline about this issue and he indicated that it was
an area that could use some attention.  So I have decided to take this
issue on and am looking for comments about how this should work.

Issue: The DVB and V4L interfaces are considered different devices from
a system standpoint.  However they often share a hardware resource, such
as a tuner, on many cards.  There is currently no locking on the shared
resource, so one interface could interfere with the resources already in
use by the other.

My experience in the code tree and API are not very in depth.  I've only
helped maintain some card specific code to this point.  I'm looking for
comments and information on various ways to accomplish this and possible
gotchas to watch out for.  Any pointers, suggestions or other help on
this would be appreciated.

Thanks,

Rusty



             reply	other threads:[~2009-05-26 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 19:51 Rusty Scott [this message]
2009-06-09  0:52 ` RFC - Locking resources between V4L and DVB interfaces hermann pitton

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=1243367475.15846.19.camel@godzilla \
    --to=rustys@ieee.org \
    --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