Revision tags: release/10.1.0 |
|
#
5c9ef378 |
| 04-Nov-2014 |
Alexander V. Chernikov <melifaro@FreeBSD.org> |
Sync to HEAD@r274095.
|
#
9d35acac |
| 31-Oct-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 wha
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.
show more ...
|
#
246e7a2b |
| 02-Sep-2014 |
Neel Natu <neel@FreeBSD.org> |
IFC @r269962
Submitted by: Anish Gupta (akgupt3@gmail.com)
|
#
ee7b0571 |
| 19-Aug-2014 |
Simon J. Gerraty <sjg@FreeBSD.org> |
Merge head from 7/28
|
Revision tags: release/9.3.0 |
|
#
6cec9cad |
| 03-Jun-2014 |
Peter Grehan <grehan@FreeBSD.org> |
MFC @ r266724
An SVM update will follow this.
|
#
e72f32cd |
| 31-May-2014 |
Luiz Otavio O Souza <loos@FreeBSD.org> |
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 cal
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).
show more ...
|
#
3b8f0845 |
| 28-Apr-2014 |
Simon J. Gerraty <sjg@FreeBSD.org> |
Merge head
|
#
84e51a1b |
| 23-Apr-2014 |
Alan Somers <asomers@FreeBSD.org> |
IFC @264767
|
#
c98bb15d |
| 21-Feb-2014 |
Glen Barber <gjb@FreeBSD.org> |
MFH: tracking commit
Sponsored by: The FreeBSD Foundation
|
#
5748b897 |
| 19-Feb-2014 |
Martin Matuska <mm@FreeBSD.org> |
Merge head up to r262222 (last merge was incomplete).
|
#
9a2a079a |
| 13-Feb-2014 |
Luiz Otavio O Souza <loos@FreeBSD.org> |
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 f
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)
show more ...
|
#
485ac45a |
| 04-Feb-2014 |
Peter Grehan <grehan@FreeBSD.org> |
MFC @ r259205 in preparation for some SVM updates. (for real this time)
|
Revision tags: release/10.0.0 |
|
#
41ec463c |
| 06-Dec-2013 |
Luiz Otavio O Souza <loos@FreeBSD.org> |
Remove unnecessary includes and an unused softc variable. While here apply two minor style(9) fixes.
Approved by: adrian (mentor)
|
Revision tags: release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0 |
|
#
8fa0b743 |
| 23-Jan-2012 |
Xin LI <delphij@FreeBSD.org> |
IFC @230489 (pending review).
|
#
80dbff4e |
| 04-Jan-2012 |
Sean Bruno <sbruno@FreeBSD.org> |
IFC to head to catch up the bhyve branch
Approved by: grehan@
|
Revision tags: release/9.0.0 |
|
#
74ab90b7 |
| 20-Dec-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
Fix broken locking that I introduced in the previous commit.
|
#
ddd76991 |
| 20-Dec-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
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 reall
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.
show more ...
|
#
93522550 |
| 04-Dec-2011 |
Adrian Chadd <adrian@FreeBSD.org> |
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.
Submitt
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>
show more ...
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0 |
|
#
6f3544cd |
| 26-Oct-2010 |
Marcel Moolenaar <marcel@FreeBSD.org> |
Merge svn+ssh://svn.freebsd.org/base/head@214309
|
#
5f958b85 |
| 29-Sep-2010 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
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 Napiera
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
show more ...
|
#
6b34b16e |
| 28-Sep-2010 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
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: Lu
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
show more ...
|