All of 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
Subject: Re: Audio miniconference schedule
Date: Tue, 16 Oct 2018 23:16:17 +0200	[thread overview]
Message-ID: <s5hefcpk2xq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181016204852.GK2340@sirena.org.uk>

On Tue, 16 Oct 2018 22:48:52 +0200,
Mark Brown wrote:
> 
> As previously announced there's an audio miniconference happening on the
> 21st in Edinburgh, meeting around 9am and getting started once enough
> people have arrived (Cirrus people, please let me know if we need to
> start later, some people have said they'll be arriving late so we won't
> wait for everyone):
> 
>    https://blog.sirena.org.uk/2018/09/19/2018-linux-audio-miniconfernce
> 
> (yes there is a typo in the URL).  A number of people have proposed
> topics so I just went through them and pulled them into a proposed
> agenda, this time revised following feedback last time:
> 
>   - Virtualization (Liam)
>   - AVB (Liam)
>   - SoundWire (Liam)
>   - GObject introspection for language bindings (Sakamoto-san)
>   - Integrating the ALSA control core (Sakamoto-san)
>   - DSPs (Liam)
>    - Sound Open Firmware (Liam)
>    - Byte controls (Vinod/Patrick)
>    - Calibration loading (Patrick)
>    - Exposing graph at runtime (Patrick)
>    - Batching commands (Patrick)
>   - AGL (Stephane/Ronan)
> 
> I've dropped Y2038 from the expliit schedule, since Arnd Bergmann (who's
> been driving a lot of the general Y2038 work) will be in Edinburgh and
> may be free to join I'm suggesting that if he's free we cover that
> either first thing or just after lunch and otherwise Takashi and I will
> try to coordinate with him during ELC-E (unless others have a great
> enthusiasm for the subject).

I haven't registered ELCE this year but only the audio mini-conf and
maintainers summit, but maybe we can catch him on Monday.

> What do people think?  Any other topics?  There's still time to sign up
> if you're interested in attending, you can sign up right up to the day
> of the event though registering early would help a lot with logistics.

Sorry for the late action, here are some items that came to my mind:

- Possible PCM improvements:
  We still miss some information like the granularity.  Although we
  had some discussions in the past, it didn't happen in the end.
  It's a good chance to revive the ideas.

  Also, PCM timestamping is another relevant topic.  It's still rarely
  used, so far.  Can we make a broader usage?

- ASoC / ALSA core merges:
  Would it make sense to move some core stuff out of ASoC?
  e.g. DPCM isn't strictly ASoC-specific things.
  Also, it'd be great if we can foresee the plan for ASoC core
  refactoring that is currently going on.

- Testing:
  My pet peeve.  I'd love to see some stuff, especially for ASoC, that
  can run on VM, and let fuzzers whipping on it.
  Also, USB audio can be virtualized.  What else?  (not only about VM
  testing but also a real hardware testing.)

- Community governance, maintenance issues:
  It's a hot topic in kernel, yeah.  Do we see any issues in audio?


thanks,

Takashi

  reply	other threads:[~2018-10-16 21:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 19:58 Audio miniconference schedule Mark Brown
2018-10-05 10:20 ` Charles Keepax
2018-10-05 11:44   ` Mark Brown
2018-10-14  5:50     ` Patrick Lai
2018-10-15 10:24       ` Mark Brown
2018-10-16 20:48 ` Mark Brown
2018-10-16 21:16   ` Takashi Iwai [this message]
2018-10-17 19:12     ` Mark Brown
2018-10-18  5:53       ` Keyon Jie
2018-10-18 17:44         ` Mark Brown
2018-10-19  3:06           ` Keyon Jie
2018-10-19 14:35           ` Charles Keepax
2018-10-19 16:14             ` Jaroslav Kysela
2018-10-21  8:12               ` Jaroslav Kysela
2018-10-21  9:01                 ` Charles Keepax
2018-10-21  9:46                 ` Takashi Iwai
2018-10-18 10:12     ` Takashi Sakamoto
2018-10-24  7:16 ` Takashi Iwai
2018-10-24  7:30   ` Jaroslav Kysela
2018-10-24  7:33     ` Takashi Iwai
2018-10-24  8:11       ` Vinod
2018-10-24  8:51         ` Jaroslav Kysela
2018-10-24 10:08           ` Vinod
2018-10-24 10:24         ` Mark Brown
2018-10-24 10:16     ` Charles Keepax
2018-10-18 17:55 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=s5hefcpk2xq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@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 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.