Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make GPIOPortMCP23017 more general and support native GPIOs #6

Open
marianopeck opened this issue Jun 19, 2019 · 0 comments
Open

Make GPIOPortMCP23017 more general and support native GPIOs #6

marianopeck opened this issue Jun 19, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@marianopeck
Copy link
Collaborator

Right now, GPIOPortMCP23017 works with a device. The API of that device is basically a subset of I2CDeviceGPIOMCP23017. I believe that subset of functionality / API should eventually be moved up in the hierarchy (to I2cDevice or GpioBusDevice). That way, GPIOPortMCP23017 could be renamed to GPIOPort and depending on which device you pass, it would use either the GPIOs of MCP23017 or the native ones.

At this point, it would also be interesting to think if those GpioBusDevice and similar GPIO* classes should be renamed to Pigpio*.

@marianopeck marianopeck added the enhancement New feature or request label Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant