HSI changes for 4.8
Hi Linus,
The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.git tags/hsi-for-4.8
for you to fetch changes up to 9c99e5e51988798af2a687ef9b1716dd79388550:
HSI: omap_ssi: drop pm_runtime_irq_safe (2016-06-28 00:40:08 +0200)
----------------------------------------------------------------
HSI changes for the v4.8 series
* proper runtime pm support for omap-ssi and ssi-protocol
* misc. fixes
----------------------------------------------------------------
Andrew F. Davis (2):
hsi: Build hsi_boardinfo.c into hsi core if enabled
hsi: Only descend into hsi directory when CONFIG_HSI is set
Iago Abal (1):
HSI: cmt_speech: Fix double spin_lock
Muhammad Falak R Wani (2):
HSI: cmt_speech: use vma_pages().
hsi: use kmemdup
Sebastian Reichel (19):
HSI: omap_ssi_port: remove useless newline
HSI: omap_ssi: do not reset module
HSI: ssi_protocol: avoid ssi_waketest call with held spinlock
HSI: ssi_protocol: replace spin_lock with spin_lock_bh
HSI: ssi_protocol: fix ssip_xmit invocation
HSI: omap_ssi: convert cawake irq handler to thread
HSI: omap_ssi_port: replace wkin_cken with atomic bitmap operations
HSI: core: switch port event notifier from atomic to blocking
HSI: omap_ssi_port: prepare start_tx/stop_tx for blocking pm_runtime calls
HSI: omap_ssi_core: use pm_runtime_put instead of pm_runtime_put_sync
HSI: omap_ssi_core: remove pm_runtime_get_sync call from tasklet
HSI: omap_ssi_port: switch to threaded pio irq
HSI: omap_ssi_port: avoid pm_runtime_get_sync in ssi_start_dma and ssi_start_pio
HSI: omap_ssi_port: avoid calling runtime_pm_*_sync inside spinlock
HSI: omap_ssi_port: replace pm_runtime_put_sync with non-sync variant
HSI: omap_ssi_port: ensure clocks are kept enabled during transfer
HSI: omap_ssi: call msg->complete() from process context
HSI: omap_ssi_port: use rpm autosuspend API
HSI: omap_ssi: drop pm_runtime_irq_safe
Documentation/DocBook/device-drivers.tmpl | 2 +-
drivers/Makefile | 2 +-
drivers/hsi/Makefile | 3 +-
drivers/hsi/clients/cmt_speech.c | 4 +-
drivers/hsi/clients/ssi_protocol.c | 110 +++++++++------
drivers/hsi/controllers/omap_ssi.h | 18 +--
drivers/hsi/controllers/omap_ssi_core.c | 46 +++---
drivers/hsi/controllers/omap_ssi_port.c | 226 +++++++++++++++++-------------
drivers/hsi/{hsi.c => hsi_core.c} | 16 +--
include/linux/hsi/hsi.h | 2 +-
10 files changed, 239 insertions(+), 190 deletions(-)
rename drivers/hsi/{hsi.c => hsi_core.c} (97%)Quoted 8 lines · Sebastian Reichel
The following changes since commit
1a695a905c18548062509178b98bc91e67510864:Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.gittags/hsi-for-4.8
Btw, _please_ change your script to make sure the email has both "git" and "pull" in it somewhere. Without that, I don't see it with my normal search criteria for git pull requests, and during the merge window that often means that emails like that get overlooked.
The preferred model tends to be to have "[GIT PULL]" at the beginning of the subject line, but even just a simple "please pull" in the body will trigger my search terms (together with the "git repository" thing from the boilerplate), so whatever is most convenient for you.
This comes up pretty much every single merge window. People, please.. I do try to notice pull requests and patches (for patches, please put "[PATCH x/y]" in the subject line) even when they don't trigger my usual search terms, but it really does help when emails match my simple rules.. I get too much email, making it easier for me to sort out pull requests really does make a difference.
Linus
Hi,
Quoted 19 lines · Linus Torvalds
Quoted 7 lines · Sebastian Reichel
The following changes since commit
1a695a905c18548062509178b98bc91e67510864:Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-hsi.gittags/hsi-for-4.8Btw, _please_ change your script to make sure the email has both "git" and "pull" in it somewhere. Without that, I don't see it with my normal search criteria for git pull requests, and during the merge window that often means that emails like that get overlooked.
The preferred model tends to be to have "[GIT PULL]" at the beginning of the subject line, but even just a simple "please pull" in the body will trigger my search terms (together with the "git repository" thing from the boilerplate), so whatever is most convenient for you.
Quoted 6 lines
This comes up pretty much every single merge window. People, please.. I do try to notice pull requests and patches (for patches, please put "[PATCH x/y]" in the subject line) even when they don't trigger my usual search terms, but it really does help when emails match my simple rules.. I get too much email, making it easier for me to sort out pull requests really does make a difference.
Sorry, I currently write the pull request mails manually and forgot to add it. I will prepare a script to avoid this in the future.
-- Sebastian