diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2024-12-19 20:27:33 +0100 |
|---|---|---|
| committer | Hans Verkuil <hverkuil@xs4all.nl> | 2025-02-15 15:22:37 +0100 |
| commit | c8525bd0a714e425b54d19f82bcfc95ea3b8b742 (patch) | |
| tree | 07ccdf3c84c4d74db8fda37dc0962f2aa525c551 /tools/perf/scripts/python | |
| parent | d8460548104de5cf8734afb6970477bf005e5765 (diff) | |
| download | linux-c8525bd0a714e425b54d19f82bcfc95ea3b8b742.tar.gz linux-c8525bd0a714e425b54d19f82bcfc95ea3b8b742.zip | |
media: hi556: Don't log hi556_check_hwcfg() errors twice
All hi556_check_hwcfg() error-exit paths already log a detailed reason,
logging a second generic "failed to check HW configuration" error is not
useful, and in case of the fwnode check failing with -EPROBE_DEFER this
is outright problematic flooding the log with:
[ 6.336318] hi556 i2c-INT3537:00: failed to check HW configuration: -517
[ 6.339006] hi556 i2c-INT3537:00: failed to check HW configuration: -517
[ 6.346293] hi556 i2c-INT3537:00: failed to check HW configuration: -517
[ 6.356129] hi556 i2c-INT3537:00: failed to check HW configuration: -517
[ 6.380316] hi556 i2c-INT3537:00: failed to check HW configuration: -517
etc.
The one exception to all hi556_check_hwcfg() error-exit paths already
logging an error is on v4l2_fwnode_endpoint_alloc_parse() errors.
Make hi556_check_hwcfg() log an error in that case too and drop
the duplicate "failed to check HW configuration" error logging.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=2307279
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions