From: Mark Brown <broonie@kernel.org>
To: Keerthy <a0393675@ti.com>
Cc: Keerthy <j-keerthy@ti.com>,
lgirdwood@gmail.com, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com
Subject: Re: [PATCH 3/3] regulator: lp873x: Add support for lp873x PMIC regulators
Date: Fri, 6 May 2016 13:02:06 +0100 [thread overview]
Message-ID: <20160506120206.GO6292@sirena.org.uk> (raw)
In-Reply-To: <572C20EC.7000706@ti.com>
[-- Attachment #1: Type: text/plain, Size: 458 bytes --]
On Fri, May 06, 2016 at 10:13:24AM +0530, Keerthy wrote:
> I am using of_platform_populate function in the mfd driver to create
> platform devices for the child nodes, in my case regulators.
> of_platform_populate in turn calls on to of_platform_bus_create which
> mandates compatible properties. It quietly skips device creation if there
> are no compatible properties.
You shouldn't be using that, you should just have a table of subdevices
in the MFD.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-06 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 5:10 [PATCH 0/3] mfd: lp873x: Add lp873x PMIC support Keerthy
2016-05-05 5:10 ` [PATCH 1/3] Documentation: mfd/regulator: LP873X: Add information for the mfd and regulator drivers Keerthy
2016-05-05 5:10 ` [PATCH] mfd: lp873x: Add lp873x PMIC support Keerthy
2016-05-05 8:35 ` Manish Badarkhe
2016-05-06 4:08 ` Keerthy
2016-05-05 5:10 ` [PATCH 3/3] regulator: lp873x: Add support for lp873x PMIC regulators Keerthy
2016-05-05 15:38 ` Mark Brown
2016-05-06 4:43 ` Keerthy
2016-05-06 12:02 ` Mark Brown [this message]
2016-05-06 12:36 ` Keerthy
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=20160506120206.GO6292@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a0393675@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®