From: Mark Brown <broonie@kernel.org> To: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Cc: Lee Jones <lee.jones@linaro.org>, Samuel Ortiz <sameo@linux.intel.com>, Mike Turquette <mturquette@linaro.org>, Liam Girdwood <lgirdwood@gmail.com>, Alessandro Zummo <a.zummo@towertech.it>, Kukjin Kim <kgene.kim@samsung.com>, Doug Anderson <dianders@chromium.org>, Olof Johansson <olof@lixom.net>, Sjoerd Simons <sjoerd.simons@collabora.co.uk>, Daniel Stone <daniels@collabora.com>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, Krzysztof Kozlowski <k.kozlowski@samsung.com>, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 07/10] regulator: Add driver for Maxim 77802 PMIC regulators Date: Sat, 21 Jun 2014 21:40:26 +0100 [thread overview] Message-ID: <20140621204026.GH22657@sirena.org.uk> (raw) In-Reply-To: <53A06749.1010606@collabora.co.uk> [-- Attachment #1: Type: text/plain, Size: 1107 bytes --] 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 #2: Digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 07/10] regulator: Add driver for Maxim 77802 PMIC regulators Date: Sat, 21 Jun 2014 21:40:26 +0100 [thread overview] Message-ID: <20140621204026.GH22657@sirena.org.uk> (raw) In-Reply-To: <53A06749.1010606@collabora.co.uk> 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140621/3900a496/attachment.sig>
next prev parent reply other threads:[~2014-06-21 20:41 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-16 18:02 [PATCH v2 00/10] Add Maxim 77802 PMIC support Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 01/10] mfd: max77686: Convert to use regmap_irq Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-17 20:32 ` Lee Jones 2014-06-17 20:32 ` Lee Jones 2014-06-17 20:57 ` Doug Anderson 2014-06-17 20:57 ` Doug Anderson 2014-06-17 20:57 ` Doug Anderson 2014-06-18 9:21 ` Javier Martinez Canillas 2014-06-18 9:21 ` Javier Martinez Canillas 2014-06-18 9:21 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 02/10] clk: max77686: add DT include for MAX77686 PMIC clock Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 03/10] Documentation: dt: improve Maxim 77686 PMIC clocks binding Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 04/10] clk: Add generic driver for Maxim PMIC clocks Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 05/10] clk: max77686: convert to the generic max clock driver Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 06/10] mfd: Add driver for Maxim 77802 Power Management IC Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 19:27 ` Mark Brown 2014-06-16 19:27 ` Mark Brown 2014-06-17 10:57 ` Javier Martinez Canillas 2014-06-17 10:57 ` Javier Martinez Canillas 2014-06-18 8:32 ` Lee Jones 2014-06-18 8:32 ` Lee Jones 2014-06-18 9:50 ` Javier Martinez Canillas 2014-06-18 9:50 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 07/10] regulator: Add driver for Maxim 77802 PMIC regulators Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 19:25 ` Mark Brown 2014-06-16 19:25 ` Mark Brown 2014-06-17 10:49 ` Javier Martinez Canillas 2014-06-17 10:49 ` Javier Martinez Canillas 2014-06-17 10:49 ` Javier Martinez Canillas 2014-06-17 14:12 ` Mark Brown 2014-06-17 14:12 ` Mark Brown 2014-06-17 16:05 ` Javier Martinez Canillas 2014-06-17 16:05 ` Javier Martinez Canillas 2014-06-21 20:40 ` Mark Brown [this message] 2014-06-21 20:40 ` Mark Brown 2014-06-23 9:28 ` Javier Martinez Canillas 2014-06-23 9:28 ` Javier Martinez Canillas 2014-06-23 9:47 ` Mark Brown 2014-06-23 9:47 ` Mark Brown 2014-06-23 9:47 ` Mark Brown 2014-06-24 16:43 ` Javier Martinez Canillas 2014-06-24 16:43 ` Javier Martinez Canillas 2014-06-17 21:17 ` Lee Jones 2014-06-17 21:17 ` Lee Jones 2014-06-17 21:17 ` Lee Jones 2014-06-18 9:47 ` Javier Martinez Canillas 2014-06-18 9:47 ` Javier Martinez Canillas 2014-06-18 14:10 ` Lee Jones 2014-06-18 14:10 ` Lee Jones 2014-06-19 13:32 ` Alessandro Zummo 2014-06-19 13:32 ` Alessandro Zummo 2014-06-16 18:02 ` [PATCH v2 08/10] clk: Add driver for Maxim 77802 PMIC clocks Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 09/10] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas 2014-06-16 18:02 ` [PATCH v2 10/10] ARM: dts: Add max77802 device node for exynos5420-peach-pit Javier Martinez Canillas 2014-06-16 18:02 ` Javier Martinez Canillas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20140621204026.GH22657@sirena.org.uk \ --to=broonie@kernel.org \ --cc=a.zummo@towertech.it \ --cc=daniels@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=javier.martinez@collabora.co.uk \ --cc=k.kozlowski@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=lee.jones@linaro.org \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mturquette@linaro.org \ --cc=olof@lixom.net \ --cc=sameo@linux.intel.com \ --cc=sjoerd.simons@collabora.co.uk \ --cc=tomeu.vizoso@collabora.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.