All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Ni <wni@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: About [PATCH 1/2] regulator: core: Provide a dummy regulator with full constraints
Date: Tue, 8 Oct 2013 14:09:02 +0800	[thread overview]
Message-ID: <5253A17E.10503@nvidia.com> (raw)

Hi, Mark
In the latest regulator framework, it default to provide dummy
regulators with full constraints by your patch "regulator: core: Provide
a dummy regulator with full constraints".
I tried to use regulator_get() on lm90.c. If not set vcc-supply property
in the dts file to assume the regulator is physically present and
enabled, but it still can't get dummy regulator, just return -ENODEV.
I traced it, the regulator_dev_lookup() will return -ENODEV, and at that
time the has_full_constraints is still false, didn't be initialized in
regulator_init_complete() yet, so it will not return dummy regulator,
and will not return -EPROBE_DEFER either. This will cause the
lm90_probe() failed.

Could you take a look ?

Thanks.
Wei.

             reply	other threads:[~2013-10-08  6:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  6:09 Wei Ni [this message]
2013-10-08  9:09 ` About [PATCH 1/2] regulator: core: Provide a dummy regulator with full constraints Mark Brown
2013-10-08  9:46   ` Wei Ni
2013-10-12 12:14     ` Mark Brown
2013-10-16  4:36       ` Wei Ni
2013-10-16 10:39         ` Mark Brown
     [not found]           ` <20131016103942.GG2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-17  4:39             ` Wei Ni
2013-10-17  4:39               ` Wei Ni
     [not found]               ` <525F6A1B.70505-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-17  9:37                 ` Mark Brown
2013-10-17  9:37                   ` Mark Brown
     [not found]                   ` <20131017093701.GH2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-17 10:39                     ` Wei Ni
2013-10-17 10:39                       ` Wei Ni

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=5253A17E.10503@nvidia.com \
    --to=wni@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.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 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.