diff options
| author |  Serge Semin <Sergey.Semin@baikalelectronics.ru>
| 2022-06-10 13:45:00 +0300 |
|---|---|---|
| committer |  Bartosz Golaszewski <brgl@bgdev.pl>
| 2022-06-10 14:26:15 +0200 |
| commit | 77006f6edc0e0f58617eb25e53731f78641e820d (patch) | |
| tree | fd61c68597d24704c509f35886a089ef6c9ae07d /include/linux | |
| parent | Merge tag 'intel-gpio-v5.19-2' of gitolite.kernel.org:pub/scm/linux/kernel/gi... (diff) | |
| download | linux-77006f6edc0e0f58617eb25e53731f78641e820d.tar.gz linux-77006f6edc0e0f58617eb25e53731f78641e820d.tar.bz2 linux-77006f6edc0e0f58617eb25e53731f78641e820d.zip | |
gpio: dwapb: Don't print error on -EPROBE_DEFER
Currently if the APB or Debounce clocks aren't yet ready to be requested
the DW GPIO driver will correctly handle that by deferring the probe
procedure, but the error is still printed to the system log. It needlessly
pollutes the log since there was no real error but a request to postpone
the clock request procedure since the clocks subsystem hasn't been fully
initialized yet. Let's fix that by using the dev_err_probe method to print
the APB/clock request error status. It will correctly handle the deferred
probe situation and print the error if it actually happens.
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions