Bug 206228
| Summary: | [patch] Add fdt_reset based on the fdt_clock implementation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Stanislav Galabov <sgalabov> | ||||
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | sgalabov, sgalabov | ||||
| Priority: | --- | Keywords: | patch | ||||
| Version: | CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
The required functionality will be implemented using the extres framework. |
Created attachment 165547 [details] Add fdt_reset based on fdt_clock The attached patch adds fdt_reset functionality in much the same way as the sys/dev/fdt/fdt_clock* functionality by ian@. Basically, a driver that provides reset controller functionality (provider) to other drivers (consumers), can (un)register itself by calling fdt_reset_(un)register_provider. Once registered, consumers can simply call fdt_reset_(de)assert_all(consumer), where consumer is the consumer's device_t in order to get their associated resets (de)asserted.