Skip to content
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.

allwinner: CPU drivers should expose pins even if can't expose due to lack of privilege #125

Closed
maruel opened this issue Apr 13, 2017 · 1 comment

Comments

@maruel
Copy link
Contributor

maruel commented Apr 13, 2017

For example, running i2c-list on a C.H.I.P. as the chip user doesn't print the GPIO lines because the allwinner drive fails to load. It fails to load because it tries to open /dev/mem.

From the user perspective it shouldn't matter, the user can still likely use sysfs gpio support (pending right udev rules) and the pins should still be aliased properly. This means registering the pin aliases when the driver fails to load, which is kind of weird in some ways as a driver failing to load should not have side effects. An option is to split the allwinner driver in two.

maruel added a commit that referenced this issue Apr 13, 2017
This makes it much more generic and extensible. This will enable addressing
issue #125.
maruel added a commit that referenced this issue Apr 13, 2017
This makes it much more generic and extensible. This will enable addressing
issue #125.

Refuse registering an high and low priority pins with different numbers but same
name and reverse.
@maruel maruel changed the title CPU drivers should expose pins even if can't expose due to lack of privilege allwinner: CPU drivers should expose pins even if can't expose due to lack of privilege Nov 9, 2018
@maruel
Copy link
Contributor Author

maruel commented Sep 20, 2023

Ported to periph/host#46.

@maruel maruel closed this as completed Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant