From: Jeremy Kerr <jk-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
To: Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>,
Christopher Bostic
<cbostic-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
andrew-zrmu5oMJ5Fs@public.gmane.org,
alistair-Y4h6yKqj69EXC2x5gXVKYQ@public.gmane.org,
benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v8 16/24] drivers/fsi: Add tracepoints for low-level operations
Date: Thu, 8 Jun 2017 10:06:16 +0800 [thread overview]
Message-ID: <4441a1ba-e66e-368a-cc07-8e3859dc8c13@ozlabs.org> (raw)
In-Reply-To: <20170607151610.52f7bc88-f9ZlEuEWxVcJvu8Pb33WZ0EMvNT87kid@public.gmane.org>
Hi Steven,
Thanks for checking this out.
>> +TRACE_EVENT(fsi_master_write,
>> + TP_PROTO(const struct fsi_master *master, int link, int id,
>> + uint32_t addr, size_t size, const void *data),
>> + TP_ARGS(master, link, id, addr, size, data),
>> + TP_STRUCT__entry(
>> + __field(int, master_idx)
>> + __field(int, link)
>> + __field(int, id)
>> + __field(__u32, addr)
>> + __field(size_t, size)
>> + __field(__u32, data)
>> + ),
>> + TP_fast_assign(
>> + __entry->master_idx = master->idx;
>> + __entry->link = link;
>> + __entry->id = id;
>> + __entry->addr = addr;
>> + __entry->size = size;
>> + __entry->data = 0;
>> + memcpy(&__entry->data, data, size);
>
>
> Um, can size ever be greater than 4? If so, this is a bug.
No, size will only ever be 1, 2, or 4, as they're the only valid FSI bus
transactions. Hence storing ->data as a u32 to keep things simple.
> I think you may want to use a dynamic array here.
>
> TP_STRUCT__entry(
> [..]
> __dynamic_array(char, data, size)
> [..]
>
> TP_fast_assign(
> [..]
> memcpy(__get_dynamic_array(data), data, size);
> [..]
>
> TP_printk(...
> [..]
> __entry->size,
> __get_dynamic_array(data)
>
> You may also want to look at __print_array() too.
The %ph specifier seems to do a decent job though...
Cheers,
Jeremy
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-08 2:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 21:08 [PATCH v8 00/24] FSI device driver implementation Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 03/24] drivers/fsi: Add empty master scan Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 04/24] lib: Add crc4 module Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 05/24] drivers/fsi: Add slave & master read/write APIs Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 08/24] drivers/fsi: Set slave SMODE to init communication Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 09/24] drivers/fsi: scan slaves & register devices Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 10/24] drivers/fsi: Add device read/write/peek API Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 11/24] drivers/fsi: Add master unscan Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 12/24] drivers/fsi: Add documentation for GPIO bindings Christopher Bostic
[not found] ` <20170606210859.80431-1-cbostic-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-06-06 21:08 ` [PATCH v8 01/24] drivers/fsi: Add fsi master definition Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 02/24] drivers/fsi: Add slave definition Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 06/24] drivers/fsi: Set up links for slave communication Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 07/24] drivers/fsi: Implement slave initialisation Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 13/24] drivers/fsi: Add client driver register utilities Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 15/24] drivers/fsi: expose direct-access slave API Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 14/24] drivers/fsi: Add sysfs files for FSI master & slave accesses Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 16/24] drivers/fsi: Add tracepoints for low-level operations Christopher Bostic
2017-06-07 19:16 ` Steven Rostedt
[not found] ` <20170607151610.52f7bc88-f9ZlEuEWxVcJvu8Pb33WZ0EMvNT87kid@public.gmane.org>
2017-06-08 2:06 ` Jeremy Kerr [this message]
2017-06-06 21:08 ` [PATCH v8 17/24] drivers/fsi: Add error handling for slave Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 18/24] drivers/fsi: Document FSI master sysfs files in ABI Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 19/24] drivers/fsi: Add GPIO based FSI master Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 20/24] drivers/fsi/gpio: Add tracepoints for GPIO master Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 21/24] drivers/fsi: Add SCOM FSI client device driver Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 22/24] drivers/fsi: Add hub master support Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 23/24] drivers/fsi: Use asynchronous slave mode Christopher Bostic
2017-06-06 21:08 ` [PATCH v8 24/24] drivers/fsi: Add module license to core driver Christopher Bostic
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=4441a1ba-e66e-368a-cc07-8e3859dc8c13@ozlabs.org \
--to=jk-mnsaurcq41sdnm+yrofe0a@public.gmane.org \
--cc=alistair-Y4h6yKqj69EXC2x5gXVKYQ@public.gmane.org \
--cc=andrew-zrmu5oMJ5Fs@public.gmane.org \
--cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
--cc=cbostic-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=joel-U3u1mxZcP9KHXe+LvDLADg@public.gmane.org \
--cc=linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).