From: Vinod Koul <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Phy <linux-phy@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: [GIT PULL]: soundwire: updates for v5.12-rc1
Date: Sun, 7 Feb 2021 23:06:01 +0530 [thread overview]
Message-ID: <20210207173601.GA879029@vkoul-mobl.Dlink> (raw)
[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]
Hello Greg,
Please pull to receive update for v5.12-rc1. This update includes new
no_pm IO routines and bunch of updates for intel & cadence drivers.
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.12-rc1
for you to fetch changes up to 6d7a1ff71cbb326fadfbedb7f75c1fc8f5c84d84:
soundwire: bus: clarify dev_err/dbg device references (2021-02-07 17:49:17 +0530)
----------------------------------------------------------------
soundwire updates for 5.12-rc1
Updates forv5.12-rc1 are:
- New no_pm IO routines and the usage in Intel drivers
- Intel driver & Cadence lib updates
----------------------------------------------------------------
Bard Liao (3):
soundwire: intel: don't return error when clock stop failed
soundwire: bus: add more details to track failed transfers
soundwire: export sdw_write/read_no_pm functions
Chao Song (1):
soundwire: return earlier if no slave is attached
Pierre-Louis Bossart (11):
soundwire: cadence: reduce timeout on transactions
soundwire: use consistent format for Slave devID logs
soundwire: cadence: add status in dev_dbg 'State change' log
soundwire: cadence: fix ACK/NAK handling
soundwire: cadence: adjust verbosity in response handling
soundwire: bus: add better dev_dbg to track complete() calls
soundwire: bus: use sdw_update_no_pm when initializing a device
soundwire: bus: use sdw_write_no_pm when setting the bus scale registers
soundwire: bus: use no_pm IO routines for all interrupt handling
soundwire: bus: fix confusion on device used by pm_runtime
soundwire: bus: clarify dev_err/dbg device references
Rikard Falkeborn (1):
soundwire: sysfs: Constify static struct attribute_group
Srinivas Kandagatla (1):
soundwire: debugfs: use controller id instead of link_id
Vinod Koul (2):
MAINTAINERS: soundwire: Add soundwire tree
soundwire: Revert "soundwire: debugfs: use controller id instead of link_id"
Zheng Yongjun (1):
soundwire: intel: Use kzalloc for allocating only one thing
MAINTAINERS | 1 +
drivers/soundwire/bus.c | 179 ++++++++++++++++++++-----------------
drivers/soundwire/cadence_master.c | 31 +++----
drivers/soundwire/intel.c | 8 +-
drivers/soundwire/slave.c | 10 +--
drivers/soundwire/sysfs_slave.c | 2 +-
include/linux/soundwire/sdw.h | 2 +
7 files changed, 128 insertions(+), 105 deletions(-)
Thanks
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-02-07 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 17:36 Vinod Koul [this message]
2021-02-09 8:31 ` [GIT PULL]: soundwire: updates for v5.12-rc1 Greg KH
2021-02-12 11:14 [GIT PULL] soundwire " Vinod Koul
2021-02-12 11:18 ` Greg KH
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=20210207173601.GA879029@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@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).