Skip to contentSkip to conversation

mux: suppress lookup errors for mux controls

PATCH In review Johan Hovold 4 participants 5 messages Apr 14, 2025 – Apr 15, 2025 Multiplexer

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 mux: suppress lookup errors for mux controls

Since commit eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux") we have drivers looking up mux controls that are optional. This results in errors incorrectly being logged on machines like the Lenovo ThinkPad X13s where the mux is missing:

wcd938x_codec audio-codec: /audio-codec: failed to get mux-control (0)

Suppress the error message when lookup of mux controls fails and make sure to return -ENOENT consistently also when looking up controls by name so that consumer drivers can easily determine how to proceed.

Note that most current consumers already log mux lookup failures themselves.

Fixes eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux")
---
 drivers/mux/core.c | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)
drivers/mux/core.c +12 -4
index 02be4ba37257..b95bc03e3d6b 100644
@@ -544,8 +544,13 @@ static struct mux_control *mux_get(struct device *dev, const char *mux_name,
 			index = of_property_match_string(np, "mux-control-names",
 							 mux_name);
 		if (index < 0) {
-			dev_err(dev, "mux controller '%s' not found\n",
-				mux_name);
+			if (!state && index == -EINVAL)
+				index = -ENOENT;
+
+			if (index != -ENOENT) {
+				dev_err(dev, "mux controller '%s' not found\n",
+					mux_name);
+			}
 			return ERR_PTR(index);
 		}
 	}
@@ -559,8 +564,11 @@ static struct mux_control *mux_get(struct device *dev, const char *mux_name,
 						 "mux-controls", "#mux-control-cells",
 						 index, &args);
 	if (ret) {
-		dev_err(dev, "%pOF: failed to get mux-%s %s(%i)\n",
-			np, state ? "state" : "control", mux_name ?: "", index);
+		if (state || ret != -ENOENT) {
+			dev_err(dev, "%pOF: failed to get mux-%s %s(%i)\n",
+				np, state ? "state" : "control",
+				mux_name ?: "", index);
+		}
 		return ERR_PTR(ret);
 	}
 
Signature · 1 line
2.49.0
#1 lore raw

Hi!

Quoted 26 lines · Johan Hovold

Since commit eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux") we have drivers looking up mux controls that are optional. This results in errors incorrectly being logged on machines like the Lenovo ThinkPad X13s where the mux is missing:

wcd938x_codec audio-codec: /audio-codec: failed to get mux-control (0)

Suppress the error message when lookup of mux controls fails and make sure to return -ENOENT consistently also when looking up controls by name so that consumer drivers can easily determine how to proceed.

Note that most current consumers already log mux lookup failures themselves.

Fixes eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux")
---
 drivers/mux/core.c | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)
drivers/mux/core.c +0 -0
index 02be4ba37257..b95bc03e3d6b 100644

drivers/mux/core.c static struct mux_control *mux_get(struct device *dev, const char *mux_name, · line 548

Quoted 7 lines
drivers/mux/core.c +2 -2
@@ -544,8 +544,13 @@ static struct mux_control *mux_get(struct device *dev, const char *mux_name,
 			index = of_property_match_string(np, "mux-control-names",
 							 mux_name);
 		if (index < 0) {
-			dev_err(dev, "mux controller '%s' not found\n",
-				mux_name);
+			if (!state && index == -EINVAL)
+				index = -ENOENT;

Why exclude states? For me, that's entirely random and inconsistent. If there's a reason to exclude them, I'd like to hear about it. If there is no reason and this is just defensive programming, then I'd like for someone to dig into it and either find a reason for the difference or clean up the inconsistency.

I think the model of explicitly marking when you'd like a mux to be optional is a better and less fragile model. Who is to say that -EINVAL from some other call is, and will remain, a perfect match for the optional case you are aiming for?

Srinivas Kandagatla is looking into optional muxes as a side issue to exclusive muxes.
https://lore.kernel.org/all/[email protected]/

Cheers,
Peter

Quoted 22 lines
drivers/mux/core.c +10 -2
+
+			if (index != -ENOENT) {
+				dev_err(dev, "mux controller '%s' not found\n",
+					mux_name);
+			}
 			return ERR_PTR(index);
 		}
 	}
@@ -559,8 +564,11 @@ static struct mux_control *mux_get(struct device *dev, const char *mux_name,
 						 "mux-controls", "#mux-control-cells",
 						 index, &args);
 	if (ret) {
-		dev_err(dev, "%pOF: failed to get mux-%s %s(%i)\n",
-			np, state ? "state" : "control", mux_name ?: "", index);
+		if (state || ret != -ENOENT) {
+			dev_err(dev, "%pOF: failed to get mux-%s %s(%i)\n",
+				np, state ? "state" : "control",
+				mux_name ?: "", index);
+		}
 		return ERR_PTR(ret);
 	}
 
#2 lore raw
Quoted 19 lines · Peter Rosin
Quoted 17 lines · Johan Hovold

Since commit eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux") we have drivers looking up mux controls that are optional. This results in errors incorrectly being logged on machines like the Lenovo ThinkPad X13s where the mux is missing:

wcd938x_codec audio-codec: /audio-codec: failed to get mux-control (0)

Suppress the error message when lookup of mux controls fails and make sure to return -ENOENT consistently also when looking up controls by name so that consumer drivers can easily determine how to proceed.

Note that most current consumers already log mux lookup failures themselves.

Fixes eec611d26f84 ("ASoC: codecs: wcd938x: add mux control support for hp audio mux")
Quoted 15 lines

drivers/mux/core.c static struct mux_control *mux_get(struct device *dev, const char *mux_name, · line 548

Quoted 10 lines
drivers/mux/core.c +2 -2
@@ -544,8 +544,13 @@ static struct mux_control *mux_get(struct device *dev, const char *mux_name,
 			index = of_property_match_string(np, "mux-control-names",
 							 mux_name);
 		if (index < 0) {
-			dev_err(dev, "mux controller '%s' not found\n",
-				mux_name);
+			if (!state && index == -EINVAL)
+				index = -ENOENT;

Why exclude states? For me, that's entirely random and inconsistent. If there's a reason to exclude them, I'd like to hear about it. If there is no reason and this is just defensive programming, then I'd like for someone to dig into it and either find a reason for the difference or clean up the inconsistency.

I only found one user of "mux states" and I'm still not quite sure why there are two interfaces for looking up muxes. But my impression was that if you need a mux set to a specific state and you even encode that directly in DT, then there should be no need to support optional resources.

After taking a closer look at the single consumer now, I see that it already implements optional lookups itself and thus could benefit from generalising this.

There's no other reason for why this could not be extended to "mux states".

Quoted 4 lines

I think the model of explicitly marking when you'd like a mux to be optional is a better and less fragile model. Who is to say that -EINVAL from some other call is, and will remain, a perfect match for the optional case you are aiming for?

-EINVAL is simply the error returned from the OF helpers when the name properties are missing. I map that to -ENOENT for consistency with index lookups (i.e. when the "mux-controls" property is missing) and that error is much less likely to be returned for other reasons.

Quoted 3 lines

Srinivas Kandagatla is looking into optional muxes as a side issue to exclusive muxes.
https://lore.kernel.org/all/[email protected]/

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 now (i.e. like is done in the TI driver looking up an optional "mux state").

Johan

#3 lore raw
Quoted 6 lines · Johan Hovold
Quoted 3 lines

Srinivas Kandagatla is looking into optional muxes as a side issue to exclusive muxes.
https://lore.kernel.org/all/[email protected]/

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.

--srini

Quoted 1 line

now (i.e. like is done in the TI driver looking up an optional "mux

#4 lore raw
Quoted 11 lines · Srinivas Kandagatla
Quoted 7 lines · Johan Hovold
Quoted 3 lines

Srinivas Kandagatla is looking into optional muxes as a side issue to exclusive muxes.
https://lore.kernel.org/all/[email protected]/

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