pt., 18 sty 2019 o 19:01 Mark Brown <broonie@xxxxxxxxxx> napisał(a):
>
> On Fri, Jan 18, 2019 at 02:42:39PM +0100, Bartosz Golaszewski wrote:
>
> > Add regulator support for max77650. We support all four variants of this
> > PMIC including non-linear voltage table for max77651 SBB1 rail.
>
> Looks good, the ramping stuff might be a candidate for core (TBH I was
> sure we'd got that implemented already but we don't seem to) but that
> can be done later and the more complex one with non-linear steps does
> feel like it might have to stay in the driver anyway.
>
> A couple of small nits:
>
> > +++ b/drivers/regulator/max77650-regulator.c
> > @@ -0,0 +1,537 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Copyright (C) 2018 BayLibre SAS
> > + * Author: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx>
>
> Please make the entire header C++ style so it looks more intentional.
>
Seems like there are more files in the kernel source using the mixed
comment style for the SPDX identifier and I also prefer it over C++
only. Would you mind if it stayed that way?
> > + for_each_child_of_node(dev->of_node, child) {
> > + if (!of_node_name_eq(child, rdesc->desc.name))
> > + continue;
> > +
> > + init_data = of_get_regulator_init_data(dev, child,
> > + &rdesc->desc);
> > + if (!init_data)
> > + return -ENOMEM;
> > +
> > + config.of_node = child;
> > + config.init_data = init_data;
> > + }
>
> You don't need to do this, the core will do it for you (it will actually
> still do it even with the above, it'll only fall back to using
> config->init_data if it's own lookup fails).
I added this loop specifically because the core would not pick up the
init data from DT. What did I miss (some specific variable to assign)?
I just noticed some other drivers do the same and thought it's the
right thing to do.
Thanks,
Bart
