All of lore.kernel.org
 help / color / mirror / Atom feed
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>, <nm@ti.com>
Subject: [GIT PULL 1/3] TI SoC driver updates for v5.18
Date: Mon, 28 Feb 2022 06:06:55 -0600	[thread overview]
Message-ID: <20220228120655.wobd72acngl2bz6k@ecard> (raw)

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]

Hi ARM SoC maintainers,

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-driver-soc-for-v5.18

for you to fetch changes up to c65d68e7e95a39da31d64d67d5bea6550b91fb43:

  soc: ti: k3-socinfo: Add AM62x JTAG ID (2022-02-28 05:35:19 -0600)

----------------------------------------------------------------
TI Driver updates for v5.18

* Fixups for k3-ringacc, smartreflex, tisci, wkup_m3_ipc
* Device detection for am62x.

----------------------------------------------------------------
Christophe JAILLET (2):
      soc: ti: k3-ringacc: Use devm_bitmap_zalloc() when applicable
      firmware: ti_sci: Fix compilation failure when CONFIG_TI_SCI_PROTOCOL is not defined

Lad Prabhakar (1):
      soc: ti: smartreflex: Use platform_get_irq_optional() to get the interrupt

Miaoqian Lin (1):
      soc: ti: wkup_m3_ipc: Fix IRQ check in wkup_m3_ipc_probe

Peiwei Hu (1):
      firmware: ti_sci: inproper error handling of ti_sci_probe

Vignesh Raghavendra (1):
      soc: ti: k3-socinfo: Add AM62x JTAG ID

 drivers/firmware/ti_sci.c              |  2 +-
 drivers/soc/ti/k3-ringacc.c            | 15 ++++++---------
 drivers/soc/ti/k3-socinfo.c            |  1 +
 drivers/soc/ti/smartreflex.c           | 13 +++++++------
 drivers/soc/ti/wkup_m3_ipc.c           |  4 ++--
 include/linux/soc/ti/ti_sci_protocol.h |  2 +-
 6 files changed, 18 insertions(+), 19 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 --]

WARNING: multiple messages have this Message-ID (diff)
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>, <nm@ti.com>
Subject: [GIT PULL 1/3] TI SoC driver updates for v5.18
Date: Mon, 28 Feb 2022 06:06:55 -0600	[thread overview]
Message-ID: <20220228120655.wobd72acngl2bz6k@ecard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1722 bytes --]

Hi ARM SoC maintainers,

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git tags/ti-driver-soc-for-v5.18

for you to fetch changes up to c65d68e7e95a39da31d64d67d5bea6550b91fb43:

  soc: ti: k3-socinfo: Add AM62x JTAG ID (2022-02-28 05:35:19 -0600)

----------------------------------------------------------------
TI Driver updates for v5.18

* Fixups for k3-ringacc, smartreflex, tisci, wkup_m3_ipc
* Device detection for am62x.

----------------------------------------------------------------
Christophe JAILLET (2):
      soc: ti: k3-ringacc: Use devm_bitmap_zalloc() when applicable
      firmware: ti_sci: Fix compilation failure when CONFIG_TI_SCI_PROTOCOL is not defined

Lad Prabhakar (1):
      soc: ti: smartreflex: Use platform_get_irq_optional() to get the interrupt

Miaoqian Lin (1):
      soc: ti: wkup_m3_ipc: Fix IRQ check in wkup_m3_ipc_probe

Peiwei Hu (1):
      firmware: ti_sci: inproper error handling of ti_sci_probe

Vignesh Raghavendra (1):
      soc: ti: k3-socinfo: Add AM62x JTAG ID

 drivers/firmware/ti_sci.c              |  2 +-
 drivers/soc/ti/k3-ringacc.c            | 15 ++++++---------
 drivers/soc/ti/k3-socinfo.c            |  1 +
 drivers/soc/ti/smartreflex.c           | 13 +++++++------
 drivers/soc/ti/wkup_m3_ipc.c           |  4 ++--
 include/linux/soc/ti/ti_sci_protocol.h |  2 +-
 6 files changed, 18 insertions(+), 19 deletions(-)

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-02-28 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 12:06 Nishanth Menon [this message]
2022-02-28 12:06 ` [GIT PULL 1/3] TI SoC driver updates for v5.18 Nishanth Menon
2022-02-28 15:00 ` 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=20220228120655.wobd72acngl2bz6k@ecard \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.