-
Notifications
You must be signed in to change notification settings - Fork 0
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
Example #1
Comments
First, this is a beta (maybe alpha) version so far, and thus master is tracking dev and changes (aka breaks) a lot. Second, the dependencies are not published npms. And specifically Third, example/client is the current working app. It follows similar style used in other repo here (aka boschieu etc). The current examples focus less on creating Gpio style access (though it is stubbed in and headed in that direction as per notes etc) and more on managing the chip settings directly as a low level api. Node, the Gpio will follow the Last, the usefulness of many of the existing and target features add a complexity not found in other (all?) libraries for the mcp23 chips. And as such usefulness of such added complexity weight against any performance gains may be negligible under V8 runtimes (as examples. supporting both 8bit and 16bit poll mode, as well as the interlaced and dual-blocks addressing mode may provide little production usages ... time will tell :) ) I would be interested in any use cases / features etc you have in mind. |
Gotcha. So is this polling-only, or is it interrupt-driven? Looking for something that doesn't eat CPU unless buttons are pressed. |
Full Interrupt driven event can be achieved. But support for single and no interrupts is supported. This chip can generate interrupts on its intA and itB pins. If those are wired to a raspberry pi, a library like The intent of this library is to then provide the callbacks The chip provides two interrupts. It is however the intent to support both independent A and B interrupts as well as the Mirrored Interrupt mode the chip supports. Also, as software fast poll example will be added when no A or B interrupt can be added and needs to be emulated.
The "point" of all that being that this extra abstraction allows for the use of any external library to provide the interrupt pins for the mcp23 while still providing a flexible Gpio style interface. The expectation is that higher-level APIs will be developed atop of these structures (such as |
Killer explanation, thank you! |
Very interested to use this. Could you throw up a full example?
The text was updated successfully, but these errors were encountered: