From: Michal Simek <michal.simek@amd.com>
To: Ronak Jain <ronak.jain@amd.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: xilinx: add a warning print for unsupported feature
Date: Wed, 2 Oct 2024 12:54:26 +0200 [thread overview]
Message-ID: <7bdbdd0e-9fcd-4f41-8352-18a98161f048@amd.com> (raw)
In-Reply-To: <20240920055410.2658465-1-ronak.jain@amd.com>
On 9/20/24 07:54, Ronak Jain wrote:
> As per the current code base, feature check API is used to check the
> version in zynqmp_pm_pinctrl_set_config() before requesting the
> firmware, and if the expected version is not found then it will
> return an error. So now when the latest kernel tries to access the
> tri-state functionality with older firmware, observe failure prints
> during booting.
>
> The failure prints,
> [ 1.204850] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: failed to set: pin 37 param 2 value 0
> [ 2.699455] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: failed to set: pin 44 param 2 value 0
> [ 2.708424] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: failed to set: pin 46 param 2 value 0
> [ 2.717387] zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: failed to set: pin 48 param 2 value 0
>
> Now, these error prints mislead the user whether it is an actual
> failure or the feature itself is not there in the firmware. So, just
> to avoid confusion around this, add some debug prints before
> returning an error code. With that, it is easier to know whether it is
> an actual failure or the feature is unsupported.
>
> Signed-off-by: Ronak Jain <ronak.jain@amd.com>
> ---
> drivers/firmware/xilinx/zynqmp.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c
> index 0b2ad46c8bce..cdb565c41119 100644
> --- a/drivers/firmware/xilinx/zynqmp.c
> +++ b/drivers/firmware/xilinx/zynqmp.c
> @@ -1245,8 +1245,11 @@ int zynqmp_pm_pinctrl_set_config(const u32 pin, const u32 param,
> if (pm_family_code == ZYNQMP_FAMILY_CODE &&
> param == PM_PINCTRL_CONFIG_TRI_STATE) {
> ret = zynqmp_pm_feature(PM_PINCTRL_CONFIG_PARAM_SET);
> - if (ret < PM_PINCTRL_PARAM_SET_VERSION)
> + if (ret < PM_PINCTRL_PARAM_SET_VERSION) {
> + pr_warn("The requested pinctrl feature is not supported in the current firmware.\n"
> + "Expected firmware version is 2023.1 and above for this feature to work.\r\n");
> return -EOPNOTSUPP;
> + }
> }
>
> return zynqmp_pm_invoke_fn(PM_PINCTRL_CONFIG_PARAM_SET, NULL, 3, pin, param, value);
Applied.
M
prev parent reply other threads:[~2024-10-02 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 5:54 Ronak Jain
2024-10-02 10:54 ` Michal Simek [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=7bdbdd0e-9fcd-4f41-8352-18a98161f048@amd.com \
--to=michal.simek@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ronak.jain@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®