[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2019237.rjYDPBpg0A@phil>
Date: Tue, 10 Mar 2015 13:33:23 +0100
From: Heiko Stuebner <heiko@...ech.de>
To: Mark Brown <broonie@...nel.org>
Cc: Philipp Zabel <p.zabel@...gutronix.de>,
David Airlie <airlied@...ux.ie>, djkurtz@...omium.org,
Yakir Yang <ykk@...k-chips.com>,
Fabio Estevam <fabio.estevam@...escale.com>,
dianders@...omium.org, Andy Yan <andy.yan@...k-chips.com>,
Mark Yao <mark.yao@...k-chips.com>,
linux-rockchip@...ts.infradead.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] regulator: don't emit errors in {devm_}regulator_bulk_get when defering
Am Dienstag, 10. März 2015, 12:07:50 schrieb Mark Brown:
> On Tue, Mar 10, 2015 at 12:22:06AM +0100, Heiko Stuebner wrote:
> > When {devm_}regulator_get returns -EPROBE_DEFER the driver in question
> > will
> > try probing again at a later time. So don't spam the log with failure
> > messages as this is an expected result of probe ordering.
> >
> > - dev_err(dev, "Failed to get supply '%s': %d\n",
> > - consumers[i].supply, ret);
> > + if (ret != -EPROBE_DEFER)
> > + dev_err(dev, "Failed to get supply '%s': %d\n",
> > + consumers[i].supply, ret);
>
> No, this is not good - you get a nice quiet boot even if the regulator
> does not appear which means people have no idea why the driver isn't
> loading. That's not a good user experience, silent error handling is
> the main problem I see people running into trying to get their systems
> up and running these days.
>
> Really deferred probe is just fundamentally noisy since it's
> intentionally tolerating errors like this and of course a lot of the
> noise comes from the deferral messages the core prints.
ok, I'll drop this one then
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists