All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: soc@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: [GIT PULL] SOC FSL for 7.4
Date: Mon, 12 Oct 2026 10:15:02 +0200	[thread overview]
Message-ID: <53a2dd80-3d3e-4b6f-9419-c71434c41a82@kernel.org> (raw)

Hi Arnd,

Please pull the following Freescale Soc Drivers changes for 7.4

Changes to fsl-mc bus are reviewed or acked by Ioana
Changes to usb drivers are acked by greg

Thanks
Christophe

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

   Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

   https://git.kernel.org/pub/scm/linux/kernel/git/chleroy/linux 
tags/soc_fsl-7.4-1

for you to fetch changes up to a7831c657c90e8f9165f6bbe0cc56262fee075e8:

   soc: fsl: dpio: Free the IRQ before releasing the I/O object 
(2026-10-09 10:15:19 +0200)

----------------------------------------------------------------
FSL SOC Changes for 7.4

Freescale QUICC Engine:
- Fix sparse warnings in GPIO
- Drop GPIOD_FLAGS_BIT_NONEXCLUSIVE

Freescale CPM1 Timeslot Assigner:
- Fix clock leak in tsa_of_parse_tdms()

Data Path I/O:
- Free the IRQ before releasing the I/O object
- Fix cleanup on IRQ registration failure

Freescale Management Complex:
- Annotate fsl_mc_io.portal_virt_addr with __counted_by_ptr
- Drop the fwnode links of the dpmacs nodes
- Register the object drivers after misc_class exists
- Set dma_mask for the DPRC devices
- Fix repeated word 'for' in comment

----------------------------------------------------------------
Bartosz Golaszewski (1):
       soc: fsl: qe: drop GPIOD_FLAGS_BIT_NONEXCLUSIVE

Bill Wendling (1):
       bus: fsl-mc: Annotate fsl_mc_io.portal_virt_addr with 
__counted_by_ptr

Christophe Leroy (CS GROUP) (1):
       soc: fsl: qe: Fix sparse warnings in GPIO

Hemanth Selam (1):
       bus: fsl-mc: fix repeated word 'for' in comment

Myeonghun Pak (2):
       soc: fsl: dpio: Fix cleanup on IRQ registration failure
       soc: fsl: dpio: Free the IRQ before releasing the I/O object

Vincent Jardin (3):
       bus: fsl-mc: set dma_mask for the DPRC devices
       bus: fsl-mc: register the object drivers after misc_class exists
       bus: fsl-mc: drop the fwnode links of the dpmacs nodes

Wentao Liang (1):
       soc: fsl: cpm1: tsa: Fix clock leak in tsa_of_parse_tdms()

  drivers/bus/fsl-mc/fsl-mc-bus.c    | 64 
+++++++++++++++++++++++++-----------
  drivers/bus/fsl-mc/fsl-mc-msi.c    |  2 +-
  drivers/soc/fsl/dpio/dpio-driver.c |  9 ++---
  drivers/soc/fsl/qe/gpio.c          | 67 
+++++++++++++++-----------------------
  drivers/soc/fsl/qe/tsa.c           | 16 ++++-----
  drivers/usb/host/fhci-hcd.c        |  2 +-
  include/linux/fsl/mc.h             |  2 +-
  include/soc/fsl/qe/qe.h            |  6 ++--
  8 files changed, 91 insertions(+), 77 deletions(-)

             reply	other threads:[~2026-10-12  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  8:15 Christophe Leroy (CS GROUP) [this message]
2026-10-13 16:10 ` [GIT PULL] SOC FSL for 7.4 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=53a2dd80-3d3e-4b6f-9419-c71434c41a82@kernel.org \
    --to=chleroy@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ioana.ciornei@nxp.com \
    --cc=linux-kernel@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 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.