All of lore.kernel.org
 help / color / mirror / Atom feed
From: jack wang <163wangjack@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, jack wang <163wangjack@gmail.com>
Subject: [PATCH 0/3] hw/misc: Replace DPRINTF with trace events in i.MX CCM family
Date: Wed, 24 Jun 2026 01:03:51 +0800	[thread overview]
Message-ID: <20260623170354.43981-1-163wangjack@gmail.com> (raw)

This series modernizes the three i.MX CCM device models by removing
the old DEBUG_IMX*_CCM / DPRINTF macros and emitting QEMU trace
events instead, following the same pattern already merged for
hw/timer/imx_epit (commit 5005b00d41).

Patches are split per file so each commit changes one device, keeps
git bisect clean, and stays in scope for the trivial-patches team.

No behavior change is intended: the previous DEBUG_IMX_CCM switches defaulted to 0, 
so DPRINTF output was off by default. After this series the same information is 
available via -trace 'imx*ccm'.

jack wang (3):
  hw/misc/imx_ccm: Replace DPRINTF with trace events
  hw/misc/imx25_ccm: Replace DPRINTF with trace events
  hw/misc/imx31_ccm: Replace DPRINTF with trace events

 hw/misc/imx25_ccm.c  | 34 ++++++++++------------------------
 hw/misc/imx31_ccm.c  | 33 ++++++++++-----------------------
 hw/misc/imx_ccm.c    | 18 +++---------------
 hw/misc/trace-events | 23 +++++++++++++++++++++++
 4 files changed, 46 insertions(+), 62 deletions(-)

-- 
2.53.0



             reply	other threads:[~2026-06-23 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 17:03 jack wang [this message]
2026-06-23 17:03 ` [PATCH 1/3] hw/misc/imx_ccm: Replace DPRINTF with trace events jack wang
2026-06-23 17:03 ` [PATCH 2/3] hw/misc/imx25_ccm: " jack wang
2026-06-23 17:03 ` [PATCH 3/3] hw/misc/imx31_ccm: " jack wang

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=20260623170354.43981-1-163wangjack@gmail.com \
    --to=163wangjack@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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.