linux-kernel - Re: [PATCH v4] regulator: qcom-saw: Add support for SAW regulators

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: <20160210184327.GB13270@sirena.org.uk>
Date:	Wed, 10 Feb 2016 18:43:27 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Georgi Djakov <georgi.djakov@...aro.org>,
	Lina Iyer <lina.iyer@...aro.org>, lgirdwood@...il.com,
	andy.gross@...aro.org, linux-kernel@...r.kernel.org,
	linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v4] regulator: qcom-saw: Add support for SAW regulators

On Wed, Feb 10, 2016 at 10:36:51AM -0800, Stephen Boyd wrote:
> On 02/10, Georgi Djakov wrote:

> > The purpose of this patch it to add support for 8064. Supporting other 
> > SoCs requires just read/writing at different offsets. To handle this we
> > can convert the above defines to a table containing the offsets for each
> > SoC. I don't think these are extensive changes or do i miss something?

> In some designs we have to talk to the PMIC with SPMI
> transactions to change the mode depending on the voltages. How do
> we plan to handle that case where the regulator control is split
> between two busses, SPMI and MMIO?

Mixed control interfaces are in general a diaster with Linux, I'd
suggest remonstrating with your system designers about doing them but in
this case since it's a syscon presumably you could hang the device off
the SPMI bus in the cases where that's in use.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)