Re: [PATCH] Tracing events with GPIOs
From: Jean-Jacques Hiblot
Date: Fri Jan 03 2014 - 12:51:34 EST
2014/1/2 Linus Walleij <linus.walleij@xxxxxxxxxx>:
> On Thu, Dec 19, 2013 at 7:52 AM, Alexandre Courbot <gnurou@xxxxxxxxx> wrote:
>> On Tue, Dec 17, 2013 at 9:22 AM, Jean-Jacques Hiblot
>> <jjhiblot@xxxxxxxxxxxxxxx> wrote:
>>> This patch implements a new tracing mechanism based on kprobes and using GPIO.
>>> Debugging with GPIO is very common in the embedded world. At least for those of us
>>> fortunate enough to have an oscilloscope or a logic analyzer on their bench...
>>> This is especially true if the issue results of a hardware/sofware interaction.
>>> Typical use cases are :
>>> * mixed software/hardware debugging. For example when the software detects a
>>> situation of interest (typically an error) it toggles a GPIO to trigger the
>>> oscilloscope acquisition.
>>> * direct latency/duration measurements.
>>> To trig the oscilloscope whenever a mmc command error:
>>> echo "p:my_mmc_blk_error mmc_blk_cmd_error gpiopulse@13" > /sys/kernel/debug/tracing/kprobe_events
>>> echo 1 > /sys/kernel/debug/tracing/events/kprobes/my_mmc_blk_error/enable
> I've never seen the whole patch.
> Can you please repost this and include linux-gpio@xxxxxxxxxxxxxxx and also
> me on the To: line?
I'll repost the patch.
It has evolved a bit since you've been included in the cc list. It's
now based upon the 'event trigger' and more important for you, it
doesn't request nor configure the GPIO before using it. The reason is
that how to do this is still being discussed with Alexandre.
> Linus Walleij
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/