[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166195221577.495172.12603063310858665227.b4-ty@arm.com>
Date: Wed, 31 Aug 2022 14:25:28 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
cristian.marussi@....com
Cc: Sudeep Holla <sudeep.holla@....com>, james.quinlan@...adcom.com,
f.fainelli@...il.com, vincent.guittot@...aro.org,
lukasz.luba@....com
Subject: Re: [PATCH 0/1] Harmonize SCMI traces formats
On Thu, 18 Aug 2022 14:23:08 +0100, Cristian Marussi wrote:
> after having recently added new scmi_msg_dump traces I realized the
> general format of the various other SCMI traces is not consistent.
>
> As an example the full traces of a simple PERF_LEVEL_SET is now:
>
> cpufreq-set-276 [000] ..... 139.905639: scmi_xfer_begin: transfer_id=145 msg_id=7 protocol_id=19 seq=145 poll=0
> cpufreq-set-276 [000] ..... 139.905724: scmi_msg_dump: pt=13 t=CMND msg_id=07 seq=0091 s=0 pyld=000000008066ab13
> cpufreq-set-276 [000] ..... 139.905725: scmi_xfer_response_wait: transfer_id=145 msg_id=7 protocol_id=19 seq=145 tmo_ms=5000 poll=0
> <idle>-0 [000] d.h2. 139.906493: scmi_msg_dump: pt=13 t=RESP msg_id=07 seq=0091 s=0 pyld=
> <idle>-0 [000] d.h2. 139.906521: scmi_rx_done: transfer_id=145 msg_id=7 protocol_id=19 seq=145 msg_type=0
> cpufreq-set-276 [000] ..... 139.906651: scmi_xfer_end: transfer_id=145 msg_id=7 protocol_id=19 seq=145 status=0
>
> [...]
Applied to sudeep.holla/linux (for-next/scmi), thanks!
[1/1] include: trace: Harmonize SCMI tracing message format
https://git.kernel.org/sudeep.holla/c/40d30cf680cb
--
Regards,
Sudeep
Powered by blists - more mailing lists