Commit 3c60d4c
committed
gpiodriver: allow GpioDigitalOutputDriver match against MatchedSysfsGPIO
The documentation states that the GpioDigitalOutputDriver should bind to
the following three 'gpio' options:
- SysfsGPIO
- MatchedSysfsGPIO
- NetworkSysfsGPIO
However, the bindings list is:
bindings = {
"gpio": {"SysfsGPIO", "NetworkSysfsGPIO"},
}
and as a result, if I try to bind these two in an environment, I see
errors like:
labgrid.exceptions.NoSupplierFoundError: binding copilot-output-driver failed: no supplier matching {'NetworkSysfsGPIO', 'SysfsGPIO'} found in Target(name='beagleplay', env=Environment(config_file='bp-conf2.yaml')) (errors: [NoResourceFoundError(msg="no NetworkSysfsGPIO resource found in Target(name='beagleplay', env=Environment(config_file='bp-conf2.yaml'))", filter=None, found=None), NoResourceFoundError(msg="no SysfsGPIO resource found in Target(name='beagleplay', env=Environment(config_file='bp-conf2.yaml'))", filter=None, found=None)])
Adjust the list to include MatchedSysfsGPIO so that this works (and so
that the docs are correct).
Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>1 parent 080502d commit 3c60d4c
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
| 17 | + | |
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| |||
0 commit comments