From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: lrg-l0cyMroinI0@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V1] regulator: Enable supply regulator if child rail is enabled.
Date: Mon, 2 Jan 2012 11:36:23 +0000 [thread overview]
Message-ID: <20120102113623.GC2899@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1325489925-5148-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On Mon, Jan 02, 2012 at 01:08:45PM +0530, Laxman Dewangan wrote:
> During regulator_register, the rail is set on the provided
> machine constraints and if it is enabled then it is also
> require to enable the supply regulator. This will make sure
> that:
> 1. Proper reference count for supply regulator to be maintain.
> 2. Supply regulator should be enable when given rail is enabled.
>
> Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Applied, thanks.
> When given rail is registered and if it has machine constratins to
> enable the rail then it is also require to enable the supply rail for
> a given rail. This will make sure that given rail is enabled and
> proper reference count is maintained for the supply rail to avoid
> disable of supply rail even child rail is enabled.
Why is this not in the changelog?
next prev parent reply other threads:[~2012-01-02 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 7:38 [PATCH V1] regulator: Enable supply regulator if child rail is enabled Laxman Dewangan
[not found] ` <1325489925-5148-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-02 11:36 ` Mark Brown [this message]
2012-01-02 12:07 ` Laxman Dewangan
[not found] ` <96C9D994977DD0439FB6D3FE3B13DD907DBD3A9A78-kdsAE/FnitNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-01-02 13:24 ` 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=20120102113623.GC2899@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.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;
as well as URLs for NNTP newsgroup(s).