gpio: dwapb: Don't print error on -EPROBE_DEFER
authorSerge Semin <Sergey.Semin@baikalelectronics.ru>
Fri, 10 Jun 2022 10:45:00 +0000 (13:45 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 22 Jun 2022 12:21:58 +0000 (14:21 +0200)
commit76ac3964a22a1e3d7c39af51816a34d39ec1d167
treed9f9dedea4acc51f52943fa2dcf2378db8e6dc54
parenteeadd7db8c3fd4cddd0442a67f345837299d6372
gpio: dwapb: Don't print error on -EPROBE_DEFER

[ Upstream commit 77006f6edc0e0f58617eb25e53731f78641e820d ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/gpio/gpio-dwapb.c