summaryrefslogtreecommitdiff
path: root/docs/feature_led_indicators.md
diff options
context:
space:
mode:
authorRyan <fauxpark@gmail.com>2024-02-17 00:18:26 +1100
committerGitHub <noreply@github.com>2024-02-17 00:18:26 +1100
commitb8646bc40bd616167da150f6da4eda372f7de23d (patch)
tree8029e1180ff0666a07d8ef896461333a836611fa /docs/feature_led_indicators.md
parent6890c1aeb82c0c2239841db57e1bd99c3a0651a5 (diff)
Update naming convention for GPIO control macros (#23085)
Diffstat (limited to 'docs/feature_led_indicators.md')
-rw-r--r--docs/feature_led_indicators.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/feature_led_indicators.md b/docs/feature_led_indicators.md
index 1f71cdb1c8..b35a174490 100644
--- a/docs/feature_led_indicators.md
+++ b/docs/feature_led_indicators.md
@@ -56,16 +56,16 @@ This is a template indicator function that can be implemented on keyboard level
bool led_update_kb(led_t led_state) {
bool res = led_update_user(led_state);
if(res) {
- // writePin sets the pin high for 1 and low for 0.
+ // gpio_write_pin sets the pin high for 1 and low for 0.
// In this example the pins are inverted, setting
// it low/0 turns it on, and high/1 turns the LED off.
// This behavior depends on whether the LED is between the pin
// and VCC or the pin and GND.
- writePin(B0, !led_state.num_lock);
- writePin(B1, !led_state.caps_lock);
- writePin(B2, !led_state.scroll_lock);
- writePin(B3, !led_state.compose);
- writePin(B4, !led_state.kana);
+ gpio_write_pin(B0, !led_state.num_lock);
+ gpio_write_pin(B1, !led_state.caps_lock);
+ gpio_write_pin(B2, !led_state.scroll_lock);
+ gpio_write_pin(B3, !led_state.compose);
+ gpio_write_pin(B4, !led_state.kana);
}
return res;
}