From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] reset: Consumers to explicitly request 'exclusive' or 'shared' lines
Date: Mon, 6 Jun 2016 16:56:48 +0100 [thread overview]
Message-ID: <20160606155655.10860-1-lee.jones@linaro.org> (raw)
Phasing out generic reset line requests enables us to make some better
decisions on when and how to (de)assert said lines. If an 'exclusive'
line is requested, we know a device *requires* a reset and that it's
preferable to act upon a request right away. However, if a 'shared'
reset line is requested, we can reasonably assume sure that placing a
device into reset isn't a hard requirement, but probably a measure to
save power and is thus able to cope with not being asserted if another
device is still in use.
In order allow gentle adoption and not to forcing all consumers to
move to the API immediately, causing administration headache between
subsystems, this patch adds some temporary stand-in shim-calls. This
will ease the burden at merge time and allow subsystems to migrate over
to the new API in a more realistic time-frame.
Lee Jones (7):
reset: Reorder inline reset_control_get*() wrappers
reset: Ensure drivers are explicit when requesting reset lines
reset: Supply *_shared variant calls when using of_* API
reset: Supply *_shared variant calls when using *_optional APIs
reset: TRIVIAL: Add line break at same place for similar APIs
phy: miphy28lp: Inform the reset framework that our reset line may be
shared
usb: dwc3: st: Inform the reset framework that our reset line may be
shared
drivers/phy/phy-miphy28lp.c | 3 +-
drivers/usb/dwc3/dwc3-st.c | 6 +-
include/linux/reset.h | 211 +++++++++++++++++++++++++++++++++++---------
3 files changed, 173 insertions(+), 47 deletions(-)
--
2.8.3
next reply other threads:[~2016-06-06 15:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 15:56 Lee Jones [this message]
2016-06-06 15:56 ` [PATCH 1/7] reset: Reorder inline reset_control_get*() wrappers Lee Jones
2016-06-20 12:07 ` Philipp Zabel
2016-06-06 15:56 ` [PATCH 2/7] reset: Ensure drivers are explicit when requesting reset lines Lee Jones
2016-06-06 15:56 ` [PATCH 3/7] reset: Supply *_shared variant calls when using of_* API Lee Jones
2016-06-06 15:56 ` [PATCH 4/7] reset: Supply *_shared variant calls when using *_optional APIs Lee Jones
2016-06-28 8:56 ` Lee Jones
2016-06-29 7:48 ` Philipp Zabel
2016-06-29 8:06 ` Lee Jones
2016-06-29 9:23 ` Philipp Zabel
2016-06-29 9:37 ` Lee Jones
2016-06-29 21:57 ` Philipp Zabel
2016-06-06 15:56 ` [PATCH 5/7] reset: TRIVIAL: Add line break at same place for similar APIs Lee Jones
2016-06-06 15:56 ` [PATCH 6/7] phy: miphy28lp: Inform the reset framework that our reset line may be shared Lee Jones
2016-06-07 8:37 ` [STLinux Kernel] " Peter Griffin
2016-06-07 8:59 ` Kishon Vijay Abraham I
2016-06-28 7:55 ` Lee Jones
2016-06-06 15:56 ` [PATCH 7/7] usb: dwc3: st: " Lee Jones
2016-06-06 17:08 ` [PATCH 8/10] phy: phy-stih407-usb: " Lee Jones
2016-06-06 17:08 ` [PATCH 9/10] usb: host: ehci-st: " Lee Jones
2016-06-06 17:44 ` Alan Stern
2016-06-28 7:58 ` Lee Jones
2016-06-28 8:01 ` Lee Jones
2016-06-07 8:36 ` [STLinux Kernel] " Peter Griffin
2016-06-06 17:08 ` [PATCH 10/10] usb: host: ohci-st: " Lee Jones
2016-06-07 8:36 ` [STLinux Kernel] [PATCH 8/10] phy: phy-stih407-usb: " Peter Griffin
2016-06-07 9:00 ` Kishon Vijay Abraham I
2016-06-07 8:36 ` [STLinux Kernel] [PATCH 7/7] usb: dwc3: st: " Peter Griffin
2016-06-16 9:03 ` Philipp Zabel
2016-06-28 9:27 ` [PATCH 1/1] " Lee Jones
2016-06-29 6:33 ` Felipe Balbi
2016-06-07 8:42 ` [STLinux Kernel] [PATCH 0/7] reset: Consumers to explicitly request 'exclusive' or 'shared' lines Peter Griffin
2016-06-07 9:15 ` Lee Jones
2016-06-07 9:24 ` Lee Jones
2016-06-16 9:03 ` Philipp Zabel
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=20160606155655.10860-1-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).