[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Apr 2024 13:44:50 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: "Peng Fan (OSS)" <peng.fan@....nxp.com>
Cc: brgl@...ev.pl, linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
cristian.marussi@....com, sudeep.holla@....com, Peng Fan <peng.fan@....com>
Subject: Re: [PATCH] pinctrl: pinconf-generic: check error value EOPNOTSUPP
On Mon, Apr 1, 2024 at 4:02 PM Peng Fan (OSS) <peng.fan@....nxp.com> wrote:
> 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>
(...)
> 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)
TBH it's a bit odd to call an in-kernel API such as pin_config_get_for_pin()
and get -EOPNOTSUPP back. But it's not like I care a lot, so patch applied.
Yours,
Linus Walleij
Powered by blists - more mailing lists