linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: Courtney Cavin <courtney.cavin@sonymobile.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Lee Jones <lee.jones@linaro.org>,
	Josh Cartwright <joshc@codeaurora.org>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: pm8x41: add support for Qualcomm 8x41 PMICs
Date: Fri, 25 Apr 2014 17:28:06 -0700	[thread overview]
Message-ID: <535AFD96.90505@gmail.com> (raw)
In-Reply-To: <1398259168.4724.217.camel@iivanov-dev>

On 4/23/2014 6:19 AM, Ivan T. Ivanov wrote:
> 
> Hi,
> 
> On Tue, 2014-04-22 at 17:31 -0700, Courtney Cavin wrote:
>> From: Josh Cartwright <joshc@codeaurora.org>
>>
>> The Qualcomm 8941 and 8841 PMICs are components used with the Snapdragon
>> 800 series SoC family.  This driver exists largely as a glue mfd component,
>> it exists to be an owner of an SPMI regmap for children devices
>> described in device tree.
>>
> 
> Thanks. This is exactly what I have planed to do :-)
> 
>> Signed-off-by: Josh Cartwright <joshc@codeaurora.org>
>> Signed-off-by: Courtney Cavin <courtney.cavin@sonymobile.com>
>> ---
>>  drivers/mfd/Kconfig  | 13 +++++++++++
>>  drivers/mfd/Makefile |  1 +
>>  drivers/mfd/pm8x41.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 77 insertions(+)
>>  create mode 100644 drivers/mfd/pm8x41.c
>>
> 
> <snip>
> 
>> +
>> +static int pm8x41_probe(struct spmi_device *sdev)
>> +{
>> +	struct regmap *regmap;
>> +
>> +	regmap = devm_regmap_init_spmi_ext(sdev, &pm8x41_regmap_config);
>> +	if (IS_ERR(regmap)) {
>> +		dev_dbg(&sdev->dev, "regmap creation failed.\n");
>> +		return PTR_ERR(regmap);
>> +	}
>> +
>> +	return of_platform_populate(sdev->dev.of_node, NULL, NULL, &sdev->dev);
> 
> I think that this will not going to work. For example in this particular
> case, both controllers have "qcom,qpnp-revid" peripheral which is
> located at offset 0x100.
> 
> And the result is:
> 
> [    0.963944] sysfs: cannot create duplicate filename '/bus/platform/devices/100.revid'

The duplicate filename error is because pm8x41_probe() is calling of_platform_populate()
directly.

If that call is removed then there is no attempt to create a revid file in
/sys/bus/platform/devices.  If I add your pm8841@4 node to my dts file, then
the 100.revid file is properly created at

  /sys/firmware/devicetree/base/soc/qcom,spmi@fc4cf000/pm8841@4/qcom,revid@100

and no attempt is made to create /sys/bus/platform/devices/100.revid

This appears to be correct to me, because I do not think revid should be created as
a platform device.

> 
> DT looks like this:
> 
> spmi {
> 	compatible = "qcom,spmi-pmic-arb";
> 	reg-names = "core", "intr", "cnfg";
> 	reg = <0xfc4cf000 0x1000>,
> 	      <0xfc4cb000 0x1000>,
> 	      <0xfc4ca000 0x1000>;
> 
> 	interrupt-names = "periph_irq";
> 	interrupts = <0 190 0>;
> 
> 	qcom,ee = <0>;
> 	qcom,channel = <0>;
> 
> 	#address-cells = <2>;
> 	#size-cells = <0>;
> 
> 	interrupt-controller;
> 	#interrupt-cells = <4>;
> 
> 	pm8941@0 {
> 		compatible = "qcom,pm8941";
> 		reg = <0x0 SPMI_USID>;
> 
> 		#address-cells = <1>;
> 		#size-cells = <0>;
> 
> 		revid@100 {
> 			compatible = "qcom,qpnp-revid";
> 			reg = <0x100 0x100>;
> 		};
> 	};
> 
> 	pm8841@4 {

        ^^^^^^^^  typo nit - that should be pm8941@4.
                  The nit does not change what you reported though.

> 		compatible = "qcom,pm8941";
> 		reg = <0x4 SPMI_USID>;
> 
> 		#address-cells = <1>;
> 		#size-cells = <0>;
> 
> 		revid@100 {
> 			compatible = "qcom,qpnp-revid";
> 			reg = <0x100 0x100>;
> 		};
> 	};
> };
> 
> Any suggestions?

Remove of_platform_populate() from pm8x41_probe().  Do you know of any
other reason it can not be removed?

-Frank

  parent reply	other threads:[~2014-04-26  0:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  0:31 [PATCH 1/2] mfd: pm8x41: add support for Qualcomm 8x41 PMICs Courtney Cavin
2014-04-23  0:31 ` [PATCH 2/2] mfd: pm8x41: document device tree bindings Courtney Cavin
2014-04-23 10:50 ` [PATCH 1/2] mfd: pm8x41: add support for Qualcomm 8x41 PMICs Lee Jones
2014-04-23 17:38   ` Courtney Cavin
2014-04-23 13:19 ` Ivan T. Ivanov
2014-04-23 18:16   ` Courtney Cavin
2014-04-23 20:34     ` Ivan T. Ivanov
2014-04-23 22:12       ` Courtney Cavin
2014-04-24  2:45   ` Rob Herring
2014-04-26  0:28   ` Frank Rowand [this message]
2014-04-26  0:40     ` Courtney Cavin
2014-04-26  0:53       ` Frank Rowand
2014-04-28  7:11     ` Ivan T. Ivanov
2014-05-07 18:35   ` Rob Herring
2014-04-23 21:46 ` Josh Cartwright
2014-04-23 23:36   ` Courtney Cavin
2014-04-24 18:18     ` Josh Cartwright
2014-05-09 12:45       ` Ivan T. Ivanov
2014-05-09 20:30         ` Courtney Cavin
2014-05-10  8:06           ` Ivan T. Ivanov
2014-04-26  1:38     ` David Collins

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=535AFD96.90505@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=courtney.cavin@sonymobile.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=iivanov@mm-sol.com \
    --cc=joshc@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sameo@linux.intel.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: 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;
as well as URLs for NNTP newsgroup(s).