Add keyboard Q1

[lokher]

Description

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[sigprof]

Did you test the behavior of the keyboard when the DIP switch is closed, and you try to put the computer into a sleep/suspend state? I suspect that the keyboard will immediately wake up the computer in this case, because the DIP switch is a part of the matrix, and anything which looks like a pressed key will be considered as a wakeup request.

You may be able to work around this problem by using the obscure MATRIX_MASKED feature:

1. Enable the feature in config.h:

#define MATRIX_MASKED

2. Configure the mask in q1.c:

const matrix_row_t matrix_mask[] = {
    0b0111111111111101,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
};

(the bit at {0, 1} needs to be reset to 0, so that the DIP switch state would be masked away).

The matrix mask affects matrix_get_row() and any dependent functions (such as wakeup check and key event processing), but does not affect peek_matrix(), which is used by the DIP switch code to get the matrix state.

[lokher]

I did some tests 2 minutes ago, and the computer stayed in sleep/suspend state what ever the DIP switch state was. The DIP switch dosen't send any keycode in my firmware, I don't think it can wake up the computer.
Thank you for reminding.

Did you test the behavior of the keyboard when the DIP switch is closed, and you try to put the computer into a sleep/suspend state? I suspect that the keyboard will immediately wake up the computer in this case, because the DIP switch is a part of the matrix, and anything which looks like a pressed key will be considered as a wakeup request.

You may be able to work around this problem by using the obscure MATRIX_MASKED feature:

1. Enable the feature in config.h:

#define MATRIX_MASKED

1. Configure the mask in q1.c:

const matrix_row_t matrix_mask[] = {
    0b0111111111111101,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
    0b0111111111111111,
};

(the bit at {0, 1} needs to be reset to 0, so that the DIP switch state would be masked away).

The matrix mask affects matrix_get_row() and any dependent functions (such as wakeup check and key event processing), but does not affect peek_matrix(), which is used by the DIP switch code to get the matrix state.

[drashna]

Thanks!