RT-Thread / RT-Thread/rt-thread
spi driver issue: rt_hw_spi_device_attach function
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
rt_hw_spi_device_attach()
This function is defined differently in different BSP
- For example,
- STM32: rt_err_t rt_hw_spi_device_attach(const char *bus_name, const char device_name, GPIO_TypeDef cs_gpiox, uint16_t cs_gpio_pin);
- imxrt: rt_err_t rt_hw_spi_device_attach(const char *bus_name, const char *device_name, rt_uint32_t pin);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating rt_hw_spi_device_attach in the STM32 and imxrt BSPs and comparing their callers. Clarify the intended common signature and scope before changing anything; done means the API decision is applied consistently across the affected BSPs and their relevant builds or tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100