- 15 May, 2014 30 commits
-
-
Jes Sorensen authored
Signed-off-by:
Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Use the knowledge we already have from parsing the TODS/FROMDS bits in hdr->frame_control to obtain the bssid. Note that get_hdr_bssid() would never return NULL as handling 4 combinations of a 2 bit word leaves little space for falling through to the 'default' value. Signed-off-by:
-
Jes Sorensen authored
This is only used in one place - do the work there properly. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Having struct qos_priv containing a single integer, and carrying a dedicated header file for it, is just plain silly. Move the integer into struct mlme_priv, which is the only place qos_priv was used anyway, and get rid of the header file. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
This avoids an ugly cast in mlme_evt_hdl23a() Signed-off-by:
-
Jes Sorensen authored
Every other place uses C2HEvent_Header() for events. Given the struct is endian dependant, use it here too to retrieve data from the parm buffer. Note the length field is not set/read in le order - question is whether it's simply an opaque field? Signed-off-by:
-
Larry Finger authored
This makes sparse happy Signed-off-by:
Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Split the old work handler into a workqueue for processing usb_read_interrupt_complete() events that require more than ust clearing the event, and leave the old handler to just handle event clearing. This means we can get rid of the hacks with magic pointers to determine what actions needs to be taken in the work handler, and as an extra bonus obsoletes the bizarre cbuf code. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
This function no longer does anything, so get rid of it. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
commit 0348dc74 ensured that the parm buffer passed to the cmd handlers is not being over-written. Hence there is no need to make a copy of the parm buffer just to pass it into the cmd handler. Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
Jes Sorensen authored
Signed-off-by:
-
- 06 May, 2014 1 commit
-
-
- 05 May, 2014 9 commits
-
-
Greg Kroah-Hartman authored
Merge tag 'iio-for-3.16b' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Jonathan writes: Second set of IIO new drivers, cleanups and functionality for the 3.16 cycle. This set contains a change to the ABI for the hid-sensors drivers to bring them in line with the long published documentation. Unfortunately, rather than reporting true scale and offset values via sysfs they were reporting some magic numbers that could only be converted to anything useful using the HID sensors specification. I missed this entirely through the introduction of a number of drivers, only picking up on it recently. Srinivas has had user feedback about this as well. The patch set is too large to go as a fix at this stage in the cycle and is not a regression fix as this was never right and so will have to wait for the next merge window. Srinivas assures me that there are relatively few pieces of hardware out there and he has had a number of people contact him to point out that the drivers did not obey the ABI. Hence hopefully the fallout of this, if any will be minor. If we don't fix it now, it will only get worse going forward. There is no sensible way of maintaining the incorrect ABI as it is simply returning the wrong values through the standard interfaces. Non IIO elements * Introduce devm_kmemdup. Does what it says on the tin. New drivers: * hid-sensors rotation devices (output as quaternion) * Freescale MPL115A2 presure and temperature sensor. * Melexis mlx90614 contactless infrared sensor. * Freescale MMA8452Q 3-axis accelerometer. New functionality: * Addition of multiple element callback to allow for sysfs interfaces to access elements such as quaternions which have no useful meaning if all 4 elements are not presented together. Other future usecases for this include rotation matrices. * Support for multiple element buffer entries for exactly the same uses as the sysfs related elements described above. * Quaternion support via the quaternion IIO modifier. * TEMP_AMBIENT and TEMP_OBJECT modifiers to distinguish cases with thermopile devices. * hid-sensors gain sysfs access to the sensor readings. Previously these drivers used the buffered interface only. This change involves some additional hid-sensors core support to read poll values back from the devices to allow the drivers to know roughly how long to wait for a result when polling the sensor. There is also an associated hid-sensors abi to allow the devices to be turned off between reads and powered up on demand. Cleanups and fixes * Hid sensors fix as described above. Result is to make the _scale and _offset attributes applicable in the same way as for all other IIO drivers. * Some additional documentation - mostly covering stuff that graduated from staging without managing to take it's ABI docs with it. * A series of little tidy ups to the exynos_adc driver that make the code nicer to read and improve handling of some corner cases. * A tidy up to mag3110 (logical fix rather than a real one ;). Also enable user offset calibration for this device. * Drop some left over IS_ERR() checks from ad799x that snuck through during the cleanup in the last IIO patch set. * Fix a naming issue from clashing patches in ak8975 - note the clash only occured in the last IIO patch set, hence the fix needs to go through this tree. * A format string missmatch fix in ad7280.c. Unlikely to have ever had an impact so not worth rushing through.
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added support for raw reading of channel. If the sensor is powered off, it will turn on for reading value. Signed-off-by:
-
Srinivas Pandruvada authored
Added an API to allow client drivers to turn ON and OFF sensors for quick read. Added data_read as counting varaible instead of boolean, so that sensor is powered off only when last user released it. Signed-off-by:
-
