linux-kernel - Doubt about Regulator Framework and VBAT use case

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: <20091130104102.GA16608@esdhcp037198.research.nokia.com>
Date:	Mon, 30 Nov 2009 12:41:02 +0200
From:	Eduardo Valentin <eduardo.valentin@...ia.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	"Hogander Jouni (Nokia-D/Tampere)" <jouni.hogander@...ia.com>,
	"De-Schrijver Peter (Nokia-D/Helsinki)" 
	<Peter.De-Schrijver@...ia.com>,
	"Keski-Saari Juha.1 (EXT-Teleca/Helsinki)" 
	<ext-juha.1.keski-saari@...ia.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Doubt about Regulator Framework and VBAT use case

Hello Mark and Liam,

I'm writing to ask about VBAT use case. What is the expected
way to use regulator framework in case of rail coming from battery?
Should it be added to the regulator framework at all?

In that case, the rail should not be controllable. So I don't see
any reason to add it to the regulator framework board definitions,
as we should not be controlling it.

However, drivers for devices on that rail would require their regulator anyway.
And I guess the point would be that drivers should not be aware that they are on VBAT
or any other rail.

So, what's the correct way to solve this?

- Should drivers fail nicely if a regulator_get fail? And continue even if one fails.
- Should drivers disable regfw usage completely in the driver if regulator_get doesn't
give valid regulator ?
- or Should a fake fixed regulator be added for vbat so drivers can still get a valid
regulator with regulator_get.

The last options seams to be the one that does not require much changes on drivers.
But it will be adding a regulator that does basically nothing in the system.

BR,

-- 
Eduardo Valentin
--
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/