From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"mengdong.lin" <mengdong.lin@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
"Koul, Vinod" <vinod.koul@intel.com>,
Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"Lai, Patrick" <plai@quicinc.com>, Takashi Iwai <tiwai@suse.de>,
Lars-Peter Clausen <lars@metafoo.de>,
"Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>,
Eric Laurent <elaurent@google.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Dylan Reid <dgreid@google.com>
Subject: Re: [MINUTES] Linux Plumbers Audio Mini Conference - Santa Fe 2016
Date: Fri, 04 Nov 2016 13:59:26 +0000 [thread overview]
Message-ID: <1478267966.27988.8.camel@loki> (raw)
In-Reply-To: <e7fc9e49-6d6a-c224-d045-ef80308e11e0@ti.com>
On Fri, 2016-11-04 at 10:54 +0200, Peter Ujfalusi wrote:
> Liam,
>
> On 11/04/2016 12:51 AM, Liam Girdwood wrote:
> > Minutes below. Comments, corrections and omissions welcomed.
> >
> > We are missing some links to some of the slides presented. Please reply with a link
> > if you have one.
>
> Were there any discussion related to 'Move of ASoC clocking into the
> clock API'? Any conclusions, plans?
>
Sorry, yes this was discussed. Mark had pointed out there was a locking
issue in the clk API preventing it being used in codecs (iirc, in I2C
devices). I think Mark has now discussed with the clock maintainers.
The plan was to use the API after the locking issue was resolved.
Thanks
Liam
next prev parent reply other threads:[~2016-11-04 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 22:51 [MINUTES] Linux Plumbers Audio Mini Conference - Santa Fe 2016 Liam Girdwood
2016-11-04 8:54 ` Peter Ujfalusi
2016-11-04 13:59 ` Liam Girdwood [this message]
2016-11-13 16:55 ` Patrick Lai
2016-11-14 14:08 ` Mark Brown
2016-11-14 23:03 ` Takashi Sakamoto
2016-11-16 16:23 ` Mark Brown
2016-11-15 3:14 ` Vinod Koul
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=1478267966.27988.8.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dgreid@google.com \
--cc=elaurent@google.com \
--cc=lars@metafoo.de \
--cc=mchehab@osg.samsung.com \
--cc=mengdong.lin@linux.intel.com \
--cc=o-takashi@sakamocchi.jp \
--cc=peter.ujfalusi@ti.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@quicinc.com \
--cc=rakesh.a.ughreja@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@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 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.