linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jassi Brar <jassisinghbrar@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Mailbox changes for v4.21
Date: Tue, 1 Jan 2019 23:34:36 -0600	[thread overview]
Message-ID: <CABb+yY1ZO8pCuN4o3ja-Lyr0G6CVSUJfotcJcEmfJ9MHEAneSA@mail.gmail.com> (raw)

Hi Linus,

The following changes since commit f5d582777bcb1c7ff19a5a2343f66ea01de401c6:

  Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid (2018-12-10
11:04:41 -0800)

are available in the Git repository at:

  git://git.linaro.org/landing-teams/working/fujitsu/integration.git
tags/mailbox-v4.21

for you to fetch changes up to d69e11648e486ee0f21cb246f687b083f0d4e124:

  mailbox: tegra-hsp: Use device-managed registration API (2018-12-21
22:31:26 -0600)

----------------------------------------------------------------
- Introduce device-managed registration
devm_mbox_controller_un/register and convert drivers to use it
- Introduce flush api to support clients that must busy-wait in atomic context
- Support multiple controllers per device
- Hi3660: a bugfix and constify ops structure
- TI-MsgMgr: off by one bugfix.
- BCM: switch to spdx license
- Tegra-HSP: support for shared mailboxes and suspend/resume.

----------------------------------------------------------------
Bartosz Golaszewski (1):
      mailbox: tegra-hsp: use devm_kstrdup_const()

Dan Carpenter (1):
      mailbox: ti-msgmgr: Off by one in ti_msgmgr_of_xlate()

Julia Lawall (1):
      mailbox: hi3660: constify mbox_chan_ops structure

Kevin Wangtao (1):
      mailbox: Hi3660: Fixup mailbox state machine malfunction issue

Mikko Perttunen (2):
      mailbox: Allow multiple controllers per device
      dt-bindings: tegra186-hsp: Add shared mailboxes

Stefan Wahren (1):
      mailbox: bcm2835: Switch to SPDX identifier

Thierry Reding (23):
      mailbox: Add device-managed registration functions
      mailbox: arm-mhu: Use device-managed registration API
      mailbox: bcm2835: Use device-managed registration API
      mailbox: bcm-flexrm: Use device-managed registration API
      mailbox: bcm-pdc: Use device-managed registration API
      mailbox: hi3660: Use device-managed registration API
      mailbox: hi6220: Use device-managed registration API
      mailbox: imx: Use device-managed registration API
      mailbox: altera: Use device-managed registration API
      mailbox: sti: Use device-managed registration API
      mailbox: xgene-slimpro: Use device-managed registration API
      mailbox: mtk-cmdq: Use device-managed registration API
      mailbox: mtk-cmdq: Remove needless devm_kfree() calls
      mailbox: omap: Use device-managed registration API
      mailbox: platform-mhu: Use device-managed registration API
      mailbox: qcom-apcs: Use device-managed registration API
      mailbox: rockchip: Use device-managed registration API
      mailbox: stm32-ipcc: Use device-managed registration API
      mailbox: ti-msgmgr: Use device-managed registration API
      mailbox: Support blocking transfers in atomic context
      mailbox: tegra-hsp: Add support for shared mailboxes
      mailbox: tegra-hsp: Add suspend/resume support
      mailbox: tegra-hsp: Use device-managed registration API

 .../bindings/mailbox/nvidia,tegra186-hsp.txt       |  30 +-
 drivers/mailbox/arm_mhu.c                          |  12 +-
 drivers/mailbox/bcm-flexrm-mailbox.c               |   4 +-
 drivers/mailbox/bcm-pdc-mailbox.c                  |   4 +-
 drivers/mailbox/bcm2835-mailbox.c                  |  18 +-
 drivers/mailbox/hi3660-mailbox.c                   |  35 +-
 drivers/mailbox/hi6220-mailbox.c                   |  11 +-
 drivers/mailbox/imx-mailbox.c                      |   3 +-
 drivers/mailbox/mailbox-altera.c                   |  15 +-
 drivers/mailbox/mailbox-sti.c                      |  13 +-
 drivers/mailbox/mailbox-xgene-slimpro.c            |  11 +-
 drivers/mailbox/mailbox.c                          | 101 +++-
 drivers/mailbox/mtk-cmdq-mailbox.c                 |  11 +-
 drivers/mailbox/omap-mailbox.c                     |   4 +-
 drivers/mailbox/platform_mhu.c                     |  12 +-
 drivers/mailbox/qcom-apcs-ipc-mailbox.c            |   3 +-
 drivers/mailbox/rockchip-mailbox.c                 |  15 +-
 drivers/mailbox/stm32-ipcc.c                       |   4 +-
 drivers/mailbox/tegra-hsp.c                        | 517 +++++++++++++++++----
 drivers/mailbox/ti-msgmgr.c                        |  15 +-
 include/dt-bindings/mailbox/tegra186-hsp.h         |  11 +
 include/linux/mailbox_client.h                     |   1 +
 include/linux/mailbox_controller.h                 |   9 +
 23 files changed, 612 insertions(+), 247 deletions(-)

             reply	other threads:[~2019-01-02  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02  5:34 Jassi Brar [this message]
2019-01-03  3:05 ` [GIT PULL] Mailbox changes for v4.21 pr-tracker-bot

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=CABb+yY1ZO8pCuN4o3ja-Lyr0G6CVSUJfotcJcEmfJ9MHEAneSA@mail.gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).