All of lore.kernel.org
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: mchehab@kernel.org, perex@perex.cz, tiwai@suse.com,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, shuah <shuah@kernel.org>
Subject: Re: [RFC PATCH v8 1/4] media: Media Device Allocator API
Date: Thu, 6 Dec 2018 08:33:14 -0700	[thread overview]
Message-ID: <73c22137-9c7a-75c8-8cd1-3736c63c2d40@kernel.org> (raw)
In-Reply-To: <20181119085931.GA28607@amd>

On 11/19/18 1:59 AM, Pavel Machek wrote:
> On Thu 2018-11-01 18:31:30, shuah@kernel.org wrote:
>> From: Shuah Khan <shuah@kernel.org>
>>
>> Media Device Allocator API to allows multiple drivers share a media device.
>> Using this API, drivers can allocate a media device with the shared struct
>> device as the key. Once the media device is allocated by a driver, other
>> drivers can get a reference to it. The media device is released when all
>> the references are released.
> 
> Sounds like a ... bad idea?
> 
> That's what new "media control" framework is for, no?
> 
> Why do you need this?
> 								Pavel
> 

Media control framework doesn't address this problem of ownership of the 
media device when non-media drivers have to own the pipeline. In this 
case, snd-usb owns the audio pipeline when an audio application is using 
the device. Without this work, media drivers won't be able to tell if 
snd-usb is using the tuner and owns the media pipeline.

I am going to clarify this in the commit log.

thanks,
-- Shuah

  reply	other threads:[~2018-12-06 15:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02  0:31 [RFC PATCH v8 0/4] Media Device Allocator API shuah
     [not found] ` <cover.1541109584.git.shuah@kernel.org>
2018-11-02  0:31   ` [RFC PATCH v8 1/4] media: " shuah
2018-11-19  8:59     ` Pavel Machek
2018-12-06 15:33       ` shuah [this message]
2018-12-09  8:09         ` Pavel Machek
2018-12-09  8:09           ` Pavel Machek
2018-12-09 11:27           ` Mauro Carvalho Chehab
2018-12-09 11:27             ` Mauro Carvalho Chehab
2018-12-09 11:37             ` Pavel Machek
2018-12-09 11:37               ` Pavel Machek
2018-11-20 11:20     ` Hans Verkuil
2018-12-06 15:27       ` shuah
2018-11-02  0:31   ` [RFC PATCH v8 2/4] media: change au0828 to use " shuah
2018-11-02  0:31   ` [RFC PATCH v8 3/4] media: media.h: Enable ALSA MEDIA_INTF_T* interface types shuah
2018-11-20 11:22     ` Hans Verkuil
2018-12-06 15:29       ` shuah
2018-11-02  0:31   ` [RFC PATCH v8 4/4] sound/usb: Use Media Controller API to share media resources shuah
2018-11-20 11:54     ` Hans Verkuil
2018-12-06 15:34       ` shuah

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=73c22137-9c7a-75c8-8cd1-3736c63c2d40@kernel.org \
    --to=shuah@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.