From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Thu, 13 Sep 2012 15:37:23 +0000 Subject: Re: [PATCH v6 1/4] Runtime Interpreted Power Sequences Message-Id: <5051FDB3.9040008@wwwdotorg.org> List-Id: References: <1347443867-18868-1-git-send-email-acourbot@nvidia.com> <2689722.93BQTh4lSC@percival> <1347519249.7471.42.camel@lappyti> <3082244.Oec3ulPCgi@percival> In-Reply-To: <3082244.Oec3ulPCgi@percival> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alex Courbot Cc: Tomi Valkeinen , Stephen Warren , Thierry Reding , Simon Glass , Grant Likely , Rob Herring , Mark Brown , Anton Vorontsov , David Woodhouse , Arnd Bergmann , Leela Krishna Amudala , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-fbdev@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" , "linux-pm@vger.kernel.org" , "linux-doc@vger.kernel.org" On 09/13/2012 01:08 AM, Alex Courbot wrote: > On Thursday 13 September 2012 14:54:09 Tomi Valkeinen wrote: >> * PGP Signed by an unknown key >> >> On Thu, 2012-09-13 at 15:36 +0900, Alex Courbot wrote: >> >>> On Thursday 13 September 2012 14:22:57 Tomi Valkeinen wrote: >>> >>> >>> >>>> However, I fear these board specific things may be quite a bit >>>> anything, >>>> so it may well be pwm, gpios and regulators are not enough for them. >>>> For >>>> example, there could be an FPGA on the board which requires some >>>> configuration to accomplish the task at hand. It could be rather >>>> difficult to handle it with a generic power sequence. >>> >>> >>> Right. Note that this framework is supposed to be extended - I would like >>> to at least add regulator voltage setting, and maybe even support for >>> clocks and pinmux (but that might be out of place). >> >> >> Yes, that's one concern of mine... I already can imagine someone >> suggesting adding conditionals to the power sequence data. > > I took care of that when naming the feature - it is not a "sequence" anymore > if you have conditionals. :P > >> Perhaps also >> direct memory read/writes so you can twiddle registers directly. And so >> on. Where's the limit what it should contain? Can we soon write full >> drivers with the DT data? =) > > I shall be satisfied the day the kernel is released as one big DT node along > with the 5KB interpreter that runs it. I know you're joking, but *cough* OpenFirmware *cough*, right?