#
303975 |
|
11-Aug-2016 |
gjb |
Copy stable/11@r303970 to releng/11.0 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, and rename it to RC1.
Update __FreeBSD_version.
Use the quarterly branch for the default FreeBSD.conf pkg(8) repo and the dvd1.iso packages population.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
302408 |
|
08-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
300393 |
|
22-May-2016 |
loos |
Sort and remove a couple of unnecessary headers.
|
#
300392 |
|
22-May-2016 |
loos |
Get rid of two consumers of gpiobus acquire/release.
The GPIO hardware should not be owned by a single device, this defeats any chance of use of the GPIO controller as an interrupt source.
ow(4) is now the only consumer of this 'feature' before we can remove it for good.
Discussed with: ian, bsdimp
|
#
300391 |
|
22-May-2016 |
loos |
Use a better prefix for defines, return BUS_PROBE_DEFAULT for probe routine.
Refuse to attach if the number of given pins is not enough for our needs.
|
#
299396 |
|
11-May-2016 |
gonzo |
Use DEVMETHOD_END instead of its value to indicate end of methods table
|
#
297794 |
|
10-Apr-2016 |
gonzo |
Fix IIC "how" argument dereferencing on big-endian platforms
"how" argument is passed as value of int* pointer to callback function but dereferenced as char* so only one byte taken into into account. On little-endian systems it happens to work because first byte is LSB that contains actual value, on big-endian it's MSB and in this case it's always equal zero
PR: 207786 Submitted by: chadf@triularity.org
|
#
273917 |
|
31-Oct-2014 |
loos |
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.
|
#
266922 |
|
31-May-2014 |
loos |
Add a bounds verification to the SCL and SDA pin values.
At attach, print the SCL and SDA pin numbers.
Remove a stray blank line.
Remove the GPIOBUS locking from gpioiic_reset(), it is already called with this lock held. This fixes a crash when you try to scan the iicbus with i2c(8).
|
#
261843 |
|
13-Feb-2014 |
loos |
Add OFW support to the in tree gpio compatible devices: gpioiic(4) and gpioled(4).
Tested on RPi and BBB (using the hardware I2C controller and gpioiic(4) for the I2C tests). It was also verified for regressions on RSPRO (MIPS/ar71xx) used as reference for a non OFW-based system.
Update the gpioled(4) and gpioiic(4) man pages with some details and examples about the FDT/OFW support.
Some compatibility details pointed out by imp@ will follow in subsequent commits.
Approved by: adrian (mentor, implicit)
|
#
259035 |
|
06-Dec-2013 |
loos |
Remove unnecessary includes and an unused softc variable. While here apply two minor style(9) fixes.
Approved by: adrian (mentor)
|
#
228729 |
|
20-Dec-2011 |
adrian |
Fix broken locking that I introduced in the previous commit.
|
#
228725 |
|
20-Dec-2011 |
adrian |
Remove these locks - they aren't strictly needed and cause measurable performance issues.
* Access to the GPIO bus is already locked by requesting and releasing the bus - thus the lock isn't really needed for each GPIO pin change. * Don't lock and unlock the GPIO bus for -each- i2c access - the i2c bus code is already doing this by calling the upper layer callback to request/release the bus. This thus locks the bus for the entirety of the transaction.
TODO:
* Further verify that everything is correctly requesting/ releasing the GPIO bus. * Look at how to lock the GPIO pin configuration stuff, potentially by locking/unlocking the bus at the gpiobus layer.
|
#
228258 |
|
04-Dec-2011 |
adrian |
Modify the GPIO i2c bus code to allow for arbitrary data/clock pins, rather than defaulting to 0 and 1.
This way the pin order can be reversed. It is reversed with the TP-Link TL-WR1043nd.
Submitted by: Stefan Bethke <stb@lassitu.de>
|
#
213277 |
|
29-Sep-2010 |
gonzo |
Fix legal staff in GPIO sources: - license clause now contains "AUTHOR AND CONTRIBUTORS" instead of just "AUTHOR" - Add license/copyright to gpioc.c
Spotted by: Edward Tomasz Napierala, Andrew Turner
|
#
213237 |
|
28-Sep-2010 |
gonzo |
Initial GPIO bus support. Includes: - GPIO bus controller interface - GPIO bus interface - Implementation of GPIO led(4) compatible device - Implementation of iic(4) bus over GPIO (author: Luiz Otavio O Souza)
Tested by: Luiz Otavio O Souza, Alexandr Rybalko
|