diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2024-12-20 15:41:30 +0100 |
|---|---|---|
| committer | Hans Verkuil <hverkuil@xs4all.nl> | 2025-02-15 15:22:40 +0100 |
| commit | 766d952c08bddfa1a503322df6feb1396f6a7107 (patch) | |
| tree | 9bc19b0f993e2f60eb5ece46519075117192d519 /tools/perf/scripts/python | |
| parent | 4254dc1ab3b8d095cacb1e273b37d6e56bd980bd (diff) | |
| download | linux-766d952c08bddfa1a503322df6feb1396f6a7107.tar.gz linux-766d952c08bddfa1a503322df6feb1396f6a7107.zip | |
media: ov08x40: Don't log ov08x40_check_hwcfg() errors twice
All ov08x40_check_hwcfg() error-exit paths already log a detailed reason,
logging a second generic "failed to check hwcfg" error is not useful, and
in case of the fwnode check failing with -EPROBE_DEFER this is outright
problematic flooding the log with:
[ 4.557059] ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -517
[ 4.559636] ov08x40 i2c-OVTI08F4:00: failed to check hwcfg: -517
etc.
messages.
The one exception to all ov08x40_check_hwcfg() error-exit paths already
logging an error is on v4l2_fwnode_endpoint_alloc_parse() errors.
Make ov08x40_check_hwcfg() log an error in that case too and drop
the duplicate "failed to check hwcfg: %d\n" error logging.
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