Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1571318
| From | Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/8] power: add power sequence library |
| Date | 2017-02-01 09:10 +0100 |
| Message-ID | <t5Y9k-3lP-27@gated-at.bofh.it> (permalink) |
| References | <t5PSq-6L5-17@gated-at.bofh.it> <t5PSq-6L5-19@gated-at.bofh.it> <t5PSq-6L5-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Feb 01, 2017 at 12:10:17AM +0100, Rafael J. Wysocki wrote: > On Tue, Jan 3, 2017 at 7:33 AM, Peter Chen <peter.chen@nxp.com> wrote: > > We have an well-known problem that the device needs to do some power > > sequence before it can be recognized by related host, the typical > > example like hard-wired mmc devices and usb devices. > > > > This power sequence is hard to be described at device tree and handled by > > related host driver, so we have created a common power sequence > > library to cover this requirement. The core code has supplied > > some common helpers for host driver, and individual power sequence > > libraries handle kinds of power sequence for devices. The pwrseq > > librares always need to allocate extra instance for compatible > > string match. > > > > pwrseq_generic is intended for general purpose of power sequence, which > > handles gpios and clocks currently, and can cover other controls in > > future. The host driver just needs to call of_pwrseq_on/of_pwrseq_off > > if only one power sequence is needed, else call of_pwrseq_on_list > > /of_pwrseq_off_list instead (eg, USB hub driver). > > > > For new power sequence library, it can add its compatible string > > to pwrseq_of_match_table, then the pwrseq core will match it with > > DT's, and choose this library at runtime. > > > > Signed-off-by: Peter Chen <peter.chen@nxp.com> > > Tested-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name> > > Tested-by Joshua Clayton <stillcompiling@gmail.com> > > Reviewed-by: Matthias Kaehlcke <mka@chromium.org> > > Tested-by: Matthias Kaehlcke <mka@chromium.org> > > Quite honestly, I have a really hard time with trying to follow this > code and the total lack of documentation makes it even harder. In > particular, the generic power sequence code is not even commented at > all, so it really is hard to say how this is going to work, let alone > deciding whether or not to apply it. > > Plus, of course, the USB core changes must be acked by the maintainer > thereof for me to be able to handle the series. Ah crap, I wanted you to explain it as I too couldn't figure it out :) > But at this point I basically need you to explain the design to me, please. Same here. thanks, greg k-h
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 2/8] power: add power sequence library "Rafael J. Wysocki" <rafael@kernel.org> - 2017-02-01 00:20 +0100
Re: [PATCH 2/8] power: add power sequence library Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2017-02-01 09:10 +0100
Re: [PATCH 2/8] power: add power sequence library Peter Chen <hzpeterchen@gmail.com> - 2017-02-03 09:20 +0100
Re: [PATCH 2/8] power: add power sequence library "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2017-02-03 22:20 +0100
Re: [PATCH 2/8] power: add power sequence library Peter Chen <hzpeterchen@gmail.com> - 2017-02-04 03:00 +0100
csiph-web