From: Nishanth Menon <nm@ti.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
<arm@kernel.org>, <soc@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>
Subject: [GIT PULL 2/4] soc: ti: TI updates for v6.2
Date: Tue, 22 Nov 2022 13:01:36 -0600 [thread overview]
Message-ID: <20221122190136.avoej5i6zccbcds3@ammonia> (raw)
[-- Attachment #1: Type: text/plain, Size: 2386 bytes --]
Hi,
Please find the TI SoC driver changes for v6.2-rc1 below.
---
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-driver-soc-for-v6.2
for you to fetch changes up to 14c7137ac750d034580a38edbaf807064ae64699:
soc: ti: k3-socinfo: Add AM62Ax JTAG ID (2022-11-21 10:29:28 -0600)
----------------------------------------------------------------
TI SoC driver updates for v6.2
* Minor bugfixes for knav_qmss_queue, smartreflex drivers
* API optimizations including using devm, bitmap apis to
ti-sci, soc-info drivers
* k3-ringacc and k3-socinfo can now be built as modules for
certain distros that mandate such usage.
* k3-socinfo can now detect AM62A SoCs.
----------------------------------------------------------------
Chen Jiahao (1):
drivers: soc: ti: knav_qmss_queue: Mark knav_acc_firmwares as static
Christophe JAILLET (3):
firmware: ti_sci: Use the bitmap API to allocate bitmaps
firmware: ti_sci: Use the non-atomic bitmap API when applicable
firmware: ti_sci: Use devm_bitmap_zalloc when applicable
Georgi Vlaev (1):
firmware: ti_sci: Fix polled mode during system suspend
Nicolas Frayer (2):
soc: ti: k3-socinfo: Convert allocations to devm
soc: ti: k3-socinfo: Add module build support
Peter Ujfalusi (1):
soc: ti: k3-ringacc: Allow the driver to be built as module
Vignesh Raghavendra (1):
soc: ti: k3-socinfo: Add AM62Ax JTAG ID
Zhang Qilong (2):
soc: ti: knav_qmss_queue: Fix PM disable depth imbalance in knav_queue_probe
soc: ti: smartreflex: Fix PM disable depth imbalance in omap_sr_probe
arch/arm64/Kconfig.platforms | 1 -
drivers/firmware/ti_sci.c | 24 +++++++++-----------
drivers/soc/ti/Kconfig | 5 +++--
drivers/soc/ti/k3-ringacc.c | 28 +++++++++++++++++++++--
drivers/soc/ti/k3-socinfo.c | 48 ++++++++++++++++++++++++++--------------
drivers/soc/ti/knav_qmss_queue.c | 3 ++-
drivers/soc/ti/smartreflex.c | 1 +
7 files changed, 73 insertions(+), 37 deletions(-)
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-11-22 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 19:01 Nishanth Menon [this message]
2022-11-22 21:32 ` [GIT PULL 2/4] soc: ti: TI updates for v6.2 Nishanth Menon
2022-11-22 22:38 ` [GIT PULL V2 " Nishanth Menon
2022-11-23 12:20 ` 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=20221122190136.avoej5i6zccbcds3@ammonia \
--to=nm@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
/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