From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: codecs: allow compile testing without MFD drivers
Date: Fri, 26 Aug 2022 19:35:55 +0100 [thread overview]
Message-ID: <YwkSi1IIRsW2Hc/u@sirena.org.uk> (raw)
In-Reply-To: <20220826093659.1059276-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
On Fri, Aug 26, 2022 at 12:36:59PM +0300, Krzysztof Kozlowski wrote:
> Motorola CPCAP, Lochnagar Sound, Rockchip RK817 and Qualcomm
> WCD9340/WCD9341 do not depend on parent MFD driver in build time and can
> be compile tested without respective MFD part for increased build
> coverage.
Although generally it's easy enough to just turn on the MFDs
themselves, it's not the same base platform issue as the firmware
interfaces can be.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: codecs: allow compile testing without MFD drivers
Date: Fri, 26 Aug 2022 19:35:55 +0100 [thread overview]
Message-ID: <YwkSi1IIRsW2Hc/u@sirena.org.uk> (raw)
In-Reply-To: <20220826093659.1059276-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
On Fri, Aug 26, 2022 at 12:36:59PM +0300, Krzysztof Kozlowski wrote:
> Motorola CPCAP, Lochnagar Sound, Rockchip RK817 and Qualcomm
> WCD9340/WCD9341 do not depend on parent MFD driver in build time and can
> be compile tested without respective MFD part for increased build
> coverage.
Although generally it's easy enough to just turn on the MFDs
themselves, it's not the same base platform issue as the firmware
interfaces can be.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-26 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 9:36 [PATCH] ASoC: codecs: allow compile testing without MFD drivers Krzysztof Kozlowski
2022-08-26 18:35 ` Mark Brown [this message]
2022-08-26 18:35 ` Mark Brown
2022-08-27 9:02 ` Krzysztof Kozlowski
2022-08-27 9:02 ` Krzysztof Kozlowski
2022-08-30 10:35 ` Mark Brown
2022-08-30 10:35 ` Mark Brown
2022-08-30 10:51 ` Krzysztof Kozlowski
2022-08-30 10:51 ` Krzysztof Kozlowski
2022-08-29 13:01 ` 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=YwkSi1IIRsW2Hc/u@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.