linux-kernel - The use_count problem of regulator

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-next>] [day] [month] [year] [list]

Message-id: <4B56A300.7000907@samsung.com>
Date:	Wed, 20 Jan 2010 15:30:24 +0900
From:	Joonyoung Shim <jy0922.shim@...sung.com>
To:	lrg@...mlogic.co.uk, broonie@...nsource.wolfsonmicro.com
Cc:	kyungmin.park@...sung.com, mk7.kang@...sung.com,
	linux-kernel@...r.kernel.org
Subject: The use_count problem of regulator

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.
--
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/