public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] firewire: core/ohci: add tracepoints events for bus-reset
Date: Thu, 2 May 2024 08:14:10 +0900	[thread overview]
Message-ID: <20240501231410.GA106963@workstation.local> (raw)
In-Reply-To: <20240501073238.72769-1-o-takashi@sakamocchi.jp>

Hi,

On Wed, May 01, 2024 at 04:32:33PM +0900, Takashi Sakamoto wrote:
> 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(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2024-05-01 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  7:32 [PATCH 0/5] firewire: core/ohci: add tracepoints events for bus-reset Takashi Sakamoto
2024-05-01  7:32 ` [PATCH 1/5] firewire: ohci: add bus-reset event for initial set of handled irq Takashi Sakamoto
2024-05-01  7:32 ` [PATCH 2/5] firewire: ohci: obsolete OHCI_PARAM_DEBUG_BUSRESETS from debug module parameter Takashi Sakamoto
2024-05-01  7:32 ` [PATCH 3/5] firewire: core: add tracepoints events for initiating bus reset Takashi Sakamoto
2024-05-01  7:32 ` [PATCH 4/5] Revert "firewire: core: option to log bus reset initiation" Takashi Sakamoto
2024-05-01  7:32 ` [PATCH 5/5] firewire: core: add tracepoint event for handling bus reset Takashi Sakamoto
2024-05-01 23:14 ` Takashi Sakamoto [this message]

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=20240501231410.GA106963@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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