| Mahesh Sivasubramanian | d69058b | 2012-10-01 16:49:26 -0600 | [diff] [blame] | 1 | Subsystem Trace Points: rpm_smd |
| 2 | |
| 3 | The rpm-smd tracing system captures the events related to sending/receiving |
| 4 | messages to/from RPM hardware. The tracing system adds the following events to |
| 5 | capture the transactions with the RPM driver. |
| 6 | |
| 7 | 1) RPM send message |
| 8 | =================== |
| 9 | rpm_send_message: ctx:%s set:%s rsc_type:0%x(%s),rsc_id:i0x%x, id:%u |
| 10 | |
| 11 | The event captures the parameters of the message that was sent to the RPM. |
| 12 | |
| 13 | The 'ctx' parameters takes one of the following string constants to indicate |
| 14 | if the request was made in atomic/non-atomic context. |
| 15 | . "sleep" - non-atomic context |
| 16 | . "noslp" - atomic context |
| 17 | |
| 18 | The 'set' parameter takes one of the following string values to indicate if |
| 19 | the message affects active or sleep set value of the resource |
| 20 | . "act" - active set configuraion |
| 21 | . "slp" - sleep set configuration |
| 22 | |
| 23 | The 'rsc_type' and 'rsc_id' identify the resource whose parametes is being |
| 24 | modified. The 4 bytes string equivalent of the resource type is also displayed |
| 25 | for easier identification of resources. |
| 26 | |
| 27 | The 'id' parameter is the id that RPM uses to acknowledge the receipt of the |
| 28 | message in its ACK message |
| 29 | |
| 30 | |
| 31 | 2) RPM ack message |
| 32 | ================= |
| 33 | rpm_ack_recd: ctx:%s id:%u |
| 34 | |
| 35 | The event captures the acknowledgement messages received from the RPM after |
| 36 | successfully send a message request. |
| 37 | |
| 38 | The 'ctx' parameter has the same string constants referred to the "RPM Send |
| 39 | Message" |
| 40 | |
| 41 | The 'id' parameter is the id that RPM uses to acknowledge the receipt of the |
| 42 | message in its ACK message |
| 43 | |