Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>
Cc: "'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>
Subject: Re: Para-virtualized audio drivers
Date: Thu, 20 Oct 2016 20:09:38 +0200	[thread overview]
Message-ID: <s5hr37aq4d9.wl-tiwai@suse.de> (raw)
In-Reply-To: <85DFEED57DC57344B2483EF7BF8CB60552C5EC44@BGSMSX104.gar.corp.intel.com>

On Thu, 20 Oct 2016 19:02:42 +0200,
Ughreja, Rakesh A wrote:
> 
> >>
> >> I am thinking to develop pv-audio-frontend (running on Dom1) and
> >> pv-audio-backend (running on Dom0) drivers all at kernel level.
> >> Backend driver owns the hardware. Frontend driver communicates with
> >> backend driver using XENbus framework just like storage and network PV
> >> drivers.
> >>
> >> Before I start, I wanted to check if there is any other
> >> work that has been done which I can take as base ?
> >
> >I don't know of any other existing implementation for Xen.  The
> >question would be rather how you would implement the backend.
> >
> 
> My thinking is to have backend driver at kernel level. The backend
> driver would receive requests from frontend driver. I agree that the
> previous effort was to develop it in user space.
> 
> >Is it about Intel hardware as Liam has been working on?  Or is it
> 
> Liam's work is different.
> 
> >targeted as a generic Xen stuff like the patches you mentioned in the
> >above?  The patchset above was about the user-space backend, IIRC.
> >
> 
> I am trying to develop generic PV audio drivers for XEN. I see people 
> have developed PV Storage and Network drivers in XEN and they
> are up-streamed. So I was thinking to do that for audio as well.
> 
> Do you recall why the above patchset was not merged ?
> any limitations or was it incomplete ? 

I don't remember it well.  I guess I wasn't involved with that
discussion since I was off when it was posted or so.  Since then there
was little attention gathered, unfortunately.


Takashi

      reply	other threads:[~2016-10-20 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17  3:01 Para-virtualized audio drivers Ughreja, Rakesh A
2016-10-19 10:27 ` Liam Girdwood
2016-10-20 15:26 ` Takashi Iwai
2016-10-20 17:02   ` Ughreja, Rakesh A
2016-10-20 18:09     ` Takashi Iwai [this message]

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=s5hr37aq4d9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=rakesh.a.ughreja@intel.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