public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Ohad Ben-Cohen" <ohad@wizery.com>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Matti Lehtimäki" <matti.lehtimaki@gmail.com>
Subject: [GIT PULL] hwspinlock updates for v6.1
Date: Wed,  9 Nov 2022 21:07:54 -0600	[thread overview]
Message-ID: <20221110030754.786462-1-andersson@kernel.org> (raw)

Hi Linus,

I apparently had missed tagging and sending this set of changes out during the
6.1 merge window. But did get the associated dts changes depending on this
merged. The result is a regression in 6.1-rc on the affected, older, Qualcomm
platforms - in for form of them not booting.

So while these weren't regression fixes originally, they are now. It's not
introducing new beahavior, but simply extending the eixsting new Devicetree
model, to cover remaining platforms.

So I hope you will accept this pull request.

Regards,
Bjorn

The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:

  Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/hwlock-v6.1

for you to fetch changes up to c29f446108e10bb791220ffbba54d82722d60d45:

  dt-bindings: hwlock: qcom-hwspinlock: add syscon to MSM8974 (2022-10-17 17:11:17 -0500)

----------------------------------------------------------------
hwspinlock updates for v6.1

This extends the DeviceTree binding and implementation for the Qualcomm
hardware spinlock on some older platforms to follow the style of the
newer ones where the DeviceTree representation does not rely on an
intermediate syscon node.

----------------------------------------------------------------
Krzysztof Kozlowski (5):
      dt-bindings: hwlock: qcom-hwspinlock: add support for MMIO on older SoCs
      dt-bindings: hwlock: qcom-hwspinlock: correct example indentation
      hwspinlock: qcom: correct MMIO max register for newer SoCs
      hwspinlock: qcom: add support for MMIO on older SoCs
      dt-bindings: hwlock: qcom-hwspinlock: add syscon to MSM8974

 .../bindings/hwlock/qcom-hwspinlock.yaml           | 29 ++++++++++-----
 drivers/hwspinlock/qcom_hwspinlock.c               | 42 ++++++++++++++++------
 2 files changed, 53 insertions(+), 18 deletions(-)

             reply	other threads:[~2022-11-10  3:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  3:07 Bjorn Andersson [this message]
2022-11-10 17:03 ` [GIT PULL] hwspinlock updates for v6.1 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=20221110030754.786462-1-andersson@kernel.org \
    --to=andersson@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=matti.lehtimaki@gmail.com \
    --cc=ohad@wizery.com \
    --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