From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
linux-kernel@vger.kernel.org,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Huajun Li <huajun.li@intel.com>,
tiwai@suse.de, Takashi Iwai <tiwai@suse.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH 0/1] sound: add quirk for Huawei D15
Date: Fri, 18 Feb 2022 12:11:59 -0600 [thread overview]
Message-ID: <c17173cb-290c-9ecd-54e3-b74f9d4e9061@linux.intel.com> (raw)
In-Reply-To: <164519450743.1836505.3912962145996830275.b4-ty@kernel.org>
On 2/18/22 08:28, Mark Brown wrote:
> On Fri, 24 Dec 2021 14:09:48 +0100, Mauro Carvalho Chehab wrote:
>> Based on my tests, Huawei D15 (Intel) uses SSP0 on es8336.
>>
>> Add a quirk for it.
>>
>> Please notice that, currently, only the internal speaker is working.
>> The topology for the internal microphone and for the headphones
>> is wrong. Enabling/disabling the other two quirks (GPIO and/or DMIC)
>> doesn't cause any audible results, nor change the devices listed
>> on pavucontrol (tested with pipewire-pulse).
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
>
> [1/1] ASoC: Intel: sof_es8336: add quirk for Huawei D15 2021
> commit: ce6a70bfce21bb4edb7c0f29ecfb0522fa34ab71
I'll probably revert this change in my next update [1], I have a set of
changes where we can detect which SSP is used by parsing the NHTL
information in platform firmware.
I am still trying to figure out how to detect which MCLK is used, and
once this is done I'll send the patches upstream.
[1] https://github.com/thesofproject/linux/pull/3338
next prev parent reply other threads:[~2022-02-18 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 13:09 Mauro Carvalho Chehab
2021-12-24 13:09 ` [PATCH 1/1] ASoC: Intel: sof_es8336: add quirk for Huawei D15 2021 Mauro Carvalho Chehab
2022-02-18 14:28 ` [PATCH 0/1] sound: add quirk for Huawei D15 Mark Brown
2022-02-18 18:11 ` Pierre-Louis Bossart [this message]
2022-02-18 23:46 ` Mauro Carvalho Chehab
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=c17173cb-290c-9ecd-54e3-b74f9d4e9061@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=huajun.li@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.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
all inboxes | Powered by JetHome®