On Tue, Jun 17, 2014 at 06:05:29PM +0200, Javier Martinez Canillas wrote: > On 06/17/2014 04:12 PM, Mark Brown wrote: > >> I just looked at regulator_register() and saw that it does rdev->dev.parent = > >> dev, so yes this has to be the MFD. > I noticed that many drivers set config.dev = &pdev->dev. The original Chrome OS > max77xxx driver and max77686 are two examples but others drivers do the same: Not all drivers are DT drivers that bother specifying supplies. > And also I see that mfd_add_device() calls > devm_regulator_bulk_register_supply_alias(&pdev->dev,...) so I'm confused now > about what the correct device should be... Right, but to do that you need to set those aliases up - have you done so? > > Do the regulators manage to get their supplies? > There are no current support in mainline for the devices that use the regulators > in this PMIC so I can't tell you if consumers manage to get their supplies > correctly (e.g: if regulator_dev_lookup succeeds). That's not really relevant here - I'm asking if the regulators get their own supplies rather than if anything uses them.
Attachment:
signature.asc
Description: Digital signature
