| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | embassy-rp: doc comment spelling pass | Rob Wells | 2025-10-27 | 1 | -1/+1 |
| | | | | | | All changes but one are to documentation comments, and one to an ordinary comment. | ||||
| * | Rustfmt for edition 2024. | Dario Nieuwenhuis | 2025-10-06 | 1 | -2/+2 |
| | | |||||
| * | removed the rp2040 flag from the dormant function | Phirks | 2025-08-03 | 1 | -3/+1 |
| | | |||||
| * | Add rand-core v0.9 support. | Dario Nieuwenhuis | 2025-05-18 | 1 | -7/+42 |
| | | | | | Co-Authored-By: Aurélien Jacobs <[email protected]> | ||||
| * | removed one line too many | 1-rafael-1 | 2025-05-13 | 1 | -0/+1 |
| | | |||||
| * | Changes after review: copypasted doc comment fixed and no cfg gates to panic ↵ | 1-rafael-1 | 2025-05-13 | 1 | -14/+3 |
| | | | | | on failing pll config in init() | ||||
| * | Refactor CoreVoltage enum, separate for rp2040 and rp235x | 1-rafael-1 | 2025-05-12 | 1 | -56/+42 |
| | | |||||
| * | Add ClockError enum and update system_freq to return Result for error handling | 1-rafael-1 | 2025-05-12 | 1 | -19/+47 |
| | | |||||
| * | limit CoreVoltage eum to values up to 1.30V, because we do not support ↵ | 1-rafael-1 | 2025-05-12 | 1 | -120/+21 |
| | | | | | unlocking higher voltages | ||||
| * | rp235x overclocking | 1-rafael-1 | 2025-05-11 | 1 | -32/+297 |
| | | |||||
| * | Clarify comment for CoreVoltage enum regarding V1_20 | 1-rafael-1 | 2025-05-07 | 1 | -1/+1 |
| | | |||||
| * | Changes after review | 1-rafael-1 | 2025-05-07 | 1 | -16/+35 |
| | | |||||
| * | rework init() | 1-rafael-1 | 2025-05-05 | 1 | -153/+103 |
| | | |||||
| * | first batch of changes after review | 1-rafael-1 | 2025-05-02 | 1 | -209/+115 |
| | | |||||
| * | - two more doc examples test ignored | 1-rafael-1 | 2025-05-01 | 1 | -8/+214 |
| | | | | | | - added tests for the new calculations and fixed an overflow issue these tests surfaced. - Activate brownout detection. | ||||
| * | add manual overclock example, finalize API, cleanup | 1-rafael-1 | 2025-05-01 | 1 | -128/+140 |
| | | |||||
| * | refactoring to have higher and lower level api | 1-rafael-1 | 2025-04-29 | 1 | -207/+339 |
| | | |||||
| * | first working draft | 1-rafael-1 | 2025-04-28 | 1 | -169/+489 |
| | | |||||
| * | Add core voltage scaling options and PLL parameter finder for RP2040 | 1-rafael-1 | 2025-04-26 | 1 | -14/+228 |
| | | |||||
| * | Remove Peripheral trait, rename PeripheralRef->Peri. | Dario Nieuwenhuis | 2025-03-27 | 1 | -17/+8 |
| | | |||||
| * | make rustfmt happy | JuliDi | 2025-03-19 | 1 | -2/+0 |
| | | |||||
| * | fix wrong funcsel on rp2350 gpout/gpin | JuliDi | 2025-03-19 | 1 | -0/+14 |
| | | |||||
| * | fix: enable RP2350 watchdog tick generator | Adrian Wowk | 2025-01-15 | 1 | -1/+6 |
| | | |||||
| * | rp: Run RP235x at 150 MHz instead of 125 | Sebastian Quilitz | 2024-10-05 | 1 | -0/+3 |
| | | |||||
| * | Disable pad isolation on clock in/out pins | Caleb Jamison | 2024-09-16 | 1 | -1/+11 |
| | | |||||
| * | Set up timer0 tick when initializing clocks | Ugljesa Jovanovic | 2024-08-24 | 1 | -1/+7 |
| | | |||||
| * | Fix docs, ci | Caleb Jamison | 2024-08-12 | 1 | -1/+1 |
| | | |||||
| * | Fix CI, rename private feature, address comments from dirbaio. | Caleb Jamison | 2024-08-12 | 1 | -10/+11 |
| | | |||||
| * | Initial rp235x support | Caleb Jamison | 2024-08-08 | 1 | -13/+71 |
| | | | | | Examples have been run, but there is not yet a test suite. | ||||
| * | Fix: typo | QWS | 2024-05-14 | 1 | -1/+1 |
| | | |||||
| * | In the start_xosc function, the frequency range is set twice. Remove the ↵ | QWS | 2024-05-13 | 1 | -4/+0 |
| | | | | | redundant one. | ||||
| * | rp: remove mod sealed. | Dario Nieuwenhuis | 2024-04-05 | 1 | -6/+5 |
| | | |||||
| * | fix: CI | Rafael Bachmann | 2024-03-25 | 1 | -0/+2 |
| | | |||||
| * | fix minor clippy lints in embassy_rp | Rafael Bachmann | 2024-03-18 | 1 | -3/+1 |
| | | |||||
| * | docs: document all embassy-rp public apis | Ulf Lilleengen | 2023-12-19 | 1 | -6/+91 |
| | | | | | Enable missing doc warnings. | ||||
| * | docs: embassy-rp rustdoc and refactoring | Ulf Lilleengen | 2023-12-19 | 1 | -0/+26 |
| | | |||||
| * | RP2040: Fixes as per PR | Michael van Niekerk | 2023-08-30 | 1 | -1/+1 |
| | | |||||
| * | RP2040: Fixes as per PR | Michael van Niekerk | 2023-08-30 | 1 | -1/+1 |
| | | |||||
| * | RP2040: Fixes as per PR | Michael van Niekerk | 2023-08-30 | 1 | -2/+2 |
| | | |||||
| * | RP2040: XOSC delay multiplier | Michael van Niekerk | 2023-08-30 | 1 | -1/+1 |
| | | |||||
| * | RP2040: XOSC delay multiplier | Michael van Niekerk | 2023-08-30 | 1 | -3/+5 |
| | | |||||
| * | rp: add generic dormant-sleep functionality | pennae | 2023-08-05 | 1 | -0/+130 |
| | | | | | | | | | | | | | | | | | this is "generic" in that it doesn't require the user to set up anything specific to go to dormant sleep, unlike the C sdk which requires clock sources to be configured explicitly and doesn't much care about PLLs. we will instead take a snapshot of the current clock configuration, switch to a known clock source (very slow rosc, in this case), go to sleep, and on wakeup undo everything we've done (ensuring stability of PLLs and such). tested locally, but adding tests to HIL seems infeasible. we'd need at least another pico or extensive modifications to teleprobe since dormant-sleep breaks SWD (except to rescue-dp), neither of which is feasible at this point. if we *did* want to add tests we should check for both rtc wakeups (with an external rtc clock source) and gpio wakeups. | ||||
| * | rp: rename gpio::Pin::io to gpio::Pin::gpio | pennae | 2023-07-31 | 1 | -4/+4 |
| | | | | | | | we'll need access to the pin io bank registers for an upcoming fix, and having both `io` and `io_bank` or similar can get confusing quickly. rename `io` to `gpio` to avoid this, and also match the type while there. | ||||
| * | Rename embassy-hal-common to embassy-hal-internal, document it's for ↵ | Dario Nieuwenhuis | 2023-07-28 | 1 | -1/+1 |
| | | | | | internal use only. (#1700) | ||||
| * | RP: Don't reset RTC in Clock::init. Updated example. | Henrik Berg | 2023-07-12 | 1 | -0/+2 |
| | | |||||
| * | Update rp-pac. | Dario Nieuwenhuis | 2023-06-29 | 1 | -46/+46 |
| | | |||||
| * | rp: update rp-pac. | Dario Nieuwenhuis | 2023-06-16 | 1 | -49/+33 |
| | | |||||
| * | rp/clocks: comment out all gpin handling for now | pennae | 2023-05-17 | 1 | -66/+71 |
| | | | | | | | gpin clock sources aren't going to be very useful during cold boot and thus require runtime clock reconfig. once we get there we can use this for reference. or maybe we can't, only time will tell. | ||||
| * | rp/clocks: remove superfluous clock actions | pennae | 2023-05-17 | 1 | -8/+0 |
| | | | | | | the rtc doesn't have to be disabled since it's always clocked from ref, and the watchdog doesn't need to be configured twice. | ||||
| * | rp/clocks: require GpinPin for gpin config | pennae | 2023-05-17 | 1 | -18/+43 |
| | | | | | | | | | | | | we'll take static ownership of an entire pin (not just a limited reference), otherwise we cannot at all guarantee that the pin will not be reused for something else while still in use. in theory we could limit the liftime of this use, but that would require attaching lifetimes to ClockConfig (and subsequently the main config), passing those through init(), and returning an object that undoes the gpin configuration on drop. that's a lot unnecessary support code while we don't have runtime clock reconfig. | ||||
