Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: gregkh@linuxfoundation.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, coresight@lists.linaro.org,
	leo.yan@linux.dev, james.clark@linaro.org, mike.leach@arm.com,
	Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [GIT PULL] coresight: Updates for Linux v7.3
Date: Sat,  8 Aug 2026 00:00:57 +0100	[thread overview]
Message-ID: <20260807230057.119105-1-suzuki.poulose@arm.com> (raw)

Hi Greg

Please find this pull request for CoreSight subsystem targeting v7.3.
Almost all of them are fixes to the existing code, along with a MAINTAINERS
update for HiSilicon PTT driver.

Kindly pull

Suzuki



The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:

  Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git tags/coresight-next-v7.3

for you to fetch changes up to 9e3604d7369cfc0110100eb1a0acab1865ee2d18:

  coresight: etm4x: remove redundant fields in etmv4_save_state (2026-08-07 10:45:11 +0100)

----------------------------------------------------------------
coresight: Updates for Linux v7.3

This is relatively smaller update for CoreSight/hwtracing subsystem updates.
 - MAINTAINERS update for HiSilicon PCI Trace & Tune drivers
 - Minor fixes to hisi_ptt driver
 - Various fixes to the coresight etm4x dirvers

Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>

----------------------------------------------------------------
Jonathan Cameron (1):
      MAINTAINERS: Update HiSilicon PCI Trace and Tune maintainer

Kuan-Wei Chiu (1):
      coresight: etm3x: Fix cntr_val_show() to match cntr_val_store() behavior

Sanman Pradhan (2):
      hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start()
      hwtracing: hisi_ptt: Remove unnecessary trace buffer zeroing in trace_start()

Yeoreum Yun (5):
      coresight: etm4x: fix wrong check of etm4x_sspcicrn_present()
      coresight: etm4x: fix underflow for usage of (nrseqstate - 1)
      coresight: etm4x: fix leaked trace id
      coresight: etm4x: missing cscfg_csdev_disable_active_config() in perf enable
      coresight: etm4x: remove redundant fields in etmv4_save_state

 MAINTAINERS                                        |  3 +-
 .../hwtracing/coresight/coresight-etm3x-sysfs.c    | 15 ++----
 drivers/hwtracing/coresight/coresight-etm4x-cfg.c  |  2 +-
 drivers/hwtracing/coresight/coresight-etm4x-core.c | 59 +++++++++++++---------
 .../hwtracing/coresight/coresight-etm4x-sysfs.c    |  6 ++-
 drivers/hwtracing/coresight/coresight-etm4x.h      | 12 ++---
 drivers/hwtracing/ptt/hisi_ptt.c                   | 25 ++++-----
 7 files changed, 63 insertions(+), 59 deletions(-)


             reply	other threads:[~2026-08-07 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 23:00 Suzuki K Poulose [this message]
2026-08-19  7:58 ` [GIT PULL] coresight: Updates for Linux v7.3 Greg KH

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=20260807230057.119105-1-suzuki.poulose@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.clark@linaro.org \
    --cc=leo.yan@linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@arm.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