From: Fabio Estevam <fabio.estevam@freescale.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Mark Brown <broonie@kernel.org>, Shawn Guo <shawn.guo@linaro.org>,
<festevam@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pfuze100-regulator: Revert "regulator: pfuze100: Use of_get_child_by_name"
Date: Tue, 18 Feb 2014 13:33:15 -0300 [thread overview]
Message-ID: <53038B4B.7020706@freescale.com> (raw)
In-Reply-To: <CAK9yfHykaoap7Dz+fsZgReRoXW_GsKvmZX7RDGqknd1_o3R50g@mail.gmail.com>
On 02/18/2014 01:28 PM, Sachin Kamat wrote:
> On 18 February 2014 21:20, Fabio Estevam <fabio.estevam@freescale.com> wrote:
>> Since commit d7857c42 (regulator: pfuze100: Use of_get_child_by_name) we get
>> the following probe failure:
>>
>> pfuze100-regulator 1-0008: Full layer: 1, Metal layer: 0
>> pfuze100-regulator 1-0008: FAB: 0, FIN: 0
>> pfuze100-regulator 1-0008: regulators node not found
>> pfuze100-regulator: probe of 1-0008 failed with error -22
>>
>> Revert the offending commit so that we can probe the regulator successfully.
>
> I wonder what is different in this case from the ones that I already
> have working
> that is causing this to fail. Can you please tell me which dts file
> you have used
> so that I can see if the way the node is defined is anything different.
The dts I am using is arch/arm/boot/dts/imx6qdl-sabresd.dtsi, and I
build imx6q-sabresd.dtb from linux-next.
Regards,
Fabio Estevam
next prev parent reply other threads:[~2014-02-18 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 15:50 [PATCH] pfuze100-regulator: Revert "regulator: pfuze100: Use of_get_child_by_name" Fabio Estevam
2014-02-18 16:28 ` Sachin Kamat
2014-02-18 16:33 ` Fabio Estevam [this message]
2014-02-19 2:12 ` Shawn Guo
2014-02-19 3:27 ` Sachin Kamat
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=53038B4B.7020706@freescale.com \
--to=fabio.estevam@freescale.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=shawn.guo@linaro.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