[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220701151359.4vnbhroubk7kswrw@bogus>
Date: Fri, 1 Jul 2022 16:13:59 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Jim Quinlan <james.quinlan@...adcom.com>
Cc: Cristian Marussi <cristian.marussi@....com>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Florian Fainelli <f.fainelli@...il.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Lukasz Luba <lukasz.luba@....com>
Subject: Re: [PATCH v2 0/2] Add SCMI full message tracing
On Fri, Jul 01, 2022 at 11:03:38AM -0400, Jim Quinlan wrote:
> Hi,
> LGTM, I appreciate this change. For testing, I fed your sample output to this:
>
Thanks!
> perl -MData::Dumper -nae 's/^.+scmi_msg_dump:// && print Dumper
> { (map { split /=/; } split" ") }' < scmi.txt
>
> which gives this
>
> $VAR1 = {
> 'pt' => '15',
> 'seq' => '0000',
> 'pyld' =>
> '000000000800000009daffffffffffff008268d4c075fd1611daffffffffffff008268d4c075fd1619daffffffffffff008268d4c075fd16',
> 'msg_id' => '01',
> 's' => '0',
> 't' => 'NOTI'
> };
> which is what I wanted. BTW, if I ever write a script that would
> take this SCMI trace text and
> decode it to nice cmd names and arguments -- where would I submit such a script?
>
I am not 100% sure. After reading this, the first thoughts were scripts/
or tools/scripts but looking at the content I am less sure about latter.
Worth posting and then check what people have to say once this lands upstream.
Or even once this is merged into -next officially.
--
Regards,
Sudeep
Powered by blists - more mailing lists