alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Koul, Vinod" <vinod.koul@intel.com>
To: "broonie@kernel.org" <broonie@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "liam.r.girdwood@linux.intel.com"
	<liam.r.girdwood@linux.intel.com>,
	"tiwai@suse.de" <tiwai@suse.de>,
	"ckeepax@opensource.wolfsonmicro.com"
	<ckeepax@opensource.wolfsonmicro.com>,
	"o-takashi@sakamocchi.jp" <o-takashi@sakamocchi.jp>
Subject: Re: Audio miniconference at LPC/KS - draft schedule
Date: Wed, 2 Nov 2016 08:30:29 +0000	[thread overview]
Message-ID: <1478075425.19762.10.camel@intel.com> (raw)
In-Reply-To: <20161027221754.GW25322@sirena.org.uk>


Hi Mark, Takashi,

We need to find some time to discuss these..

- ASoC HDA..
- Byte controls TLV issue raised by Sakomoto-san (need charles here as
well)

Thanks
~Vinod


On Thu, 2016-10-27 at 23:17 +0100, Mark Brown wrote:
> The audio miniconference is next Tuesday, starting at 9am in Sweeney
> CDE
> at the Santa Fe Convention Center.
> 
> Currently the set of topics we have on the wiki and from e-mail for
> discussion is:
> 
>  - mmap/no IRQ mode
>  - Time stamp reporting (both current APIs and addition of ability to
>    push down PCM sync)
>  - USB audio power and latency performance
>  - Standardizing HDMI / DP interface
>  - SoundWire support
>  - Tracepoints for PCM parameter support
>  - Low latency audio
>  - Propagating digital configuration through the DAPM graph
>  - Userspace and configuration integration (how will topology etc get
>    integrated in OSes)
>  - Move of ASoC clocking into the clock API
>  - HDA/ASoC integration
>  - UCM scaling, does it scale well…?
>  - How to improve upstreaming vendor drivers?
>  - Stable / LTS kernel maintenance
>  - Para Virtualized audio driver support
>  - Userspace drivers (for IEEE 1394 and other things)
>  - Dropping the DICE driver
>  - Media Controller API integration
>   - Is there anything new here or should we just drop this entirely?
> 
> which is quite a list but some of those should be fairly simple to
> discuss so hopefully fairly quick.  I've made some effort to sort this
> into a rough order but it's very much a first pass so suggestions for
> changes are welcome.  Similarly are there are other things people
> think
> we should discuss?
> 
> There's also some discussion of incoporating the kernel wide topic of
> inter-device dependenices into the audio miniconference since this
> affects audio (especially ASoC) quite a bit as well as several other
> subsystems, that is likely to be just after a break or first thing in
> the morning in order to allow others who aren't interested in audio
> specifically to join (and hopefully if this happens we can convince
> them
> to get involved in working on audio!).
> 
> I look forward to seeing many of you in Santa Fe next week!

-- 
~Vinod
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2016-11-02  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-27 22:17 Audio miniconference at LPC/KS - draft schedule Mark Brown
2016-10-28  8:01 ` Liam Girdwood
2016-10-28 11:47   ` Lars-Peter Clausen
2016-10-28 15:39   ` Mark Brown
2016-10-29 14:05 ` Takashi Sakamoto
2016-10-31 23:39   ` Ughreja, Rakesh A
2016-11-02  8:30 ` Koul, Vinod [this message]
2016-11-13  3:33   ` Takashi Sakamoto
2016-11-13  6:09     ` Vinod Koul
2016-11-14  2:01       ` Takashi Sakamoto
2016-11-02 13:17 ` Lars-Peter Clausen

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=1478075425.19762.10.camel@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).