On Thu, Mar 06, 2014 at 01:35:59PM +, David Howells wrote:
> Add tracepoints into the I2C message transfer function to retrieve the message
> sent or received. The following config options must be turned on to make use
> of the facility:
>
> CONFIG_FTRACE
> CONFIG_ENABLE_DEFAULT_T
Wolfram Sang wrote:
> > > And for the buffer: %*phN is difficult to read IMO. What about %*ph? Or
> > > %*phD at least?
> >
> > My problem with that is that it increases the length of the output by 50%
> > and there's a hard limit on how much output we may produce.
>
> Is it PAGE_SIZE? How is t
> > And for the buffer: %*phN is difficult to read IMO. What about %*ph? Or
> > %*phD at least?
>
> My problem with that is that it increases the length of the output by 50% and
> there's a hard limit on how much output we may produce.
Is it PAGE_SIZE? How is this handled when the buffer is so b
Wolfram Sang wrote:
> 'flags' are u16 and the whole range is needed -> %04x
Done. Note that %02x does not preclude more digits, but I guess it's better
to have things line up.
> for the address simply %03x should do.
Done.
> And for the buffer: %*phN is difficult to read IMO. What about %*ph
Hi David,
On Thu, Jan 09, 2014 at 09:49:54PM +, David Howells wrote:
> Add tracepoints into the I2C message transfer function to retrieve the message
> sent or received. The following config options must be turned on to make use
> of the facility:
>
> CONFIG_FTRACE
> CONFIG_ENABL
On Thu, Jan 09, 2014 at 09:49:54PM +, David Howells wrote:
> Add tracepoints into the I2C message transfer function to retrieve the message
> sent or received. The following config options must be turned on to make use
> of the facility:
>
> CONFIG_FTRACE
> CONFIG_ENABLE_DEFAULT_T
6 matches
Mail list logo
