[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240401141031.3106216-1-peng.fan@oss.nxp.com>
Date: Mon, 1 Apr 2024 22:10:31 +0800
From: "Peng Fan (OSS)" <peng.fan@....nxp.com>
To: linus.walleij@...aro.org,
brgl@...ev.pl,
linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: cristian.marussi@....com,
sudeep.holla@....com,
Peng Fan <peng.fan@....com>
Subject: [PATCH] pinctrl: pinconf-generic: check error value EOPNOTSUPP
From: Peng Fan <peng.fan@....com>
The SCMI error value SCMI_ERR_SUPPORT maps to linux error value
'-EOPNOTSUPP', so when dump configs, need check the error value
EOPNOTSUPP, otherwise there will be log "ERROR READING CONFIG SETTING".
Signed-off-by: Peng Fan <peng.fan@....com>
---
drivers/pinctrl/pinconf-generic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinconf-generic.c b/drivers/pinctrl/pinconf-generic.c
index cada5d18ffae..541c2ac9ffcb 100644
--- a/drivers/pinctrl/pinconf-generic.c
+++ b/drivers/pinctrl/pinconf-generic.c
@@ -75,7 +75,7 @@ static void pinconf_generic_dump_one(struct pinctrl_dev *pctldev,
else
ret = pin_config_get_for_pin(pctldev, pin, &config);
/* These are legal errors */
- if (ret == -EINVAL || ret == -ENOTSUPP)
+ if (ret == -EINVAL || ret == -ENOTSUPP || ret == -EOPNOTSUPP)
continue;
if (ret) {
seq_printf(s, "ERROR READING CONFIG SETTING %d ", i);
--
2.37.1
Powered by blists - more mailing lists