#
296373 |
|
04-Mar-2016 |
marius |
- Copy stable/10@296371 to releng/10.3 in preparation for 10.3-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.3. - Update default pkg(8) configuration to use the quarterly branch.
Approved by: re (implicit) |
#
278072 |
|
02-Feb-2015 |
loos |
MFC r277206:
Catch a few cases where we need to release memory resources on errors.
Place parentheses around variables in macros.
|
#
276872 |
|
09-Jan-2015 |
loos |
MFC r276314:
Convert the BSC (i2c) driver to use the new iicbus_get_frequency().
Tested on: Raspberry pi
|
#
276869 |
|
09-Jan-2015 |
loos |
MFC r273610:
Add an iicbus_reset() method to bcm2835_bsc. While it is generally not used for kernel devices it is used by i2c(8).
This fix the 'error: Device not configured' when i2c(8) tries to reset the controller:
# i2c -r Resetting I2C controller on /dev/iic0: error: Device not configured
For now use conservative settings for default i2c speeds.
|
#
276868 |
|
09-Jan-2015 |
loos |
MFC r273329, r273337 and r274415
Add another wakeup() after actually set the bus as free.
This fix a race where the threads waiting for the bus would wake up early and still see bus as busy.
While here, give a better description to wmesg for the two use cases we have (bus and io waiting).
Fix the mtx_sleep() error checking, catch all errors and not only EWOULDBLOCK.
Do not print any message at errors. The errors are properly sent to upper layers which should be able to deal with it, including printing the errors when they need to.
The error message was quite annoying while scanning the i2c bus.
|
#
270243 |
|
20-Aug-2014 |
loos |
MFC r267021:
FreeBSD, historically, has always used 8-bit addresses for i2c devices (7-bit device address << 1), always leaving the room for the read/write bit.
This commit convert ti_i2c and revert r259127 on bcm2835_bsc to make them compatible with 8-bit addresses. Previous to this commit an i2c device would have different addresses depending on the controller it was attached to (by example, when compared to any iicbb(4) based i2c controller), which was a pretty annoying behavior.
Also, update the PMIC i2c address on beaglebone* DTS files to match the new address scheme.
Now the userland utilities need to do the correct slave address shifting (but it is going to work with any i2c controller on the system).
Discussed with: ian
MFC r267834:
Clarify the expected usage of I2C 7-bit slave addresses on ioctl(2) interface.
While here add the cross reference to iic(4) on iicbus(4).
CR: D210 Suggested by: jmg
|
#
266152 |
|
15-May-2014 |
ian |
MFC r261410
Follow r261352 by updating all drivers which are children of simplebus to check the status property in their probe routines.
|
#
261078 |
|
23-Jan-2014 |
loos |
MFC r256959:
Add the Raspberry Pi BSC (I2C compliant) controller driver.
Reviewed by: rpaulo
MFC r256961:
Enable the build of OFW I2C bus for FDT systems.
MFC r258045:
As all the IIC controllers on system uses the same 'iichb' prefix we cannot rely only on checking the device unit to indentify the BSC unit we are attaching to. Make use of the device base address to identify our BSC unit.
MFC r259127:
Bring the RPi I2C driver in line with ti_i2c. Make it treat any slave address as a 7-bit address.
Approved by: adrian (mentor)
|
#
256959 |
|
23-Oct-2013 |
loos |
Add the Raspberry Pi BSC (I2C compliant) controller driver.
Reviewed by: rpaulo Approved by: adrian (mentor)
|