From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC updates for v4.15
Date: Mon, 13 Nov 2017 16:54:13 +0100 [thread overview]
Message-ID: <s5h4lpyb2e2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171113115242.pmc7asf4yumj5ubk@sirena.co.uk>
On Mon, 13 Nov 2017 12:52:42 +0100,
Mark Brown wrote:
>
> The following changes since commit 39dae59d66acd86d1de24294bd2f343fd5e7a625:
>
> Linux 4.14-rc8 (2017-11-05 13:05:14 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-v4.15
>
> for you to fetch changes up to df6a3e245541ac61cc99f2887437e0a43dd08f2e:
>
> Merge remote-tracking branches 'asoc/topic/tfa9879', 'asoc/topic/ts3a277e', 'asoc/topic/wm8741', 'asoc/topic/wm97xx' and 'asoc/topic/zte' into asoc-next (2017-11-10 21:31:33 +0000)
>
> ----------------------------------------------------------------
> ASoC: Updates for v4.15
>
> The biggest thing this release has been the conversion of the AC98 bus
> to the driver model, that's been a long time coming so thanks to Robert
> Jarzmik for his dedication there. Due to there being some AC97 MFD
> there's a few fairly large changes in input and the MFD layer, mainly to
> the wm97xx driver.
>
> There's also some drivers/drm changes to support the new AMD Stoney
> platform, these are shared with the DRM subsystem and should be being
> merged via both.
>
> Within the subsystem the overwhelming bulk of the changes is in the
> Intel drivers which continue to need lots of cleanups and fixes, this
> release they've also gained support for their open source firmware.
> There's also some large changs in the core as Morimoto-san continues to
> mirror operations into the component level in preparation for conversion
> of drivers to that.
>
> - The AC97 bus has finally caught up with the driver model thanks to
> some dedicated and persistent work from Robert Jarzmik.
> - Continued work from Morimoto-san on moving us towards being able to
> use components for everything.
> - Lots of cleanups for the Intel platform code, including support for
> their open source audio firmware.
> - Support for scaling MCLK with sample rate in simple-card.
> - Support for AMD Stoney platform.
Pulled now, thanks.
BTW, one thing Linus requested in the last KS is to avoid merging to a
stub branch when you're managing topic branches. If any, just smash
the rest branches into one of your branches, instead of merging into
the upstream point. Just a reminder for the next time.
Takashi
next prev parent reply other threads:[~2017-11-13 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 11:52 [GIT PULL] ASoC updates for v4.15 Mark Brown
2017-11-13 15:54 ` Takashi Iwai [this message]
2017-11-13 16:30 ` Mark Brown
2017-11-13 16:36 ` Takashi Iwai
2017-11-13 17:20 ` Mark Brown
2017-11-15 4:33 ` 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=s5h4lpyb2e2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox