From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF Date: Wed, 25 Jan 2017 18:49:49 +0000 Message-ID: <20170125184949.x2wkoo7kbaaajkjk@sirena.org.uk> References: <20170125000641.25520-1-furquan@chromium.org> <20170125124911.dxveow7bo3zw5jcc@sirena.org.uk> <20170125182319.GB25470@leverpostej> <20170125182955.uznr5ehpx4dabcon@sirena.org.uk> <20170125183420.GC25470@leverpostej> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="m2wbrdgsmguypckw" Return-path: Content-Disposition: inline In-Reply-To: <20170125183420.GC25470@leverpostej> Sender: linux-kernel-owner@vger.kernel.org To: Mark Rutland Cc: Furquan Shaikh , "Rafael J. Wysocki" , "Rafael J . Wysocki" , Liam Girdwood , Tony Lindgren , Dmitry Torokhov , Len Brown , Greg Kroah-Hartman , Lorenzo Pieralisi , Hanjun Guo , Will Deacon , Rob Herring , Sathyanarayana Nujella , Heikki Krogerus , Adam Thomson , Linus Walleij , Alexandre Courbot , linux-gpio@vger.kernel.org, ACPI List-Id: linux-acpi@vger.kernel.org --m2wbrdgsmguypckw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 25, 2017 at 06:34:20PM +0000, Mark Rutland wrote: > On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote: > > > Mark, this was added in this cycle; can we please rip that out for now? > > If it's instantiated directly we probably should. > I think that given the larger problem that needs to be addressed here, > and how the us of DSD properties muddies the water, it would be > preferable to remove it until we have some consensus. Can you send a patch with a writeup please? > > I think there's a reasonable chance that any ACPI specs could be written > > in such a way as to allow transparent support in Linux, the main thing > > I'd worry about is naming issues. > I think it's certainly possible to handle this so that drivers don't > largely have to care. I also think there is some massaging the needs to > be done (e.g. tables of names or some indirection for ACPI/DT > differences), and a unified API that tries to completely hide that is > not truly possible. Given how little consumers can assume about what they'll be allowed/able to do on a given system the naming should be about it - if anything else leaks through I'd be a bit worried. --m2wbrdgsmguypckw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAliI80wACgkQJNaLcl1U h9BWHAf/chblqjRrhy7ISRo+p8FnYmmOXh2WvjIeJfrJdeK3R8er0Q/Ig66UTU/t bMfB4/P2RSyc8rhoyg2InpjhQYzTkBOt/r+XVROCHs0qLQppyUYzlWH8OXcTGG8M kQ+LwJl77KNkGbCCFFmRxii4+0rpNaeKJHJidR+W5ffSUb/v60A3n2OhKGRIuOaV N/cdDUIPH1e4W1k9IWAlZWUmxIcVoqkZVZ5Lqoz0REfuqXLJPE8Iy3osk2iipDcd UYxZrbE43m0zxUBb74Pb4V7ff5Kaqst3zXVeHqXPjxv8/gzbMg2IfXUGRNHdBEbV pu14fLSXYIjU+gqarybtSDQjfNzE8w== =LoTK -----END PGP SIGNATURE----- --m2wbrdgsmguypckw-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752327AbdAYSuR (ORCPT ); Wed, 25 Jan 2017 13:50:17 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:41212 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751925AbdAYSuP (ORCPT ); Wed, 25 Jan 2017 13:50:15 -0500 Date: Wed, 25 Jan 2017 18:49:49 +0000 From: Mark Brown To: Mark Rutland Cc: Furquan Shaikh , "Rafael J. Wysocki" , "Rafael J . Wysocki" , Liam Girdwood , Tony Lindgren , Dmitry Torokhov , Len Brown , Greg Kroah-Hartman , Lorenzo Pieralisi , Hanjun Guo , Will Deacon , Rob Herring , Sathyanarayana Nujella , Heikki Krogerus , Adam Thomson , Linus Walleij , Alexandre Courbot , linux-gpio@vger.kernel.org, ACPI Devel Maling List , Linux Kernel Mailing List , Linux OMAP Mailing List , Aaron Durbin , dlaurie@chromium.org Message-ID: <20170125184949.x2wkoo7kbaaajkjk@sirena.org.uk> References: <20170125000641.25520-1-furquan@chromium.org> <20170125124911.dxveow7bo3zw5jcc@sirena.org.uk> <20170125182319.GB25470@leverpostej> <20170125182955.uznr5ehpx4dabcon@sirena.org.uk> <20170125183420.GC25470@leverpostej> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="m2wbrdgsmguypckw" Content-Disposition: inline In-Reply-To: <20170125183420.GC25470@leverpostej> X-Cookie: A man's best friend is his dogma. 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: [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF 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 --m2wbrdgsmguypckw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 25, 2017 at 06:34:20PM +0000, Mark Rutland wrote: > On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote: > > > Mark, this was added in this cycle; can we please rip that out for now? > > If it's instantiated directly we probably should. > I think that given the larger problem that needs to be addressed here, > and how the us of DSD properties muddies the water, it would be > preferable to remove it until we have some consensus. Can you send a patch with a writeup please? > > I think there's a reasonable chance that any ACPI specs could be written > > in such a way as to allow transparent support in Linux, the main thing > > I'd worry about is naming issues. > I think it's certainly possible to handle this so that drivers don't > largely have to care. I also think there is some massaging the needs to > be done (e.g. tables of names or some indirection for ACPI/DT > differences), and a unified API that tries to completely hide that is > not truly possible. Given how little consumers can assume about what they'll be allowed/able to do on a given system the naming should be about it - if anything else leaks through I'd be a bit worried. --m2wbrdgsmguypckw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAliI80wACgkQJNaLcl1U h9BWHAf/chblqjRrhy7ISRo+p8FnYmmOXh2WvjIeJfrJdeK3R8er0Q/Ig66UTU/t bMfB4/P2RSyc8rhoyg2InpjhQYzTkBOt/r+XVROCHs0qLQppyUYzlWH8OXcTGG8M kQ+LwJl77KNkGbCCFFmRxii4+0rpNaeKJHJidR+W5ffSUb/v60A3n2OhKGRIuOaV N/cdDUIPH1e4W1k9IWAlZWUmxIcVoqkZVZ5Lqoz0REfuqXLJPE8Iy3osk2iipDcd UYxZrbE43m0zxUBb74Pb4V7ff5Kaqst3zXVeHqXPjxv8/gzbMg2IfXUGRNHdBEbV pu14fLSXYIjU+gqarybtSDQjfNzE8w== =LoTK -----END PGP SIGNATURE----- --m2wbrdgsmguypckw--