From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
<alsa-devel@alsa-project.org>, <broonie@kernel.org>
Cc: hdegoede@redhat.com, tiwai@suse.com, amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH v4 00/17] ASoC: Intel: haswell and broadwell boards update
Date: Thu, 23 Jun 2022 10:16:15 +0200 [thread overview]
Message-ID: <3a10d841-b8aa-fe4b-4fad-bdaf0fa42ad7@intel.com> (raw)
In-Reply-To: <28efb05f-2f8e-c0fb-c079-0f65ee5283c5@linux.intel.com>
On 2022-06-22 8:55 PM, Pierre-Louis Bossart wrote:
>>> I also had additional errors not reported,
>>>
>>> [ 36.125113] kernel: rt286 i2c-INT343A:00: ASoC: unknown pin HV
>>> [ 36.125128] kernel: rt286 i2c-INT343A:00: ASoC: unknown pin VREF
>>> [ 36.125130] kernel: rt286 i2c-INT343A:00: ASoC: unknown pin LDO1
>>> [ 36.125921] kernel: rt286 i2c-INT343A:00: ASoC: DAPM unknown pin LDO1
(save)
> That's fine as well. What I was arguing on is the relationship between
> patchsets and dependencies, what you are suggesting is perfectly acceptable.
I agree. Frankly I was not aware about the dependencies myself - it
wasn't done on purpose. Your report above (notice that there is more
than just the LDO1 line) made me analyze our tree once more. Turned out
that fixes related to Realtek codecs sent by Amadeo last week [1]
address the problem and that's why I had not noticed anything.
Will work on the codec series and see what's needed or not given Mark's
review and then come back to the bdw_rt286 jack-handling subject. Thanks!
[1]:
https://lore.kernel.org/alsa-devel/20220609133541.3984886-1-amadeuszx.slawinski@linux.intel.com/
Regards,
Czarek
next prev parent reply other threads:[~2022-06-23 8:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:13 [PATCH v4 00/17] ASoC: Intel: haswell and broadwell boards update Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 01/17] ASoC: Intel: Rename haswell source file to hsw_rt5640 Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 02/17] ASoC: Intel: hsw_rt5640: Reword prefixes of all driver members Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 03/17] ASoC: Intel: hsw_rt5640: Reword driver name Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 04/17] ASoC: Intel: hsw_rt5640: Update code indentation Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 05/17] ASoC: Intel: hsw_rt5640: Update file comments Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 06/17] ASoC: Intel: hsw_rt5640: Improve probe() function quality Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 07/17] ASoC: Intel: hsw_rt5640: Improve hw_params() debug-ability Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 08/17] ASoC: Intel: Rename broadwell source file to bdw_rt286 Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 09/17] ASoC: Intel: bdw_rt286: Reword prefixes of all driver members Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 10/17] ASoC: Intel: bdw_rt286: Reword driver name Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 11/17] ASoC: Intel: bdw_rt286: Update code indentation Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 12/17] ASoC: Intel: bdw_rt286: Update file comments Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 13/17] ASoC: Intel: bdw_rt286: Improve probe() function quality Cezary Rojewski
2022-06-20 10:13 ` [PATCH v4 14/17] ASoC: Intel: bdw_rt286: Improve hw_params() debug-ability Cezary Rojewski
2022-06-20 10:14 ` [PATCH v4 15/17] ASoC: Intel: bdw_rt286: Improve codec_init() quality Cezary Rojewski
2022-06-20 10:14 ` [PATCH v4 16/17] ASoC: Intel: bdw_rt286: Refactor jack handling Cezary Rojewski
2022-06-20 10:14 ` [PATCH v4 17/17] ASoC: Intel: bdw_rt286: Remove FE DAI ops Cezary Rojewski
2022-06-21 16:36 ` [PATCH v4 00/17] ASoC: Intel: haswell and broadwell boards update Pierre-Louis Bossart
2022-06-21 17:47 ` Cezary Rojewski
2022-06-21 21:11 ` Pierre-Louis Bossart
2022-06-22 18:15 ` Cezary Rojewski
2022-06-22 18:55 ` Pierre-Louis Bossart
2022-06-23 8:16 ` Cezary Rojewski [this message]
2022-06-24 10:59 ` (subset) " 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=3a10d841-b8aa-fe4b-4fad-bdaf0fa42ad7@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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