Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161210AbcLPQyH (ORCPT ); Fri, 16 Dec 2016 11:54:07 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:35092 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1161173AbcLPQx6 (ORCPT ); Fri, 16 Dec 2016 11:53:58 -0500 Date: Fri, 16 Dec 2016 16:53:48 +0000 From: Mark Brown To: Harald Geyer Cc: Liam Girdwood , linux-kernel@vger.kernel.org Message-ID: <20161216165348.mha6d3faucxdript@sirena.org.uk> References: <20161214181405.7hyn4b6yxdetzn5p@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cbtr2hl43urqkirr" Content-Disposition: inline In-Reply-To: X-Cookie: I represent a sardine!! User-Agent: NeoMutt/20161126 (1.7.1) X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: Question about regulator API X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2046 Lines: 50 --cbtr2hl43urqkirr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 16, 2016 at 02:41:42PM +0100, Harald Geyer wrote: > Mark Brown writes: > > On Wed, Dec 14, 2016 at 03:52:54PM +0100, Harald Geyer wrote: > > This doesn't feel like a regulator API problem exactly, a lot of what > > you're talking about here seems like you really need the devices to > > coopereate with each other and know what they're doing in order to work > > well together. > I was hoping, that I somehow could get the necessary coordination from > the regulator framework. If the best I can get ATM is notifications, then > I'll try it and see what kind of code falls out of this. > It still seems a bit of a limitation to me, that the only way to really > switch off a regulator is with regulator_force_disable(), which is quite > a hard hammer. I really have no idea what sort of communication you're envisaging here - powering supplies down when other devices are trying to use them is a really serious thing with very substantial consequences for userspace, if the devices aren't cooperating at a level higher than the regulator API level it's unlikely to go well. > This only works as long as every consumer of the supply is cooperating > (which is my personal use case but doesn't look very future proof). I guess > there has to be some pain for using quirky, unreliable HW... ;) That's going to be the case no matter what I think. --cbtr2hl43urqkirr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlhUHBsACgkQJNaLcl1U h9Djdgf/bsimmbl2mU9+a5o5UUbiMjjb8KKW7pvDSPtN8qkSBAZ5xK/XsrUaffii K8bMjbkfXzV2bZ8jAThr8I/eVkWOUyXW6EV0RHlqJKCHzKR4uelS/MSN3dEbFlfB Mzf9/9nsd3PWa7DRg0mSuXHQvgZtDRH4Igewsk5Ld63AWClykCgrpN2JBach4xVu Rx9BpUAGxlZSkeeI4wVwR88kccDP43EonHYzJnmjK4JfqWt3VTJo04nbAfYKJkM2 Lfw+SWrDOOIIMJs+wcsUlxD7K/gXGMxwS+bAkICLP4YWsC7uLwrxBKmFBnvBmpWj MIRi6+PelhWULcxQmTYwuJsOT2gFfw== =uQzq -----END PGP SIGNATURE----- --cbtr2hl43urqkirr--