From: Lars-Peter Clausen <lars@metafoo.de>
To: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: ASoC updates for v3.17
Date: Mon, 04 Aug 2014 18:57:31 +0200 [thread overview]
Message-ID: <53DFBB7B.2030804@metafoo.de> (raw)
In-Reply-To: <s5hppgg6wj5.wl%tiwai@suse.de>
On 08/04/2014 06:37 PM, Takashi Iwai wrote:
> At Mon, 4 Aug 2014 17:17:50 +0100,
> Mark Brown wrote:
>>
>> The following changes since commit 19583ca584d6f574384e17fe7613dfaeadcdc4a6:
>>
>> Linux 3.16 (2014-08-03 15:25:02 -0700)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v3.17
>>
>> for you to fetch changes up to ae34a78c430c37c06404f032fb04e51315204281:
>>
>> Merge remote-tracking branch 'asoc/topic/wm8985' into asoc-next (2014-08-04 16:32:25 +0100)
>>
>> ----------------------------------------------------------------
>>
>> ASoC: Updates for v3.17
>>
>> This has been a pretty exciting release in terms of the framework, we've
>> finally got support for multiple CODECs attached to a single DAI link
>> which has been something there's been interest in as long as I've been
>> working on ASoC. A big thanks to Benoit and Misael for their work on
>> this.
>>
>> Otherwise it's been a fairly standard release for development, including
>> more componentisation work from Lars-Peter and a good selection of both
>> CODEC and CPU drivers.
>>
>> - Support for multiple CODECs attached to a single DAI, enabling
>> systems with for example multiple DAC/speaker drivers on a single
>> link, contributed by Benoit Cousson based on work from Misael Lopez
>> Cruz.
>> - Support for byte controls larger than 256 bytes based on the use of
>> TLVs contributed by Omair Mohammed Abdullah.
>> - More componentisation work from Lars-Peter Clausen.
>> - The remainder of the conversions of CODEC drivers to params_width()
>> - Drivers for Cirrus Logic CS4265, Freescale i.MX ASRC blocks, Realtek
>> RT286 and RT5670, Rockchip RK3xxx I2S controllers and Texas Instruments
>> TAS2552.
>> - Lots of updates and fixes, especially to the DaVinci, Intel,
>> Freescale, Realtek, and rcar drivers.
>
> Thanks, pulled now. The only build regression I've seen is the
> warning:
>
> sound/soc/soc-dapm.c: In function ‘snd_soc_dapm_get_enum_double’:
> sound/soc/soc-dapm.c:2862:15: warning: ‘reg_val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> I guess it came from the recent Lars' change.
> It just gives the garbage value and shouldn't be serious, but it'd be
> better to be fixed in anyways.
>
yep. looks like your compiler is a bit smarter than mine. I'll send a patch.
The issue itself is harmless though since we even though we do some
transformations on the uninitialized value the result of that is never used
since we return a error code.
- Lars
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-08-04 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 16:17 ASoC updates for v3.17 Mark Brown
2014-08-04 16:37 ` Takashi Iwai
2014-08-04 16:57 ` Lars-Peter Clausen [this message]
2014-08-04 17:29 ` 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=53DFBB7B.2030804@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--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 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.