From: Johan Hovold <johan@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Peter Rosin <peda@axentia.se>,
Johan Hovold <johan+linaro@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mux: suppress lookup errors for mux controls
Date: Tue, 15 Apr 2025 08:26:45 +0200 [thread overview]
Message-ID: <Z_38JaJLNXnq1STb@hovoldconsulting.com> (raw)
In-Reply-To: <20bc473e-3386-443d-8350-f6718e7903a0@linaro.org>
On Mon, Apr 14, 2025 at 03:35:03PM +0100, Srinivas Kandagatla wrote:
> On 14/04/2025 15:01, Johan Hovold wrote:
> >> Srinivas Kandagatla is looking into optional muxes as a side issue to
> >> exclusive muxes.
> >> https://lore.kernel.org/all/20250326154613.3735-1-srinivas.kandagatla@linaro.org/
> > The audio codec change introduces a de-facto regression so if you want
> > something different, we'll have to fix this in the codec driver directly
> > by checking for a "mux-controls" property before doing the lookup for
>
> This is not scalable solution, we need something in the core to allow
> optional mux like any other framworks.
Maybe, but that's not something that exists today and we should not
knowingly introduce bogus errors.
I'll suppress the error in the codec driver instead and you guys can
continue discussing how you want to rework the mux driver.
Johan
prev parent reply other threads:[~2025-04-15 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 12:42 [PATCH] mux: suppress lookup errors for mux controls Johan Hovold
2025-04-14 13:18 ` Peter Rosin
2025-04-14 14:01 ` Johan Hovold
2025-04-14 14:35 ` Srinivas Kandagatla
2025-04-15 6:26 ` Johan Hovold [this message]
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=Z_38JaJLNXnq1STb@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=srinivas.kandagatla@linaro.org \
/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