RFC omap: gpio: User generic (instead of custom) API
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Luca Ceresoli |
|---|---|
| Series | T-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [U-Boot] [RFC 0/3] omap: gpio: User generic (instead of custom) API
Hi Sanjeev,
Quoted 9 lines · Sanjeev Premi
The OMAP boards use a custom api for GPIO operations. While it works, it doesn't help when when we don't know existence of the customization.
I earlier encountered the problem when looking for GPIO related changes when submitting prev set of patches. Since the search for
gpio_request()in omap sources returned empty, I had assumed that it isn't supported.
Quoted 7 lines
This patchset attempts to adapt the current implementation to use generic API.
Since, the changes impact all OMAP boards, and I wouldn't be able to test on all, I decided to submit changes as RFC. Unless any major issue is found, I will be able to submit as formal patch by end of this week.
Tested and working on the dig297 board, on top of the master branch in the u-boot-ti repository.
I also tried to merge your work on the u-boot-arm repo, but it conflicts with the GPIO work recently committed there. You might want to rebase and resubmit when the -ti repo will be in line with the -arm one.
Anyway, for the current version:
Luca