Backlight abstraction and other changes (#439)

* redoes matrix pins, abstracts backlight code for B5,6,7

* slimming down keyboard stuff, backlight breathing implemented

* don't call backlight init when no pin

* cleans up user/kb/quantum calls, keyboard files

* fix pvc atomic

* replaces CHANNEL with correct var in breathing

* removes .hexs, updates readmes, updates template

* cleans-up clueboards, readmes to lowercase

* updates readme

keyboards/kc60/config.h

@@ -50,6 +50,8 @@ along with this program.  If not, see <http://www.gnu.org/licenses/>.
 #define MATRIX_COL_PINS { F0, F1, E6, C7, C6, B7, D4, B1, B0, B5, B4, D7, D6, B3 }
 #define UNUSED_PINS
 
+#define BACKLIGHT_PIN B6
+
 /* COL2ROW or ROW2COL */
 #define DIODE_DIRECTION COL2ROW
 

keyboards/kc60/kc60.c

@@ -1,111 +1 @@
 #include "kc60.h"
-
-__attribute__ ((weak))
-  void matrix_init_user(void) {
-    // leave this function blank - it can be defined in a keymap file
-  };
-
-__attribute__ ((weak))
-  void matrix_scan_user(void) {
-    // leave this function blank - it can be defined in a keymap file
-  }
-
-__attribute__ ((weak))
-  bool process_action_user(keyrecord_t *record) {
-    // leave this function blank - it can be defined in a keymap file
-    return true;
-  }
-
-__attribute__ ((weak))
-  void led_set_user(uint8_t usb_led) {
-    // leave this function blank - it can be defined in a keymap file
-  }
-
-void matrix_init_kb(void) {
-  // put your keyboard start-up code here
-  // runs once when the firmware starts up
-
-#ifdef BACKLIGHT_ENABLE
-  backlight_init_ports();
-#endif
-
-  matrix_init_user();
-}
-
-void matrix_scan_kb(void) {
-  // put your looping keyboard code here
-  // runs every cycle (a lot)
-
-  matrix_scan_user();
-}
-
-bool process_action_kb(keyrecord_t *record) {
-  // put your per-action keyboard code here
-  // runs for every action, just before processing by the firmware
-
-  return process_action_user(record);
-}
-
-void led_set_kb(uint8_t usb_led) {
-  // put your keyboard LED indicator (ex: Caps Lock LED) toggling code here
-
-  led_set_user(usb_led);
-}
-
-#ifdef BACKLIGHT_ENABLE
-#define CHANNEL OCR1B
-
-void backlight_init_ports()
-{
-
-  // Setup PB6 as output and output low.
-  DDRB |= (1<<6);
-  PORTB &= ~(1<<6);
-
-  // Use full 16-bit resolution. 
-  ICR1 = 0xFFFF;
-
-  // I could write a wall of text here to explain... but TL;DW
-  // Go read the ATmega32u4 datasheet.
-  // And this: http://blog.saikoled.com/post/43165849837/secret-konami-cheat-code-to-high-resolution-pwm-on
-
-  // Pin PB7 = OCR1C (Timer 1, Channel C)
-  // Compare Output Mode = Clear on compare match, Channel C = COM1B1=1 COM1C0=0
-  // (i.e. start high, go low when counter matches.)
-  // WGM Mode 14 (Fast PWM) = WGM13=1 WGM12=1 WGM11=1 WGM10=0
-  // Clock Select = clk/1 (no prescaling) = CS12=0 CS11=0 CS10=1
-
-  TCCR1A = _BV(COM1B1) | _BV(WGM11); // = 0b00001010;
-  TCCR1B = _BV(WGM13) | _BV(WGM12) | _BV(CS10); // = 0b00011001;
-
-  backlight_init();
-}
-
-void backlight_set(uint8_t level)
-{
-  // Prevent backlight blink on lowest level
-  PORTB &= ~(_BV(PORTB6));
-
-  if ( level == 0 )
-  {
-    // Turn off PWM control on PB6, revert to output low.
-    TCCR1A &= ~(_BV(COM1B1));
-    CHANNEL = 0x0;
-  }
-  else if ( level == BACKLIGHT_LEVELS)
-  {
-    // Turn on PWM control of PB6
-    TCCR1A |= _BV(COM1B1);
-    // Set the brightness
-    CHANNEL = 0xFFFF;
-  }
-  else        
-  {
-    // Turn on PWM control of PB6
-    TCCR1A |= _BV(COM1B1);
-    // Set the brightness
-    CHANNEL = 0xFFFF >> ((BACKLIGHT_LEVELS - level) * ((BACKLIGHT_LEVELS + 1) / 2));
-  }
-}
-
-#endif

keyboards/kc60/kc60.h

@@ -1,13 +1,7 @@
 #ifndef KC60_H
 #define KC60_H
 
-#include "matrix.h"
-#include "keymap.h"
-#ifdef BACKLIGHT_ENABLE
-#include "backlight.h"
-#endif
-#include <avr/io.h>
-#include <stddef.h>
+#include "quantum.h"
 
 // This a shortcut to help you visually see your layout.
 // The first section contains all of the arguements
@@ -26,11 +20,4 @@
   {  K40,  K41,  K42,  KC_NO,  KC_NO,  K45,  KC_NO,  KC_NO,  KC_NO,  KC_NO,K4A,  K4B,  K4C,  K4D  }   \
 }
 
-void matrix_init_user(void);
-void matrix_scan_user(void);
-bool process_action_user(keyrecord_t *record);
-
-void led_set_user(uint8_t usb_led);
-void backlight_init_ports(void);
-
 #endif

keyboards/kc60/keymaps/stanleylai/readme.md

@@ -4,7 +4,7 @@ Stanley Lai's Split Right Shift with Dedicated Arrow Keys
 ![Image of KC60 with RGB Underglow](../ws2812/ws2812_example.jpg)
 
 ## Quantum MK Firmware
-For the full Quantum feature list, see [the parent README.md](/README.md).
+For the full Quantum feature list, see [the parent readme.md](/readme.md).
 
 ## Keymap Notes
 - Keymap setup with split Right Shift in mind.

keyboards/kc60/keymaps/ws2812/readme.md

@@ -4,7 +4,7 @@ KC60 with WS2812 RGB Underglow
 ![Image of KC60 with RGB Underglow](ws2812_example.jpg)
 
 ## Quantum MK Firmware
-For the full Quantum feature list, see [the parent README.md](/README.md).
+For the full Quantum feature list, see [the parent readme.md](/readme.md).
 
 ## WS2812 Support
 By default, it is now setup for 16 LEDs on the PF5 breakout pin. See [included image](ws2812_wiring.jpg) for wiring reference.

keyboards/kc60/readme.md

@@ -2,7 +2,7 @@ KC60 (version 2.0) keyboard firmware
 ======================
 
 ## Quantum MK Firmware
-For the full Quantum feature list, see [the parent README.md](/README.md).
+For the full Quantum feature list, see [the parent readme.md](/readme.md).
 
 ## Building
 Download or clone the whole firmware and navigate to the keyboards/kc60 folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use the Teensy Loader to program your .hex file.
@@ -13,7 +13,7 @@ Depending on which keymap you would like to use, you will have to compile slight
 To build with the default keymap, simply run `make`.
 
 ### Other Keymaps
-Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create file named `<name>.c` in the keymaps folder, and see keymap document (you can find in top README.md) and existent keymap files.
+Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create file named `<name>.c` in the keymaps folder, and see keymap document (you can find in top readme.md) and existent keymap files.
 
 To build the firmware binary hex file with a keymap just do `make` with `KEYMAP` option like:
 ```