diff options
| author | Ronak Jain <ronak.jain@amd.com> | 2024-09-20 08:54:10 +0300 |
|---|---|---|
| committer | Michal Simek <michal.simek@amd.com> | 2024-10-02 13:51:02 +0300 |
| commit | e8415a8aecdb73cadfcfd1f1e1307d84413a5eb8 (patch) | |
| tree | aa13bc59b6f392a1079df14ecf02a3df95c3c0ef /tools/perf/scripts/python | |
| parent | f33d6099edf78e3c97900c0173fedbfecc025a9e (diff) | |
| download | linux-e8415a8aecdb73cadfcfd1f1e1307d84413a5eb8.tar.xz | |
firmware: xilinx: add a warning print for unsupported feature
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>
Link: https://lore.kernel.org/r/20240920055410.2658465-1-ronak.jain@amd.com
Signed-off-by: Michal Simek <michal.simek@amd.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions