Watchdog conflicts OMAP and TWL4030
Open
Nobody has claimed this yet.
auto-migrated
Priority-Medium
Type-Defect
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
It is impossible to enable both:
CONFIG_OMAP_WATCHDOG=y
CONFIG_TWL4030_WATCHDOG=y
Both are using the same minor number in the code: WATCHDOG_MINOR.
```
Original issue reported on code.google.com by `gilzha...@gmail.com` on 31 Aug 2011 at 8:26
Contributor guide
No contributing guide indexed for this repository
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
Locate the OMAP and TWL4030 watchdog implementations and inspect their shared WATCHDOG_MINOR usage. The issue is done when CONFIG_OMAP_WATCHDOG and CONFIG_TWL4030_WATCHDOG can both be enabled without a minor-number conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100