Reset controller API to reset IP modules on i.MX5 and i.MX6
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest0 of 8 patches 0 repliesNew
- v1 RFC0 of 5 patches 0 repliesSuperseded
Patches in v5 No applies recorded yet
None of the 8 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Marek Vasut |
|---|---|
| Series | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v5 0/8] Reset controller API to reset IP modules on i.MX5 and i.MX6
Dear Pavel Machek,
Quoted 17 lines
Hi!
Quoted 15 lines
The system reset controller (SRC) on i.MX51, i.MX53, and i.MX6q controls reset lines to the GPU, VPU, IPU, and OpenVG IP modules.
The following patches add a simple API for devices to request being reset by separate reset controller hardware and implements the reset signal device tree binding proposed by Stephen Warren. Contrary to Tegra hardware, the i.MX SRC contains self-deasserting reset registers, so I've included both ops to manually assert/deassert a reset line, as well as a "reset" operation that is supposed to assert the reset line and wait for it to deassert.
The i.MX SRC is enhanced to provide a reset controller and the IPU driver is made to request being reset by calling the
device_reset(&pdev->dev)convenience wrapper during probing.
Quoted 8 lines
Quoted 5 lines
Changes since v4:
- removed flags parameter from .of_xlate /of_reset_simple_xlate
- warn also ifreset_spec->args_count>rcdev->of_reset_n_cells
- unlock list mutex only aftertry_module_get
- tightendevm_reset_control_matcha bitSeries looks mostly ok to me. (Should the last patch be actually first, so that reset functionality is kept between 5/8 and 8/8?)
Not first, but rather third.
You can add my
Best regards,
Marek Vasut