Lines Matching refs:message
147 * Somehow we've missed the last message. The message will be repeated
177 * Routine that handles all the logic needed to parse out the message from the remote.
183 struct keyspan_message message;
188 * In stage 0 we want to find the start of a message. The remote sends a 0xFF as filler.
189 * So the first byte that isn't a FF should be the start of a new message.
242 * message. We need to parse out the system code, button code,
248 message.system = 0;
253 message.system = message.system << 1;
257 message.system = (message.system << 1) + 1;
269 message.button = 0;
274 message.button = message.button << 1;
278 message.button = (message.button << 1) + 1;
292 message.toggle = 0;
296 message.toggle = 1;
301 "%s - Error in message, invalid toggle.\n",
313 "Bad message received, no stop bit found.\n");
317 "%s found valid message: system: %d, button: %d, toggle: %d\n",
318 __func__, message.system, message.button, message.toggle);
320 if (message.toggle != remote->toggle) {
321 keyspan_report_button(remote, message.button, 1);
322 keyspan_report_button(remote, message.button, 0);
323 remote->toggle = message.toggle;
370 * Routine used to handle a new message that has come in.
467 remote->toggle = -1; /* Set to -1 so we will always not match the toggle from the first remote message. */