shell_lock: don't set CONFIG_SHELL_SHUTDOWN_ON_EXIT#19268
Merged
bors[bot] merged 2 commits intoRIOT-OS:masterfrom May 28, 2023
Merged
shell_lock: don't set CONFIG_SHELL_SHUTDOWN_ON_EXIT#19268bors[bot] merged 2 commits intoRIOT-OS:masterfrom
bors[bot] merged 2 commits intoRIOT-OS:masterfrom
Conversation
benpicco
requested review from
MichelRottleuthner,
aabadie,
fjmolinas,
leandrolanzieri and
smlng
as code owners
benpicco
requested review from
HendrikVE and
maribu
and removed request for
MichelRottleuthner,
aabadie,
fjmolinas,
leandrolanzieri and
smlng
github-actions
bot
added
Area: sys
benpicco
added
Type: bug
HendrikVE
approved these changes
Feb 10, 2023
Member
|
In the documentation I can find on SHUTDOWN_ON_EXIT, this is about the behavior when receiving a ^D (which is often irrecoverable). Have you tested how locking interacts with the ^D stdio closing that was observed on Ubuntu? This looks to me like there are two different concepts entangled in one effect. Like, if ^D closes stdin for good, even a shell-locked system should exit when receiving a ^D. If we want to maintain support for "we close when stdin goes bad" (which may or may not be the case, depending on how modern systems work), the exiting shell may need to report that to distinguish between "I've been locked" and "My stdin went away". |
github-actions
bot
added
Area: sys
Contributor
Author
|
Ok, the shell is now also locked on ctrl-d |
maribu
approved these changes
May 26, 2023
Contributor
Author
|
bors merge |
bors bot
added a commit
that referenced
this pull request
May 27, 2023
19268: shell_lock: don't set CONFIG_SHELL_SHUTDOWN_ON_EXIT r=benpicco a=benpicco 19629: cpu/stm32/periph/adc: fix setting ADC clock r=benpicco a=Enoch247 ### Contribution description The current implementation uses the core clock frequency to calculate the needed prescalar to achieve a given ADC clock frequency. This is incorrect. This patch fixes the calculation to use the correct source clock (PCKLK2 ie APB2). It also changes the defined max clock rate to use the frequency macro to improve readability. I based on code similarity. I believe the gd32v CPU may need this same fix, but I am not familiar with that MCU. ### Testing procedure I tested this on a nucleo-f767zi. The the MCU's reference manual is in agreement with what I have implemented here. I spot checked references manuals for a random [STM32F1](https://www.st.com/resource/en/reference_manual/cd00171190-stm32f101xx-stm32f102xx-stm32f103xx-stm32f105xx-and-stm32f107xx-advanced-arm-based-32-bit-mcus-stmicroelectronics.pdf) and [STM32F2](https://www.st.com/resource/en/reference_manual/rm0033-stm32f205xx-stm32f207xx-stm32f215xx-and-stm32f217xx-advanced-armbased-32bit-mcus-stmicroelectronics.pdf), and they are clocked similar to the F7 I have. ### Issues/PRs references None known. 19670: cpu/stm32: stm32f4 BRR from BSRR r=benpicco a=kfessel ### Contribution description sometimes one wants to save one instruction :) just write the bits we need to write. ### Testing procedure tests/periph/gpio_ll tests this ### Issues/PRs references `@maribu` might know some reference maybe #19407 Co-authored-by: Benjamin Valentin <[email protected]> Co-authored-by: Benjamin Valentin <[email protected]> Co-authored-by: Joshua DeWeese <[email protected]> Co-authored-by: Karl Fessel <[email protected]>
Contributor
|
Build failed (retrying...): |
Contributor
|
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution description
We always want
CONFIG_SHELL_SHUTDOWN_ON_EXITnot to be set ifshell_lockus used asshell_lockwill exit the shell to lock it.Testing procedure
Run
tests/shell_lockonnative(or any othernativeapp withshell_lockenabled)Issues/PRs references