All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stephen Warren <swarren@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: DT support for input-supply of regulator.
Date: Sat, 19 May 2012 20:34:07 +0530	[thread overview]
Message-ID: <4FB7B667.9010606@nvidia.com> (raw)
In-Reply-To: <20120519104436.GR4039@opensource.wolfsonmicro.com>

On Saturday 19 May 2012 04:14 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Fri, May 18, 2012 at 10:19:32PM +0530, Laxman Dewangan wrote:
>
>> But when it looks for the device node containing this regulator, it
>> starts searching of the props from the dev_node of parent device
>> i.e. pmu: tps65910@d2 and in search, it does not found the
>> vin-supply property. It got property for compatible reg, gpio_cell,
>> gpio-controller and then no more property.
>> Is there any issue in laying down the regulator structure?
> I'm sorry but I'm having a really hard time parsing what you're saying
> above.  It sounds like there's some sort of device tree specific bug
> that needs fixing.
>

I found small issue in core regulator and the tps65910 regulator driver 
where it was not passing correct regulator node. After fixing this, it 
worked fine.
I already sent the patches for review.

Thanks,
Laxman



      reply	other threads:[~2012-05-19 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 16:49 DT support for input-supply of regulator Laxman Dewangan
2012-05-19 10:44 ` Mark Brown
2012-05-19 15:04   ` Laxman Dewangan [this message]

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=4FB7B667.9010606@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.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 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.