Linux SOC development
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Subject: [GIT PULL] Qualcomm Arm64 defconfig fixes for v6.16
Date: Thu, 10 Jul 2025 12:58:14 -0500	[thread overview]
Message-ID: <20250710175815.6504-1-andersson@kernel.org> (raw)


The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-arm64-defconfig-fixes-for-6.16

for you to fetch changes up to 3871b51a684275e3a47fbebf93c0a0e7a05d7f9f:

  arm64: defconfig: Enable Qualcomm CPUCP mailbox driver (2025-06-09 21:14:40 -0500)

----------------------------------------------------------------
Qualcomm Arm64 defconfig fixes for v6.16

The v6.16 driver and DeviceTree updates described and implemented CPU
frequency scaling for the Qualcomm X Elite platform. But the necessary
CPUCP mailbox driver was not enabled, resulting in a series of error
messages being logged during boot (and no CPU frequency scaling).

Enable the missing drivers to silence the errors, and enable CPU
frequency scaling on this platform.

----------------------------------------------------------------
Bjorn Andersson (1):
      arm64: defconfig: Enable Qualcomm CPUCP mailbox driver

 arch/arm64/configs/defconfig | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2025-07-10 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10 17:58 Bjorn Andersson [this message]
2025-07-11 11:50 ` [GIT PULL] Qualcomm Arm64 defconfig fixes for v6.16 patchwork-bot+linux-soc
2025-07-11 11:50 ` patchwork-bot+linux-soc

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=20250710175815.6504-1-andersson@kernel.org \
    --to=andersson@kernel.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=soc@kernel.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