From: Mark Brown <broonie@kernel.org> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Cc: Mark Rutland <mark.rutland@arm.com>, Furquan Shaikh <furquan@chromium.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Rafael J . Wysocki" <rjw@rjwysocki.net>, Liam Girdwood <lgirdwood@gmail.com>, Tony Lindgren <tony@atomide.com>, Dmitry Torokhov <dmitry.torokhov@gmail.com>, Len Brown <lenb@kernel.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Hanjun Guo <hanjun.guo@linaro.org>, Will Deacon <will.deacon@arm.com>, Rob Herring <robh@kernel.org>, Sathyanarayana Nujella <sathyanarayana.nujella@intel.com>, Heikki Krogerus <heikki.krogerus@linux.intel.com>, Adam Thomson <Adam.Thomson.Opensource@diasemi.com>, Linus Walleij <linus.walleij@linaro.org>, Alexandre Courbot <gnurou@gmail.com>, linux-gpio@vger.kernel.orgACPI Devel Maling List <lin> Subject: Re: [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF Date: Wed, 25 Jan 2017 20:40:53 +0000 [thread overview] Message-ID: <20170125204053.st2ce7wfjttnk65k@sirena.org.uk> (raw) In-Reply-To: <20170125192135.GA8605@red-moon> [-- Attachment #1: Type: text/plain, Size: 1020 bytes --] On Wed, Jan 25, 2017 at 07:21:35PM +0000, Lorenzo Pieralisi wrote: > On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote: > > 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 that the difference between ACPI and DT firmware models, > in particular in relation to power states handling (and what piece > of SW is in charge of power management) is significant and goes beyond > naming conventions, therefore the code (and reasoning behind it - ie > to have an identical driver interface to a completely different FW > model) in this series is just not acceptable, that's a plain shortcut. > We will see how this should be implemented in ACPI, not with this > code (and FW bindings). Oh, absolutely - what I'm saying is that once that's done I'd expect implementing it to be almost entirely a regulator core change in the same way that implementing DT support was. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> Cc: Mark Rutland <mark.rutland@arm.com>, Furquan Shaikh <furquan@chromium.org>, "Rafael J. Wysocki" <rafael@kernel.org>, "Rafael J . Wysocki" <rjw@rjwysocki.net>, Liam Girdwood <lgirdwood@gmail.com>, Tony Lindgren <tony@atomide.com>, Dmitry Torokhov <dmitry.torokhov@gmail.com>, Len Brown <lenb@kernel.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Hanjun Guo <hanjun.guo@linaro.org>, Will Deacon <will.deacon@arm.com>, Rob Herring <robh@kernel.org>, Sathyanarayana Nujella <sathyanarayana.nujella@intel.com>, Heikki Krogerus <heikki.krogerus@linux.intel.com>, Adam Thomson <Adam.Thomson.Opensource@diasemi.com>, Linus Walleij <linus.walleij@linaro.org>, Alexandre Courbot <gnurou@gmail.com>, linux-gpio@vger.kernel.org, ACPI Devel Maling List <linux-acpi@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux OMAP Mailing List <linux-omap@vger.kernel.org>, Aaron Durbin <adurbin@chromium.org>, dlaurie@chromium.org Subject: Re: [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF Date: Wed, 25 Jan 2017 20:40:53 +0000 [thread overview] Message-ID: <20170125204053.st2ce7wfjttnk65k@sirena.org.uk> (raw) In-Reply-To: <20170125192135.GA8605@red-moon> [-- Attachment #1: Type: text/plain, Size: 1020 bytes --] On Wed, Jan 25, 2017 at 07:21:35PM +0000, Lorenzo Pieralisi wrote: > On Wed, Jan 25, 2017 at 06:29:55PM +0000, Mark Brown wrote: > > 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 that the difference between ACPI and DT firmware models, > in particular in relation to power states handling (and what piece > of SW is in charge of power management) is significant and goes beyond > naming conventions, therefore the code (and reasoning behind it - ie > to have an identical driver interface to a completely different FW > model) in this series is just not acceptable, that's a plain shortcut. > We will see how this should be implemented in ACPI, not with this > code (and FW bindings). Oh, absolutely - what I'm saying is that once that's done I'd expect implementing it to be almost entirely a regulator core change in the same way that implementing DT support was. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-01-25 20:40 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-25 0:06 [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF Furquan Shaikh 2017-01-25 0:06 ` [PATCH 1/7] drivers/regulator: Rename of_map_mode to map_mode in regulator desc Furquan Shaikh 2017-01-25 0:06 ` [PATCH 2/7] ACPI / property: have acpi_get_next_subnode take fwnode_handle Furquan Shaikh 2017-01-25 0:06 ` Furquan Shaikh 2017-01-25 11:00 ` kbuild test robot 2017-01-25 11:00 ` kbuild test robot 2017-01-25 0:06 ` [PATCH 3/7] device property: introduce fwnode_for_each_child() Furquan Shaikh 2017-01-25 0:06 ` Furquan Shaikh 2017-01-25 0:06 ` [PATCH 4/7] device property: introduce fwnode_get_named_child_node() Furquan Shaikh 2017-01-25 0:06 ` Furquan Shaikh 2017-01-25 0:06 ` [PATCH 5/7] device property: Export dev_fwnode Furquan Shaikh 2017-01-25 0:06 ` [PATCH 6/7] drivers/gpio: Add and export gpiod_lookup[_index] Furquan Shaikh 2017-01-25 0:06 ` Furquan Shaikh 2017-01-25 11:18 ` kbuild test robot 2017-01-25 11:18 ` kbuild test robot 2017-01-26 15:24 ` Linus Walleij 2017-01-26 15:24 ` Linus Walleij 2017-01-25 0:06 ` [PATCH 7/7] drivers/regulator: Initialize regulator init data for ACPI regulators Furquan Shaikh 2017-01-25 12:29 ` [PATCH 0/7] Implement generic regulator constraints parsing for ACPI and OF Lorenzo Pieralisi 2017-01-25 12:49 ` Mark Brown 2017-01-25 12:49 ` Mark Brown 2017-01-25 12:55 ` Rafael J. Wysocki 2017-01-25 12:55 ` Rafael J. Wysocki 2017-01-25 16:56 ` Furquan Shaikh 2017-01-25 16:56 ` Furquan Shaikh 2017-01-25 18:23 ` Mark Rutland 2017-01-25 18:23 ` Mark Rutland 2017-01-25 18:29 ` Mark Brown 2017-01-25 18:29 ` Mark Brown 2017-01-25 18:34 ` Mark Rutland 2017-01-25 18:34 ` Mark Rutland 2017-01-25 18:49 ` Mark Brown 2017-01-25 18:49 ` Mark Brown 2017-01-25 19:39 ` Mark Rutland 2017-01-25 19:39 ` Mark Rutland 2017-01-25 18:44 ` Dmitry Torokhov 2017-01-25 18:44 ` Dmitry Torokhov 2017-01-25 19:27 ` Dmitry Torokhov 2017-01-25 19:27 ` Dmitry Torokhov 2017-01-25 20:39 ` Mark Brown 2017-01-25 20:39 ` Mark Brown 2017-01-25 21:17 ` Dmitry Torokhov 2017-01-25 21:17 ` Dmitry Torokhov 2017-01-25 21:30 ` Mark Brown 2017-01-25 21:30 ` Mark Brown 2017-01-25 22:05 ` Dmitry Torokhov 2017-01-25 22:05 ` Dmitry Torokhov 2017-01-25 22:25 ` Mark Brown 2017-01-25 22:25 ` Mark Brown 2017-01-25 21:44 ` Al Stone 2017-01-25 21:44 ` Al Stone 2017-01-25 23:27 ` Dmitry Torokhov 2017-01-25 23:27 ` Dmitry Torokhov 2017-01-26 0:15 ` Al Stone 2017-01-26 0:15 ` Al Stone 2017-01-26 0:33 ` Dmitry Torokhov 2017-01-26 0:33 ` Dmitry Torokhov 2017-01-26 10:35 ` Rafael J. Wysocki 2017-01-26 10:35 ` Rafael J. Wysocki 2017-02-04 16:08 ` Mark Brown 2017-02-04 16:08 ` Mark Brown 2017-01-25 19:21 ` Lorenzo Pieralisi 2017-01-25 19:21 ` Lorenzo Pieralisi 2017-01-25 20:40 ` Mark Brown [this message] 2017-01-25 20:40 ` Mark Brown 2017-01-25 18:25 ` Mark Brown 2017-01-25 18:25 ` Mark Brown
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20170125204053.st2ce7wfjttnk65k@sirena.org.uk \ --to=broonie@kernel.org \ --cc=Adam.Thomson.Opensource@diasemi.com \ --cc=dmitry.torokhov@gmail.com \ --cc=furquan@chromium.org \ --cc=gnurou@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=hanjun.guo@linaro.org \ --cc=heikki.krogerus@linux.intel.com \ --cc=lenb@kernel.org \ --cc=lgirdwood@gmail.com \ --cc=linus.walleij@linaro.org \ --cc=linux-gpio@vger.kernel.orgACPI \ --cc=lorenzo.pieralisi@arm.com \ --cc=mark.rutland@arm.com \ --cc=rafael@kernel.org \ --cc=rjw@rjwysocki.net \ --cc=robh@kernel.org \ --cc=sathyanarayana.nujella@intel.com \ --cc=tony@atomide.com \ --cc=will.deacon@arm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.