Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@kernel.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: Prague Audio miniconference - topics for discussion?
Date: Tue, 3 Oct 2017 12:51:24 +0300	[thread overview]
Message-ID: <4bd48871-5894-d585-ed8b-4a9135aa6cc6@ti.com> (raw)
In-Reply-To: <20170920174505.64nieg6plut36cl5@sirena.co.uk>

Hi,


Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

On 2017-09-20 20:45, 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!

Common clock framework within ASoC framework.
 - Use CCF for clock configuration in ASoC for DAIs/codecs
 - at least for McASP we need a way to select different reference clocks
and clock directions from several sources and then route clocks to
outside of the SoC.

http://mailman.alsa-project.org/pipermail/alsa-devel/2016-February/104316.html
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-February/104320.html

afaik it is still not resolved and I'm carrying the patches ever since.

- Péter

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

  parent reply	other threads:[~2017-10-03  9:51 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 [this message]
2017-10-06 12:55 ` Takashi Iwai
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=4bd48871-5894-d585-ed8b-4a9135aa6cc6@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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