[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdKxRGrmqPDTugVNrc3i_JDyEdJ6gmjyH=t9OiRTGg+AA@mail.gmail.com>
Date: Fri, 17 Apr 2020 23:50:37 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Dmitry Osipenko <digetx@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Jonathan Cameron <jic23@...nel.org>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
linux-iio <linux-iio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] iio: magnetometer: ak8974: Silence deferred-probe error
On Fri, Apr 17, 2020 at 11:49 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Fri, Apr 17, 2020 at 7:24 PM Dmitry Osipenko <digetx@...il.com> wrote:
> >
> > It's not uncommon that voltage regulator becomes available later during
> > kernel's boot process. This patch adds info message about unavailable
> > regulators in a case of the deferred-probe error and also amends the
> > error message with a error code.
>
>
> > + if (ret == -EPROBE_DEFER)
>
> > + dev_info(&i2c->dev,
> > + "regulators unavailable, deferring probe\n");
>
> I dunno why you think it is worth to spam log with this?
> This message will be printed as many times as driver got deferred
> probe cycle (maybe dozens in worst case).
As you may see in other drivers we usually have the opposite check and
print error message in case of != EPROBE_DEFER.
>
> > + else
> > + dev_err(&i2c->dev, "cannot get regulators: %d\n", ret);
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists