Skip to content
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

Document all packages and peripherals #29

Closed
42 tasks done
jessebraham opened this issue Mar 7, 2022 · 4 comments · Fixed by #680
Closed
42 tasks done

Document all packages and peripherals #29

jessebraham opened this issue Mar 7, 2022 · 4 comments · Fixed by #680
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@jessebraham
Copy link
Member

jessebraham commented Mar 7, 2022

It's that job nobody wants to do!

This is a long-term project, as there's not much point documenting drivers until their interfaces are relatively stable.

Each HAL package should have top-level documentation at the very least. Peripheral drivers should additionally be documented, preferably even containing simple examples as doc tests.


Beginning with module-level documentation, here are all modules which are currently exported by any of the chip-specific HAL packages:

  • adc
  • aes
  • analog
  • assist_debug
  • clock
  • cpu_control
  • dac
  • delay
  • dma
  • efuse
  • esp_riscv_rt
  • gpio
  • i2c
  • i2s
  • interrupt
  • ledc
  • lp_core
  • macros
  • mcpwm
  • otg_fs
  • pcnt
  • peripheral
  • peripherals
  • prelude
  • psram
  • radio
  • reset
  • rmt
  • rng
  • rom
  • rsa
  • rtc_cntl
  • sha
  • spi
  • system
  • systimer
  • timer
  • trapframe
  • twai
  • uart
  • ulp_core
  • usb_serial_jtag
@jessebraham jessebraham added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Mar 7, 2022
@IshanDaga
Copy link

Hi Jesse,
New to Rust, though I have been using the ESP-IDF for the last 15 or so months.

I'd like to be able to contribute to this project and learn rust while I'm at it - is this a good place to start?

@jessebraham
Copy link
Member Author

@IshanDaga if you are willing to work on this then yes, that would be awesome! This is definitely one of our weaker points currently so it'd be great to improve this.

In general (with the exception of the chip support label) any open issue is fair game; if it's assigned to somebody already just ask if they're actively working on it, there's a good chance they are not and that you can take it over 😁

@jessebraham
Copy link
Member Author

I've documented the Rng peripheral in #650, which can be loosely used as a model for other peripherals. @playfulFence is also working on a number of drivers' documentation.

@jessebraham
Copy link
Member Author

With #680 merged I'm happy to call this "done". There is of course more work to do, but all packages and modules have at least some documentation now.

@SergioGasquez SergioGasquez linked a pull request Aug 9, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants