You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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*.
The text was updated successfully, but these errors were encountered:
Right now,
GPIOPortMCP23017
works with adevice
. The API of thatdevice
is basically a subset ofI2CDeviceGPIOMCP23017
. I believe that subset of functionality / API should eventually be moved up in the hierarchy (toI2cDevice
orGpioBusDevice
). That way,GPIOPortMCP23017
could be renamed toGPIOPort
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 similarGPIO*
classes should be renamed toPigpio*
.The text was updated successfully, but these errors were encountered: