View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007077 | UBoot | U-Boot | public | 2026-01-21 15:27 | 2026-01-21 15:30 |
| Reporter | mueller | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | fsimx6sx-Y2024.12 | ||||
| Target Version | osm8mp-Y2025.04 | Fixed in Version | osm8mp-Y2025.04 | ||
| Summary | 0007077: [ALL] Add mechanism to only call updates when a GPIO is set | ||||
| Description | Check an environment variable updategpio. If this is set, then only issue the update in UBoot when booting while the GPIO is set. If not set, the UBoot should behave as always, updating when a script is found. | ||||
| Forum Link | |||||
|
|
Git commit: fc38bfc25a7c6c6080963c130174cb9c1c6ddfff /* * Returns true if the condition of the GPIO description is met. * * The given GPIO description contains the number of a GPIO, followed by an * optional '-' or '_', followed by an optional "high" or "low" for active * high or active low signal. Actually only the first character is checked, * 'h' and 'H' mean "high", everything else is taken for "low". Default is * active low. * * Examples: * 123_high GPIO 123, active high * 65-low GPIO 65, active low * 13 GPIO 13, active low * 0x1fh GPIO 31, active high (this shows why a dash or * underscore before "high" or "low" makes sense) * * Remark: * We do not have any clue here what the GPIO represents and therefore we do * not assume any pad settings. So for example if the GPIO represents a button * that is floating in the released state, an external pull-up or pull-down * must be used to avoid unintentionally detecting the active state. */ |
