From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org, Varka Bhadram <varkab@cdac.in>
Subject: Re: [RFC bluetooth-next] mac802154: add trace functionality for driver ops
Date: Fri, 29 May 2015 11:01:48 +0530 [thread overview]
Message-ID: <5567F9C4.5080904@gmail.com> (raw)
In-Reply-To: <20150528082032.GA1114@omega>
Hi Alex,
On 05/28/2015 01:50 PM, Alexander Aring wrote:
> Hi,
>
> I did not test yet, but found some review things.
Please test it.
> On Wed, May 27, 2015 at 01:54:50PM +0530, Varka Bhadram wrote:
> ...
>> + __field(bool, mode)
>> + ),
>> + TP_fast_assign(
>> + LOCAL_ASSIGN;
>> + __entry->mode = mode;
>> + ),
>> + TP_printk(LOCAL_PR_FMT ", lbt mode: %s", LOCAL_PR_ARG,
>> + BOOL_TO_STR(__entry->mode))
>> +);
>> +
>> +TRACE_EVENT(802154_drv_set_short_addr,
>> + TP_PROTO(struct ieee802154_local *local, __le16 short_addr),
>> + TP_ARGS(local, short_addr),
>> + TP_STRUCT__entry(
>> + LOCAL_ENTRY
>> + __field(__le16, short_addr)
>> + ),
>> + TP_fast_assign(
>> + LOCAL_ASSIGN;
>> + __entry->short_addr = short_addr;
>> + ),
>> + TP_printk(LOCAL_PR_FMT ", sa: 0x%04x", LOCAL_PR_ARG,
>> + __entry->short_addr)
> care about byteorder here. you need cpu_to_le16 in the format string,
> please.
>
>
>> +);
>> +
>> +TRACE_EVENT(802154_drv_set_pan_id,
>> + TP_PROTO(struct ieee802154_local *local, __le16 pan_id),
>> + TP_ARGS(local, pan_id),
>> + TP_STRUCT__entry(
>> + LOCAL_ENTRY
>> + __field(__le16, pan_id)
>> + ),
>> + TP_fast_assign(
>> + LOCAL_ASSIGN;
>> + __entry->pan_id = pan_id;
>> + ),
>> + TP_printk(LOCAL_PR_FMT ", pan id: 0x%04x", LOCAL_PR_ARG,
>> + __entry->pan_id)
> same here.
>
>> +);
>> +
>> +TRACE_EVENT(802154_drv_set_extended_addr,
>> + TP_PROTO(struct ieee802154_local *local, __le64 extended_addr),
>> + TP_ARGS(local, extended_addr),
>> + TP_STRUCT__entry(
>> + LOCAL_ENTRY
>> + __field(__le64, extended_addr)
>> + ),
>> + TP_fast_assign(
>> + LOCAL_ASSIGN;
>> + __entry->extended_addr = extended_addr;
>> + ),
>> + TP_printk(LOCAL_PR_FMT ", extended addr %llx", LOCAL_PR_ARG,
>> + __entry->extended_addr)
>> +);
>> +
> same here.
>
>> +TRACE_EVENT(802154_drv_set_pan_coord,
>> + TP_PROTO(struct ieee802154_local *local, bool is_coord),
>> + TP_ARGS(local, is_coord),
>> + TP_STRUCT__entry(
>> + LOCAL_ENTRY
>> + __field(bool, is_coord)
>> + ),
>> + TP_fast_assign(
>> + LOCAL_ASSIGN;
>> + __entry->is_coord = is_coord;
>> + ),
>> + TP_printk(LOCAL_PR_FMT ", is_coord: %s", LOCAL_PR_ARG,
>> + BOOL_TO_STR(__entry->is_coord))
>> +);
>> +
Ok i will do.
Thanks.
--
Varka Bhadram
next prev parent reply other threads:[~2015-05-29 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 8:24 [RFC bluetooth-next] mac802154: add trace functionality for driver ops Varka Bhadram
2015-05-28 8:20 ` Alexander Aring
2015-05-29 5:31 ` Varka Bhadram [this message]
2015-05-29 6:19 ` Alexander Aring
2015-05-29 6:20 ` Varka Bhadram
2015-05-31 13:22 ` Alexander Aring
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=5567F9C4.5080904@gmail.com \
--to=varkabhadram@gmail.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=varkab@cdac.in \
/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