The driver does not implement a display API, it has a custom API. Having it under display is confusing, since display API consumers may expect they can use it. These sort of custom drivers fit better under drivers/misc. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| boards | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| sample.yaml | ||