Re: [PATCH v1 1/4] i2c: mux: Add i2c-arbitrator 'mux' driver

[Linus Walleij <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>]

On Fri, Feb 15, 2013 at 11:24 AM, Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> wrote:
> On Thu, Feb 14, 2013 at 01:40:49PM -0800, Doug Anderson wrote:
>> On Wed, Feb 13, 2013 at 4:54 PM, Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> wrote:
>
>> ...but when I moved to module_platform_driver() then things still broke.
>
>> [    1.510000] platform-lcd supply lcd_vdd not found, using dummy regulator
>
>> I was sorta hoping that there would be some magic where
>> regulator_get() would find the device tree node for the regulator and
>> then resolve the chain.  ...but maybe that's a pipe dream.
>
> You shouldn't have dummy regulators enabled at all, that'll break a
> bunch of stuff including dependency resolution.  They're a crutch to
> help get things booting not something you should be using in production.
> If they're not enabled regulator_get() will defer the probe.

Hm, totally unrelated but Mark, should we consider marking the
kernel tainted when the dummy regulators are in use?
(And likewise for the dummy pinctrl I guess.)

We could use some TAINT_INCONSISTENT_RESOURCES
or something.

I was thinking it could help to draw attention to resolving the
platforms that stick dummy stuff in them and never get rid of
it.

But maybe this would be too rude?

Yours,
Linus Walleij