From: Joonyoung Shim <jy0922.shim@samsung.com>
To: lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com
Cc: kyungmin.park@samsung.com, mk7.kang@samsung.com,
linux-kernel@vger.kernel.org
Subject: The use_count problem of regulator
Date: Wed, 20 Jan 2010 15:30:24 +0900 [thread overview]
Message-ID: <4B56A300.7000907@samsung.com> (raw)
Hi, all.
I have one simple question.
In the regulator framework, if the regulator is enabled for example by
boot_on constraint, when regulator_get is called at the driver probe
function, the use_count of struct regulator_dev is zero. But if
regulator_has_full_constraints() is used, even though above the
regulator is using, it is disabled by regulator_init_complete() because
the use_count is zero.
Of course, we can use regulator_get_exclusive instead of regulator_get,
but if the regulator can be shared, i think this will be a problem.
Thanks.
next reply other threads:[~2010-01-20 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 6:30 Joonyoung Shim [this message]
2010-01-20 10:35 ` The use_count problem of regulator Mark Brown
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=4B56A300.7000907@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=mk7.kang@samsung.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.