Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: Prague Audio miniconference - topics for discussion?
Date: Fri, 06 Oct 2017 14:55:31 +0200	[thread overview]
Message-ID: <s5hvajs5tbw.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170920174505.64nieg6plut36cl5@sirena.co.uk>

On Wed, 20 Sep 2017 19:45:05 +0200,
Mark Brown wrote:
> 
> As previously announced[1] by Takashi our annual Linux audio
> miniconference will be held this year at the SuSE offices in Prague on
> 27th October (the week of ELC-E).  Thanks again to SuSe for sponsoring
> this.  As with previous years let's pull together an agenda through a
> mailing list discussion - if people could reply to this mail with any
> topics they'd like to discuss we can take it from there.  Of course if
> we can sort things out more quickly via the mailing list that's even
> better!
> 
> I'll start things off by mentining the TLV issues that Sakamoto-san was
> raising - do we have any better ideas to handle larger binary controls
> than what's currently being done?
> 
> [1] http://mailman.alsa-project.org/pipermail/alsa-devel/2017-August/124623.html

Thanks Mark for heading up.
And sorry for the late reply, it took time to process backlogs after
my vacation.

Here are the lists of topics I had in my mind:

- Status-quo;
  Recap what's been added/changed recently from API/ABI POV

- USB-audio - PCM handling;
  it's been a known issue regarding the unnecessary latency with
  USB-audio.  Do we need a new operation mode?

- Dynamic device handling, e.g. HDMI/DP;
  currently we deal with only the card-level disconnection, but it
  doesn't work well with devices having multiple digital ports.
  The disconnected state also leads to a problem with PulseAudio.

- Year 2038 problem;
  PCM API changes RFC were posted recently on alsa-devel, and we have
  timespec in other APIs (rawmidi and timer), too.

- ASoC hotplug support;
  recent works / reports from Morimoto-san revealed the lack of
  hotplug support in ASoC.

- Drop of obsoleted drivers / features;
  time to think of diet?

- API/ABI documentation;
  do we have a better shape than before?  How can it be improved?

- ALSA user-space stuff releases;
  maybe we should stick with more strict release schedule?


thanks,

Takashi

  parent reply	other threads:[~2017-10-06 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 17:45 Prague Audio miniconference - topics for discussion? Mark Brown
2017-09-21  8:43 ` Charles Keepax
2017-09-29  0:45 ` Eric Laurent
2017-10-02 14:57 ` Takashi Sakamoto
2017-10-03  9:51 ` Peter Ujfalusi
2017-10-06 12:55 ` Takashi Iwai [this message]
2017-10-23 12:36   ` Mark Brown

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=s5hvajs5tbw.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    /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