-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXPERIMENTAL: Zephyr 3.4 update #1853
EXPERIMENTAL: Zephyr 3.4 update #1853
Conversation
20e87d9
to
c0dc4e9
Compare
@@ -72,7 +72,7 @@ void wpm_expiry_function() { k_work_submit(&wpm_work); } | |||
|
|||
K_TIMER_DEFINE(wpm_timer, wpm_expiry_function, NULL); | |||
|
|||
int wpm_init() { | |||
static int wpm_init(void) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do this become static?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency, it should have been static in the first place, it doesn't need to be an exported public symbol.
flashed my keyboard with it, the only issue i noticed is that my central side sharp memory display was not working, no errors in the log. I'll try to see why they don't work later. |
@@ -74,8 +74,8 @@ void activity_work_handler(struct k_work *work) { | |||
} else | |||
#endif /* IS_ENABLED(CONFIG_ZMK_SLEEP) */ | |||
if (inactive_time > MAX_IDLE_MS) { | |||
set_state(ZMK_ACTIVITY_IDLE); | |||
} | |||
set_state(ZMK_ACTIVITY_IDLE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation looks messed up here.
d3205ea
to
b4dc54e
Compare
I think I found two more LV_Z_DPI symbols that can be changed:
|
b4dc54e
to
55565b2
Compare
* Upstream added an equivalent fuel gauge driver, so namespace our Kconfig symbol for the MAX17048 driver.
Note for Zephyr 3.5: Previously SPI3 could be defined with the MOSI pin and nothing else when configuring WS2812B. Zephyr 3.5 seems to require a dummy SCK pin on SPI3 (just like how it was necessary for SPI0/SPI1/SPI2). |
Superseded by #1995 |
This is a placeholder for now, so folks who have reported BLE issues on Windows in particular can test latest Zephyr BLE stack and see if this improves things.
This has not gotten extensive testing yet, and should be considered highly experimental.