···33333434VPATH += $(QUANTUM_DIR)/logging
3535# Fall back to lib/printf if there is no platform provided print
3636-ifeq ("$(wildcard $(TMK_PATH)/common/$(PLATFORM_KEY)/printf.mk)","")
3636+ifeq ("$(wildcard $(PLATFORM_PATH)/$(PLATFORM_KEY)/printf.mk)","")
3737 include $(QUANTUM_PATH)/logging/print.mk
3838+else
3939+ include $(PLATFORM_PATH)/$(PLATFORM_KEY)/printf.mk
3840endif
39414042ifeq ($(strip $(DEBUG_MATRIX_SCAN_RATE_ENABLE)), yes)
+1-1
docs/feature_layers.md
···45454646Layers stack on top of each other in numerical order. When determining what a keypress does, QMK scans the layers from the top down, stopping when it reaches the first active layer that is not set to `KC_TRNS`. As a result if you activate a layer that is numerically lower than your current layer, and your current layer (or another layer that is active and higher than your target layer) has something other than `KC_TRNS`, that is the key that will be sent, not the key on the layer you just activated. This is the cause of most people's "why doesn't my layer get switched" problem.
47474848-Sometimes, you might want to switch between layers in a macro or as part of a tap dance routine. `layer_on` activates a layer, and `layer_off` deactivates it. More layer-related functions can be found in [action_layer.h](https://github.com/qmk/qmk_firmware/blob/master/tmk_core/common/action_layer.h).
4848+Sometimes, you might want to switch between layers in a macro or as part of a tap dance routine. `layer_on` activates a layer, and `layer_off` deactivates it. More layer-related functions can be found in [action_layer.h](https://github.com/qmk/qmk_firmware/blob/master/quantum/action_layer.h).
49495050## Functions :id=functions
5151
+1-1
docs/fr-fr/faq_keymap.md
···6677Regardez [Keycodes](keycodes.md) pour une liste des keycodes disponibles. Certains keycodes spécifiques ont des documentations plus complètes de disponible.
8899-Les keycodes sont définies dans [common/keycode.h](https://github.com/qmk/qmk_firmware/blob/master/tmk_core/common/keycode.h).
99+Les keycodes sont définies dans [common/keycode.h](https://github.com/qmk/qmk_firmware/blob/master/quantum/keycode.h).
10101111## Quels sont les keycodes par défaut ?
1212
+1-1
docs/internals_gpio_control.md
···4455## Functions :id=functions
6677-The following functions provide basic control of GPIOs and are found in `tmk_core/common/<platform>/gpio.h`.
77+The following functions provide basic control of GPIOs and are found in `platforms/<platform>/gpio.h`.
8899|Function |Description | Old AVR Examples | Old ChibiOS/ARM Examples |
1010|------------------------|--------------------------------------------------|-------------------------------------------------|-------------------------------------------------|
···2424 - no "old-school" or other low-level GPIO/I2C/SPI functions may be used -- must use QMK abstractions unless justifiable (and laziness is not valid justification)
2525 - timing abstractions should be followed too:
2626 - `wait_ms()` instead of `_delay_ms()` (remove `#include <util/delay.h>` too)
2727- - `timer_read()` and `timer_read32()` etc. -- see [timer.h](https://github.com/qmk/qmk_firmware/blob/master/tmk_core/common/timer.h) for the timing APIs
2727+ - `timer_read()` and `timer_read32()` etc. -- see [timer.h](https://github.com/qmk/qmk_firmware/blob/master/platforms/timer.h) for the timing APIs
2828 - if you think a new abstraction is useful, you're encouraged to:
2929 - prototype it in your own keyboard until it's feature-complete
3030 - discuss it with QMK Collaborators on Discord
···88#include "quantum.h"
991010#ifdef EE_HANDS
1111-# include "tmk_core/common/eeprom.h"
1111+# include "eeprom.h"
1212# include "eeconfig.h"
1313#endif
1414
···991010#include "raw_hid.h"
1111#include "dynamic_keymap.h"
1212-#include "tmk_core/common/eeprom.h"
1212+#include "eeprom.h"
1313#include "version.h" // for QMK_BUILDDATE used in EEPROM magic
14141515/* Artificial delay added to get media keys to work in the encoder*/