Searched hist:"9 d35acacd31ea9b4055ba61d4578af73571bc209" (Results 1 – 5 of 5) sorted by relevance
| /freebsd/sys/dev/gpio/ |
| H A D | gpiobus_if.m | diff 9d35acacd31ea9b4055ba61d4578af73571bc209 Fri Oct 31 20:15:14 CET 2014 Luiz Otavio O Souza <loos@FreeBSD.org> Fix the gpiobus locking by using a more sane model where it isn't necessary
hold the gpiobus lock between the gpio calls.
gpiobus_acquire_lock() now accepts a third parameter which tells gpiobus
what to do when the bus is already busy.
When GPIOBUS_WAIT wait is used, the calling thread will be put to sleep
until the bus became free.
With GPIOBUS_DONTWAIT the calling thread will receive EWOULDBLOCK right
away and then it can act upon.
This fixes the gpioiic(4) locking issues that arises when doing multiple
concurrent access on the bus.
|
| H A D | gpioled.c | diff 9d35acacd31ea9b4055ba61d4578af73571bc209 Fri Oct 31 20:15:14 CET 2014 Luiz Otavio O Souza <loos@FreeBSD.org> Fix the gpiobus locking by using a more sane model where it isn't necessary
hold the gpiobus lock between the gpio calls.
gpiobus_acquire_lock() now accepts a third parameter which tells gpiobus
what to do when the bus is already busy.
When GPIOBUS_WAIT wait is used, the calling thread will be put to sleep
until the bus became free.
With GPIOBUS_DONTWAIT the calling thread will receive EWOULDBLOCK right
away and then it can act upon.
This fixes the gpioiic(4) locking issues that arises when doing multiple
concurrent access on the bus.
|
| H A D | gpioiic.c | diff 9d35acacd31ea9b4055ba61d4578af73571bc209 Fri Oct 31 20:15:14 CET 2014 Luiz Otavio O Souza <loos@FreeBSD.org> Fix the gpiobus locking by using a more sane model where it isn't necessary
hold the gpiobus lock between the gpio calls.
gpiobus_acquire_lock() now accepts a third parameter which tells gpiobus
what to do when the bus is already busy.
When GPIOBUS_WAIT wait is used, the calling thread will be put to sleep
until the bus became free.
With GPIOBUS_DONTWAIT the calling thread will receive EWOULDBLOCK right
away and then it can act upon.
This fixes the gpioiic(4) locking issues that arises when doing multiple
concurrent access on the bus.
|
| H A D | gpiobusvar.h | diff 9d35acacd31ea9b4055ba61d4578af73571bc209 Fri Oct 31 20:15:14 CET 2014 Luiz Otavio O Souza <loos@FreeBSD.org> Fix the gpiobus locking by using a more sane model where it isn't necessary
hold the gpiobus lock between the gpio calls.
gpiobus_acquire_lock() now accepts a third parameter which tells gpiobus
what to do when the bus is already busy.
When GPIOBUS_WAIT wait is used, the calling thread will be put to sleep
until the bus became free.
With GPIOBUS_DONTWAIT the calling thread will receive EWOULDBLOCK right
away and then it can act upon.
This fixes the gpioiic(4) locking issues that arises when doing multiple
concurrent access on the bus.
|
| H A D | gpiobus.c | diff 9d35acacd31ea9b4055ba61d4578af73571bc209 Fri Oct 31 20:15:14 CET 2014 Luiz Otavio O Souza <loos@FreeBSD.org> Fix the gpiobus locking by using a more sane model where it isn't necessary
hold the gpiobus lock between the gpio calls.
gpiobus_acquire_lock() now accepts a third parameter which tells gpiobus
what to do when the bus is already busy.
When GPIOBUS_WAIT wait is used, the calling thread will be put to sleep
until the bus became free.
With GPIOBUS_DONTWAIT the calling thread will receive EWOULDBLOCK right
away and then it can act upon.
This fixes the gpioiic(4) locking issues that arises when doing multiple
concurrent access on the bus.
|