Hi,

In IEEE 1394 bus, the type of asynchronous packet without any offset to
node address space is called as phy packet. The destination of packet is
IEEE 1394 phy itself. This type of packet is used for several purposes,
mainly for selfID at the state of bus reset, to force selection of root
node, and to adjust gap count.

This series of changes is to add tracepoints events for this kind of
asynchronous packets.

Takashi Sakamoto (2):
  firewire: core/cdev: add tracepoints events for asynchronous phy
    packet
  firewire: core: add tracepoints event for asynchronous inbound phy
    packet

 drivers/firewire/core-cdev.c        |  7 +++
 drivers/firewire/core-transaction.c |  8 +++
 include/trace/events/firewire.h     | 78 +++++++++++++++++++++++++++++
 3 files changed, 93 insertions(+)

-- 
2.43.0

On Tue, Apr 30, 2024 at 09:14:02AM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> In IEEE 1394 bus, the type of asynchronous packet without any offset to
> node address space is called as phy packet. The destination of packet is
> IEEE 1394 phy itself. This type of packet is used for several purposes,
> mainly for selfID at the state of bus reset, to force selection of root
> node, and to adjust gap count.
> 
> This series of changes is to add tracepoints events for this kind of
> asynchronous packets.
> 
> Takashi Sakamoto (2):
>   firewire: core/cdev: add tracepoints events for asynchronous phy
>     packet
>   firewire: core: add tracepoints event for asynchronous inbound phy
>     packet
> 
>  drivers/firewire/core-cdev.c        |  7 +++
>  drivers/firewire/core-transaction.c |  8 +++
>  include/trace/events/firewire.h     | 78 +++++++++++++++++++++++++++++
>  3 files changed, 93 insertions(+)

Applied to for-next branch.


Regards

Takashi Sakamoto