On Wed, Mar 27, 2013 at 3:52 PM, G Jones <[email protected]> wrote: > Hi,
Hello > Anyone know why there are a bunch of messages like this in dmesg on a ROACH > II: > > r2case_event(): Got type 11, code 8, value 1 > attempting led toggle > About to toggle cpu_rdy pin<7>r2case_event(): Got type 11, code 8, value 0 > attempting led toggle > About to toggle cpu_rdy pin<7>r2case_event(): Got type 11, code 8, value 1 > attempting led toggle > About to toggle cpu_rdy pin<7>r2case_event(): Got type 11, code 8, value 0 > attempting led toggle tcpborphserver3 turns off the one LED while processing a katcp command (and when done turns it on again) - this is an attempt at an activity LED - this LED is routed to the front panel in our cases. This logic is implemented using the linux input event framework, and what you are seeing is the debug output in the event driver (drivers/input/misc/r2chassis.c). If you wish to remove a couple of system calls in overhead you can remove the driver and tcpborphserver3 then won't do this. TLDR: Nothing to worry about regards marc
