linux-kernel - RE: [PATCH V1] regulator: Enable supply regulator if child rail is enabled.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <96C9D994977DD0439FB6D3FE3B13DD907DBD3A9A78@BGMAIL01.nvidia.com>
Date:	Mon, 2 Jan 2012 17:37:04 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"lrg@...com" <lrg@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: RE: [PATCH V1] regulator: Enable supply regulator if child rail is
 enabled.

> From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
> Sent: Monday, January 02, 2012 5:06 PM
> > 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@...dia.com>
> 
> 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?
I think this is in just different wording for explaining the change.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/