Linux-remoteproc Archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Beleswar Padhi <b-padhi@ti.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
	Chen-Yu Tsai <wenst@chromium.org>,
	Robin Murphy <robin.murphy@arm.com>
Subject: [GIT PULL] remoteproc updates for v6.14
Date: Sat, 25 Jan 2025 09:39:04 -0800	[thread overview]
Message-ID: <20250125173905.1150203-1-andersson@kernel.org> (raw)


The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/rproc-v6.14

for you to fetch changes up to 3a53ff95b0be9a5d0ef5037e539558d0041f9a89:

  remoteproc: st: Use syscon_regmap_lookup_by_phandle_args (2025-01-15 10:04:27 -0700)

----------------------------------------------------------------
remoteproc updates for v6.14

Correct error path in rproc_alloc(), with regards to put_device() and
freeing of the rproc index ida. The Mediatek SCP remoteproc driver is
returned to only creating child devices from specific DeviceTree nodes.
OMAP remoteproc driver is updated to match the cleanups in the OMAP
iommu driver.

In addition to this, a number of conversions to devres and other small,
mostly stylistic, code cleanups.

----------------------------------------------------------------
Arnaud Pouliquen (1):
      remoteproc: core: Fix ida_free call while not allocated

Beleswar Padhi (5):
      remoteproc: k3-r5: Add devm action to release reserved memory
      remoteproc: k3-r5: Use devm_kcalloc() helper
      remoteproc: k3-r5: Use devm_ioremap_wc() helper
      remoteproc: k3-r5: Use devm_rproc_add() helper
      remoteproc: k3-r5: Add devm action to release tsp

Chen-Yu Tsai (1):
      remoteproc: mtk_scp: Only populate devices for SCP cores

Krzysztof Kozlowski (5):
      remoteproc: keystone: Simplify returning syscon PTR_ERR
      remoteproc: omap: Simplify returning syscon PTR_ERR
      remoteproc: st: Simplify with dev_err_probe
      remoteproc: keystone: Use syscon_regmap_lookup_by_phandle_args
      remoteproc: st: Use syscon_regmap_lookup_by_phandle_args

Robin Murphy (1):
      remoteproc: omap: Handle ARM dma_iommu_mapping

 drivers/remoteproc/keystone_remoteproc.c | 17 ++----
 drivers/remoteproc/mtk_scp.c             | 12 ++++-
 drivers/remoteproc/omap_remoteproc.c     | 24 +++++++--
 drivers/remoteproc/remoteproc_core.c     | 14 ++---
 drivers/remoteproc/st_remoteproc.c       | 54 ++++++++------------
 drivers/remoteproc/ti_k3_r5_remoteproc.c | 88 +++++++++++++-------------------
 6 files changed, 97 insertions(+), 112 deletions(-)

             reply	other threads:[~2025-01-25 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 17:39 Bjorn Andersson [this message]
2025-01-26  1:03 ` [GIT PULL] remoteproc updates for v6.14 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=20250125173905.1150203-1-andersson@kernel.org \
    --to=andersson@kernel.org \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=b-padhi@ti.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wenst@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).