Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1736309
| From | Florian Fainelli <f.fainelli@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH 0/2] pinctrl: Allow indicating loss of state across suspend/resume |
| Date | 2017-09-21 03:10 +0200 |
| Message-ID | <urYa5-2kx-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hello Linus, It's me again, so I have been thinking about the problem originally reported in: [PATCH fixes v3] pinctrl: Really force states during suspend/resume and other similar patches a while ago, and this new version allows a platform using pinctrl-single to specify whether its pins are going to lose their state during a system deep sleep. Note that this is still checked at the pinctrl_select_state() because consumers of the pinctrl API might be calling this from their suspend/resume functions and should not have to know whether the provider does lose its pin states. Thanks! Florian Fainelli (2): pinctrl: Allow a device to indicate when to force a state pinctrl: single: Allow indicating loss of pin states during low-power .../devicetree/bindings/pinctrl/pinctrl-single.txt | 4 ++++ drivers/pinctrl/core.c | 15 +++++++++++++++ drivers/pinctrl/core.h | 4 ++++ drivers/pinctrl/pinctrl-single.c | 3 +++ 4 files changed, 26 insertions(+) -- 2.14.1
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH 0/2] pinctrl: Allow indicating loss of state across suspend/resume Florian Fainelli <f.fainelli@gmail.com> - 2017-09-21 03:10 +0200
csiph-web