Received-SPF: pass (google.com: domain of linux-kernel+bounces-164988-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Feedback-ID: ie8e14432:Fastmail
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org,
	adamg@pobox.com
Subject: [PATCH 0/5] firewire: core/ohci: add tracepoints events for bus-reset
Date: Wed,  1 May 2024 16:32:33 +0900
Message-ID: <20240501073238.72769-1-o-takashi@sakamocchi.jp>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Hi,

IEEE 1394 bus is under bus-reset state when the physical state of bus is
changed; e.g. bus topology change by adding new nodes in the bus. It is
important to handle the state appropriately for the maintenance of bus.

This series of change adds some tracepoints events to trace the events
related to bus-reset. Some kernel log messages are obsoleted and
deleted. It also includes for 1394 OHCI driver so that bus-reset IRQ
event is recorded as much as possible, and obsoletes bus-resets bit
from debug parameter successfully.

Takashi Sakamoto (5):
  firewire: ohci: add bus-reset event for initial set of handled irq
  firewire: ohci: obsolete OHCI_PARAM_DEBUG_BUSRESETS from debug module
    parameter
  firewire: core: add tracepoints events for initiating bus reset
  Revert "firewire: core: option to log bus reset initiation"
  firewire: core: add tracepoint event for handling bus reset

 drivers/firewire/core-card.c        | 13 +++---
 drivers/firewire/core-topology.c    |  3 ++
 drivers/firewire/core-transaction.c |  7 ----
 drivers/firewire/core.h             |  4 --
 drivers/firewire/ohci.c             | 18 +++------
 include/trace/events/firewire.h     | 61 ++++++++++++++++++++++++++++-
 6 files changed, 73 insertions(+), 33 deletions(-)

-- 
2.43.0