From: Nishanth Menon <nm@ti.com>
To: Arnd <arnd@arndb.de>, Olof <olof@lixom.net>, SoC <soc@kernel.org>
Cc: <arm@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: [GIT PULL 1/3] soc: ti: Updates for v6.4
Date: Mon, 10 Apr 2023 09:05:06 -0500 [thread overview]
Message-ID: <20230410140506.ucvkwq7vz2h47vyj@stipulate> (raw)
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
Hi,
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
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.4
for you to fetch changes up to a33bfafd99e0d1e33dfe910f751426f298a218b6:
soc: ti: Use devm_platform_ioremap_resource() (2023-03-28 06:23:42 -0500)
----------------------------------------------------------------
TI SoC driver updates for v6.4
* Minor fixups for of_property, using devm_platform_ioremap
* Fixups for refcount leaks in pm33xx
* Fixups for k3-ringacc for dmaring_request
* SoCinfo detection for J784S4 SoC.
----------------------------------------------------------------
Miaoqian Lin (1):
soc: ti: pm33xx: Fix refcount leak in am33xx_pm_probe
Nicolas Frayer (1):
soc: ti: k3-ringacc: Add try_module_get() to k3_dmaring_request_dual_ring()
Rob Herring (2):
soc: ti: Use of_property_present() for testing DT property presence
soc: ti: Use of_property_read_bool() for boolean properties
Siddharth Vadapalli (1):
soc: ti: k3-socinfo: Add entry for J784S4 SOC
Yang Li (1):
soc: ti: Use devm_platform_ioremap_resource()
drivers/soc/ti/k3-ringacc.c | 7 +++++++
drivers/soc/ti/k3-socinfo.c | 1 +
drivers/soc/ti/knav_dma.c | 4 ++--
drivers/soc/ti/knav_qmss_acc.c | 2 +-
drivers/soc/ti/knav_qmss_queue.c | 4 ++--
drivers/soc/ti/omap_prm.c | 2 +-
drivers/soc/ti/pm33xx.c | 5 +++--
drivers/soc/ti/wkup_m3_ipc.c | 6 ++----
8 files changed, 19 insertions(+), 12 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 --]
reply other threads:[~2023-04-10 14:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230410140506.ucvkwq7vz2h47vyj@stipulate \
--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
all inboxes | Powered by JetHome®