From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
alsa-devel@alsa-project.org
Cc: tiwai@suse.de, liam.r.girdwood@linux.intel.com,
broonie@kernel.org, jarkko.nikula@linux.intel.com,
vinod.koul@intel.com
Subject: Re: [PATCH 3/7] ASoC: Intel: cht_bsw_max98090: add support for Baytrail
Date: Mon, 18 Sep 2017 12:14:17 -0500 [thread overview]
Message-ID: <37e5b151-f556-aaa3-ff34-877de72d6347@linux.intel.com> (raw)
In-Reply-To: <1505719053.25945.269.camel@linux.intel.com>
On 9/18/17 2:17 AM, Andy Shevchenko wrote:
> On Fri, 2017-09-08 at 00:13 -0500, Pierre-Louis Bossart wrote:
>> Distributions such as Fedora, Ubuntu and Gallium don't currently
>> have a means to support Baytrail Chromebooks and other platforms
>> with the same build [1][2] due to incompatible platform drivers.
>>
>> Add MCLK management to reuse this machine driver for Baytrail
>> platforms and solve this coexistence problem at last. UCM files are
>> provided at [3] and will eventually be submitted to the new repo.
>>
>> The legacy byt-max98090 machine driver is still maintained but can
>> only be used when the other Atom/DPCM driver is not compiled in, or
>> when users don't want to configure extra mixers required by the
>> Atom/sst driver.
>>
>> Tested on Lenovo 100s Baytrail Chromebook w/ Mr. Chromebox BOOT_STUB
>> firmware and Acer R11 Cherrytrail Chromebook
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1335196
>> [2] http://mailman.alsa-project.org/pipermail/alsa-devel/2016-August/
>> 111641.html
>> [3] https://github.com/plbossart/UCM/tree/master/byt-max98090
>>
>>
>
>>
>> +static inline struct snd_soc_dai *cht_get_codec_dai(struct
>> snd_soc_card *card)
>> +{
>> + struct snd_soc_pcm_runtime *rtd;
>> +
>> + list_for_each_entry(rtd, &card->rtd_list, list) {
>> + if (!strncmp(rtd->codec_dai->name, CHT_CODEC_DAI,
>> + strlen(CHT_CODEC_DAI)))
>
> Same comments as per another patch series wrt str_n_cmp() use.
Yes, if that's alright with you I'll clean this up in all Intel machine
drivers in one patch since this is all copy-paste. I just need a clear
indication on what the preferred means of string comparisons is...
>
>> + return rtd->codec_dai;
>> + }
>> + return NULL;
>
>
next prev parent reply other threads:[~2017-09-18 17:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 5:13 [PATCH 0/7] BYT/CHT clocks/max98090 updates Pierre-Louis Bossart
2017-09-08 5:13 ` [PATCH 1/7] ASoC: max98090: reduce verbosity on PLL unlock Pierre-Louis Bossart
2017-09-19 13:45 ` Applied "ASoC: max98090: reduce verbosity on PLL unlock" to the asoc tree Mark Brown
2017-09-08 5:13 ` [PATCH 2/7] ASoC: Intel: cht_bsw_max98090: Fix I2S config + unused code Pierre-Louis Bossart
2017-09-08 5:13 ` [PATCH 3/7] ASoC: Intel: cht_bsw_max98090: add support for Baytrail Pierre-Louis Bossart
2017-09-18 7:17 ` Andy Shevchenko
2017-09-18 17:14 ` Pierre-Louis Bossart [this message]
2017-09-19 9:51 ` Andy Shevchenko
2017-09-19 13:45 ` Applied "ASoC: Intel: cht_bsw_max98090: add support for Baytrail" to the asoc tree Mark Brown
2017-09-08 5:13 ` [PATCH 4/7] ASoC: Intel: atom: use cht_bsw_max98090 for Baytrail Chromebooks Pierre-Louis Bossart
2017-09-08 5:13 ` [PATCH 5/7] ASoC: ts3a227e: add acpi table Pierre-Louis Bossart
2017-09-08 13:27 ` Vinod Koul
2017-09-08 13:30 ` Pierre-Louis Bossart
2017-09-12 14:54 ` Mark Brown
2017-09-18 3:36 ` Vinod Koul
2017-09-08 5:13 ` [PATCH 6/7] ASoc: Intel: cht_bsw_max98090_ti: Fix jack initialization Pierre-Louis Bossart
2017-09-19 13:45 ` Applied "ASoC: Intel: cht_bsw_max98090_ti: Fix jack initialization" to the asoc tree Mark Brown
2017-09-08 5:13 ` [PATCH 7/7] ASoC: Intel: cht_bsw_max98090: add gpio-based jack detection Pierre-Louis Bossart
2017-09-19 13:45 ` Applied "ASoC: Intel: cht_bsw_max98090: add gpio-based jack detection" to the asoc tree Mark Brown
2017-09-18 3:36 ` [PATCH 0/7] BYT/CHT clocks/max98090 updates 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=37e5b151-f556-aaa3-ff34-877de72d6347@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=liam.r.girdwood@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).