3.10.89-stable review
Greg Kroah-Hartman
maintainerPATCH 8/20 USB: ftdi_sio: Added custom PID for CustomWare products
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matthijs Kooijman <[email protected]>
commit 1fb8dc36384ae1140ee6ccc470de74397606a9d5 upstream.
CustomWare uses the FTDI VID with custom PIDs for their ShipModul MiniPlex products.
--- drivers/usb/serial/ftdi_sio.c | 4 ++++ drivers/usb/serial/ftdi_sio_ids.h | 8 ++++++++ 2 files changed, 12 insertions(+)
drivers/usb/serial/ftdi_sio.c +4 -0
@@ -621,6 +621,10 @@ static struct usb_device_id id_table_com { USB_DEVICE(FTDI_VID, FTDI_NT_ORIONLXM_PID), .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk }, { USB_DEVICE(FTDI_VID, FTDI_SYNAPSE_SS200_PID) }, + { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX_PID) }, + { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2_PID) }, + { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX2WI_PID) }, + { USB_DEVICE(FTDI_VID, FTDI_CUSTOMWARE_MINIPLEX3_PID) },/* * ELV devices: */
drivers/usb/serial/ftdi_sio_ids.h +8 -0
@@ -568,6 +568,14 @@*/ #define FTDI_SYNAPSE_SS200_PID 0x9090/* SS200 - SNAP Stick 200 */ +/* +* CustomWare / ShipModul NMEA multiplexers product ids (FTDI_VID) +*/ +#define FTDI_CUSTOMWARE_MINIPLEX_PID 0xfd48/* MiniPlex first generation NMEA Multiplexer */ +#define FTDI_CUSTOMWARE_MINIPLEX2_PID 0xfd49/* MiniPlex-USB and MiniPlex-2 series */ +#define FTDI_CUSTOMWARE_MINIPLEX2WI_PID 0xfd4a/* MiniPlex-2Wi */ +#define FTDI_CUSTOMWARE_MINIPLEX3_PID 0xfd4b/* MiniPlex-3 series */ +/********************************/ /** third-party VID/PID combos **/
Greg Kroah-Hartman
maintainerPATCH 9/20 usb: dwc3: ep0: Fix mem corruption on OUT transfers of more than 512 bytes
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kishon Vijay Abraham I <[email protected]>
commit b2fb5b1a0f50d3ebc12342c8d8dead245e9c9d4e upstream.
DWC3 uses bounce buffer to handle non max packet aligned OUT transfers and the size of bounce buffer is 512 bytes. However if the host initiates OUT transfers of size more than 512 bytes (and non max packet aligned), the driver throws a WARN dump but still programs the TRB to receive more than 512 bytes. This will cause bounce buffer to overflow and corrupt the adjacent memory locations which can be fatal.
Fix it by programming the TRB to receive a maximum of DWC3_EP0_BOUNCE_SIZE
(512) bytes.
--- drivers/usb/dwc3/ep0.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
drivers/usb/dwc3/ep0.c +10 -2
@@ -804,6 +804,11 @@ static void dwc3_ep0_complete_data(strucunsigned maxp = ep0->endpoint.maxpacket; transfer_size += (maxp - (transfer_size % maxp)); + +/* Maximum of DWC3_EP0_BOUNCE_SIZE can only be received */ +if (transfer_size >DWC3_EP0_BOUNCE_SIZE ) + transfer_size =DWC3_EP0_BOUNCE_SIZE ; + transferred =min_t (u32, ur->length, transfer_size - length);memcpy (ur->buf, dwc->ep0_bounce, transferred);
@@ -916,11 +921,14 @@ static void __dwc3_ep0_do_control_data(sreturn ; } -WARN_ON (req->request.length >DWC3_EP0_BOUNCE_SIZE ); - maxpacket = dep->endpoint.maxpacket; transfer_size =roundup (req->request.length, maxpacket); +if (transfer_size >DWC3_EP0_BOUNCE_SIZE ) { +dev_WARN (dwc->dev,"bounce buf can't handle req len\n" ); + transfer_size =DWC3_EP0_BOUNCE_SIZE ; + } + dwc->ep0_bounced = true;/*
Greg Kroah-Hartman
maintainerPATCH 12/20 crypto: ghash-clmulni: specify context size for ghash async algorithm
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrey Ryabinin <[email protected]>
commit 71c6da846be478a61556717ef1ee1cea91f5d6a8 upstream.
Currently context size (cra_ctxsize) doesn't specified for ghash_async_alg. Which means it's zero. Thus crypto_create_tfm() doesn't allocate needed space for ghash_async_ctx, so any read/write to ctx (e.g. in ghash_async_init_tfm()) is not valid.
--- arch/x86/crypto/ghash-clmulni-intel_glue.c | 1 + 1 file changed, 1 insertion(+)
arch/x86/crypto/ghash-clmulni-intel_glue.c +1 -0
@@ -291,6 +291,7 @@ static struct ahash_alg ghash_async_alg .cra_name = "ghash", .cra_driver_name = "ghash-clmulni", .cra_priority = 400, + .cra_ctxsize = sizeof(struct ghash_async_ctx), .cra_flags = CRYPTO_ALG_TYPE_AHASH | CRYPTO_ALG_ASYNC, .cra_blocksize = GHASH_BLOCK_SIZE, .cra_type = &crypto_ahash_type,
Greg Kroah-Hartman
maintainercover 3.10.89-stable review
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.89-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.10.89-rc1
Mikulas Patocka <[email protected]>
hpfs: update ctime and mtime on directory modification
Grant Likely <[email protected]>
drivercore: Fix unregistration path of platform devices
David Daney <[email protected]>
of/address: Don't loop forever in of_find_matching_node_by_address().
Sudip Mukherjee <[email protected]>
auxdisplay: ks0108: fix refcount
Masahiro Yamada <[email protected]>
devres: fix devres_get()
Max Filippov <[email protected]>
xtensa: fix kernel register spilling
Max Filippov <[email protected]>
xtensa: fix threadptr reload on return to userspace
Don Zickus <[email protected]>
HID: usbhid: Fix the check for HID_RESET_PENDING in hid_io_error
Andrey Ryabinin <[email protected]>
crypto: ghash-clmulni: specify context size for ghash async algorithm
Maciej S. Szmigiero <[email protected]>
serial: 8250: don't bind to SMSC IrCC IR port
Peter Chen <[email protected]>
usb: host: ehci-sys: delete useless bus_to_hcd conversion
Kishon Vijay Abraham I <[email protected]>
usb: dwc3: ep0: Fix mem corruption on OUT transfers of more than 512 bytes
Matthijs Kooijman <[email protected]>
USB: ftdi_sio: Added custom PID for CustomWare products
Philipp Hachtmann <[email protected]>
USB: symbolserial: Use usb_get_serial_port_data
Bjorn Helgaas <[email protected]>
PCI: Fix TI816X class code quirk
Dan Carpenter <[email protected]>
clk: versatile: off by one in clk_sp810_timerclken_of_get()
Lars-Peter Clausen <[email protected]>
iio: adis16480: Fix scale factors
Lars-Peter Clausen <[email protected]>
iio: Add inverse unit conversion macros
Markus Pargmann <[email protected]>
iio: bmg160: IIO_BUFFER and IIO_TRIGGERED_BUFFER are required
Stephen Chandler Paul <[email protected]>
DRM - radeon: Don't link train DisplayPort on HPD until we get the dpcd
-------------
Diffstat:
Makefile | 4 +-- arch/x86/crypto/ghash-clmulni-intel_glue.c | 1 + arch/xtensa/include/asm/traps.h | 29 ++++++++++++++-------- arch/xtensa/kernel/entry.S | 7 +++--- drivers/auxdisplay/ks0108.c | 1 + drivers/base/devres.c | 4 +-- drivers/base/platform.c | 8 ++---- drivers/clk/versatile/clk-sp810.c | 4 +-- drivers/gpu/drm/radeon/radeon_connectors.c | 5 ++++ drivers/hid/usbhid/hid-core.c | 2 +- drivers/iio/gyro/Kconfig | 3 ++- drivers/iio/imu/adis16480.c | 39 +++++++++++++++++++++++++----- drivers/of/address.c | 6 ++--- drivers/pci/quirks.c | 9 ++++--- drivers/tty/serial/8250/8250_pnp.c | 5 ++++ drivers/usb/dwc3/ep0.c | 12 +++++++-- drivers/usb/host/ehci-sysfs.c | 8 +++--- drivers/usb/serial/ftdi_sio.c | 4 +++ drivers/usb/serial/ftdi_sio_ids.h | 8 ++++++ drivers/usb/serial/symbolserial.c | 6 ++--- fs/hpfs/namei.c | 25 ++++++++++++++++++- include/linux/iio/iio.h | 17 +++++++++++++ 22 files changed, 158 insertions(+), 49 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/20 DRM - radeon: Dont link train DisplayPort on HPD until we get the dpcd
3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stephen Chandler Paul <[email protected]>
commit 924f92bf12bfbef3662619e3ed24a1cea7c1cbcd upstream.
Most of the time this isn't an issue since hotplugging an adaptor will trigger a crtc mode change which in turn, causes the driver to probe every DisplayPort for a dpcd. However, in cases where hotplugging doesn't cause a mode change (specifically when one unplugs a monitor from a DisplayPort connector, then plugs that same monitor back in seconds later on the same port without any other monitors connected), we never probe for the dpcd before starting the initial link training. What happens from there looks like this:
- GPU has only one monitor connected. It's connected via DisplayPort, and does not go through an adaptor of any sort.
- User unplugs DisplayPort connector from GPU.
- Change in HPD is detected by the driver, we probe every DisplayPort for a possible connection.
- Probe the port the user originally had the monitor connected on for it's dpcd. This fails, and we clear the first (and only the first) byte of the dpcd to indicate we no longer have a dpcd for this port.
- User plugs the previously disconnected monitor back into the same DisplayPort.
- radeon_connector_hotplug() is called before everyone else, and tries to handle the link training. Since only the first byte of the dpcd is zeroed, the driver is able to complete link training but does so against the wrong dpcd, causing it to initialize the link with the wrong settings.
- Display stays blank (usually), dpcd is probed after the initial link training, and the driver prints no obvious messages to the log.
In theory, since only one byte of the dpcd is chopped off (specifically, the byte that contains the revision information for DisplayPort), it's not entirely impossible that this bug may not show on certain monitors. For instance, the only reason this bug was visible on my ASUS PB238 monitor was due to the fact that this monitor using the enhanced framing symbol sequence, the flag for which is ignored if the radeon driver thinks that the DisplayPort version is below 1.1.
--- drivers/gpu/drm/radeon/radeon_connectors.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/gpu/drm/radeon/radeon_connectors.c +5 -0
@@ -78,6 +78,11 @@ void radeon_connector_hotplug(struct drmif (!radeon_hpd_sense (rdev, radeon_connector->hpd.hpd)) {drm_helper_connector_dpms (connector,DRM_MODE_DPMS_OFF ); }else if (radeon_dp_needs_link_train (radeon_connector)) { +/* Don't try to start link training before we +* have the dpcd */ +if (!radeon_dp_getdpcd (radeon_connector)) +return ; +/* set it to OFF so that drm_helper_connector_dpms() * won't return immediately since the current state * is ON at this point.
Greg Kroah-Hartman
maintainerPATCH 10/20 usb: host: ehci-sys: delete useless bus_to_hcd conversion
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Chen <[email protected]>
commit 0521cfd06e1ebcd575e7ae36aab068b38df23850 upstream.
The ehci platform device's drvdata is the pointer of struct usb_hcd already, so we doesn't need to call bus_to_hcd conversion again.
--- drivers/usb/host/ehci-sysfs.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/usb/host/ehci-sysfs.c +4 -4
@@ -29,7 +29,7 @@ static ssize_t show_companion(struct devint count =PAGE_SIZE ;char *ptr = buf; - ehci =hcd_to_ehci (bus_to_hcd (dev_get_drvdata (dev))); + ehci =hcd_to_ehci (dev_get_drvdata (dev)); nports =HCS_N_PORTS (ehci->hcs_params);for (index =0 ; index < nports; ++index) {
@@ -54,7 +54,7 @@ static ssize_t store_companion(struct destruct ehci_hcd *ehci;int portnum, new_owner; - ehci =hcd_to_ehci (bus_to_hcd (dev_get_drvdata (dev))); + ehci =hcd_to_ehci (dev_get_drvdata (dev)); new_owner =PORT_OWNER ;/* Owned by companion */ if (sscanf (buf,"%d" , &portnum) !=1 )return -EINVAL ;
@@ -85,7 +85,7 @@ static ssize_t show_uframe_periodic_max(struct ehci_hcd *ehci;int n; - ehci =hcd_to_ehci (bus_to_hcd (dev_get_drvdata (dev))); + ehci =hcd_to_ehci (dev_get_drvdata (dev)); n =scnprintf (buf,PAGE_SIZE ,"%d\n" , ehci->uframe_periodic_max);return n; }
@@ -102,7 +102,7 @@ static ssize_t store_uframe_periodic_maxunsigned long flags;ssize_t ret; - ehci =hcd_to_ehci (bus_to_hcd (dev_get_drvdata (dev))); + ehci =hcd_to_ehci (dev_get_drvdata (dev));if (kstrtouint (buf,0 , &uframe_periodic_max) <0 )return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 11/20 serial: 8250: dont bind to SMSC IrCC IR port
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Maciej S. Szmigiero" <[email protected]>
commit ffa34de03bcfbfa88d8352942bc238bb48e94e2d upstream.
SMSC IrCC SIR/FIR port should not be bound to by (legacy) serial driver so its own driver (smsc-ircc2) can bind to it.
--- drivers/tty/serial/8250/8250_pnp.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/tty/serial/8250/8250_pnp.c +5 -0
@@ -365,6 +365,11 @@ static const struct pnp_device_id pnp_de/* Winbond CIR port, should not be probed. We should keep track of it to prevent the legacy serial driver from probing it */ { "WEC1022", CIR_PORT }, +/* +* SMSC IrCC SIR/FIR port, should not be probed by serial driver +* as well so its own driver can bind to it. +*/ + { "SMCF010", CIR_PORT }, { "", 0 } };
Greg Kroah-Hartman
maintainerPATCH 13/20 HID: usbhid: Fix the check for HID_RESET_PENDING in hid_io_error
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Don Zickus <[email protected]>
commit 3af4e5a95184d6d3c1c6a065f163faa174a96a1d upstream.
It was reported that after 10-20 reboots, a usb keyboard plugged into a docking station would not work unless it was replugged in.
Using usbmon, it turns out the interrupt URBs were streaming with callback errors of -71 for some reason. The hid-core.c::hid_io_error was supposed to retry and then reset, but the reset wasn't really happening.
The check for HID_NO_BANDWIDTH was inverted. Fix was simple.
Tested by reporter and locally by me by unplugging a keyboard halfway until I could recreate a stream of errors but no disconnect.
--- drivers/hid/usbhid/hid-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hid/usbhid/hid-core.c +1 -1
@@ -180,7 +180,7 @@ static void hid_io_error(struct hid_deviif (time_after (jiffies, usbhid->stop_retry)) {/* Retries failed, so do a port reset unless we lack bandwidth*/ -if (test_bit (HID_NO_BANDWIDTH , &usbhid->iofl) +if (!test_bit (HID_NO_BANDWIDTH , &usbhid->iofl) && !test_and_set_bit (HID_RESET_PENDING , &usbhid->iofl)) {schedule_work (&usbhid->reset_work);
Greg Kroah-Hartman
maintainerPATCH 14/20 xtensa: fix threadptr reload on return to userspace
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Max Filippov <[email protected]>
commit 4229fb12a03e5da5882b420b0aa4a02e77447b86 upstream.
Userspace return code may skip restoring THREADPTR register if there are no registers that need to be zeroed. This leads to spurious failures in libc NPTL tests.
Always restore THREADPTR on return to userspace.
--- arch/xtensa/kernel/entry.S | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/xtensa/kernel/entry.S +2 -1
@@ -549,12 +549,13 @@ user_exception_exit: * (if we have restored WSBITS-1 frames). */ +2: #if XCHAL_HAVE_THREADPTR l32i a3, a1, PT_THREADPTR wur a3, threadptr #endif -2: j common_exception_exit + j common_exception_exit /* This is the kernel exception exit. * We avoided to do a MOVSP when we entered the exception, but we
Greg Kroah-Hartman
maintainerPATCH 15/20 xtensa: fix kernel register spilling
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Max Filippov <[email protected]>
commit 77d6273e79e3a86552fcf10cdd31a69b46ed2ce6 upstream.
call12 can't be safely used as the first call in the inline function, because the compiler does not extend the stack frame of the bounding function accordingly, which may result in corruption of local variables.
If a call needs to be done, do call8 first followed by call12.
For pure assembly code in _switch_to increase stack frame size of the bounding function.
--- arch/xtensa/include/asm/traps.h | 29 +++++++++++++++++++---------- arch/xtensa/kernel/entry.S | 4 ++-- 2 files changed, 21 insertions(+), 12 deletions(-)
arch/xtensa/include/asm/traps.h +19 -10
@@ -24,30 +24,39 @@ static inline void spill_registers(void) {#if XCHAL_NUM_AREGS >16 __asm__ __volatile__ ( -" call12 1f\n" + " call8 1f\n" " _j 2f\n" " retw\n" " .align 4\n" "1:\n" +#if XCHAL_NUM_AREGS ==32 +" _entry a1, 32\n" +" addi a8, a0, 3\n" +" _entry a1, 16\n" +" mov a12, a12\n" + " retw\n" +#else " _entry a1, 48\n" -" addi a12, a0, 3\n" -#if XCHAL_NUM_AREGS > 32 - " .rept (" __stringify(XCHAL_NUM_AREGS) " - 32) / 12\n" +" call12 1f\n" +" retw\n" +" .align 4\n" +"1:\n" + " .rept (" __stringify(XCHAL_NUM_AREGS) " - 16) / 12\n"" _entry a1, 48\n" " mov a12, a0\n" " .endr\n" -#endif - " _entry a1, 48\n" + " _entry a1, 16\n"#if XCHAL_NUM_AREGS %12 ==0 - " mov a8, a8\n" -#elif XCHAL_NUM_AREGS %12 ==4 " mov a12, a12\n" -#elif XCHAL_NUM_AREGS %12 ==8 +#elif XCHAL_NUM_AREGS %12 ==4 " mov a4, a4\n" +#elif XCHAL_NUM_AREGS %12 ==8 +" mov a8, a8\n" #endif " retw\n" +#endif "2:\n" - : : : "a12", "a13", "memory"); + : : : "a8", "a9", "memory");#else __asm__ __volatile__ ( " mov a12, a12\n"
arch/xtensa/kernel/entry.S +2 -2
@@ -1934,7 +1934,7 @@ ENDPROC(system_call) mov a12, a0 .endr #endif - _entry a1, 48 + _entry a1, 16 #if XCHAL_NUM_AREGS % 12 == 0 mov a8, a8 #elif XCHAL_NUM_AREGS % 12 == 4
@@ -1958,7 +1958,7 @@ ENDPROC(system_call) ENTRY(_switch_to) - entry a1, 16 + entry a1, 48 mov a11, a3 # and 'next' (a3)
Greg Kroah-Hartman
maintainerPATCH 2/20 iio: bmg160: IIO_BUFFER and IIO_TRIGGERED_BUFFER are required
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Pargmann <[email protected]>
commit 06d2f6ca5a38abe92f1f3a132b331eee773868c3 upstream.
This patch adds selects for IIO_BUFFER and IIO_TRIGGERED_BUFFER. Without IIO_BUFFER, the driver does not compile.
--- drivers/iio/gyro/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/iio/gyro/Kconfig +2 -1
@@ -73,7 +73,8 @@ config IIO_ST_GYRO_SPI_3AXIS config ITG3200 tristate "InvenSense ITG3200 Digital 3-Axis Gyroscope I2C driver" depends on I2C - select IIO_TRIGGERED_BUFFER if IIO_BUFFER + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER help Say yes here to add support for the InvenSense ITG3200 digital 3-axis gyroscope sensor.
Greg Kroah-Hartman
maintainerPATCH 3/20 iio: Add inverse unit conversion macros
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit c689a923c867eac40ed3826c1d9328edea8b6bc7 upstream.
Add inverse unit conversion macro to convert from standard IIO units to units that might be used by some devices.
Those are useful in combination with scale factors that are specified as IIO_VAL_FRACTIONAL. Typically the denominator for those specifications will contain the maximum raw value the sensor will generate and the numerator the value it maps to in a specific unit. Sometimes datasheets specify those in different units than the standard IIO units (e.g. degree/s instead of rad/s) and so we need to do a unit conversion.
Quoted 1 line
Quoted 1 line
From a mathematical point of view it does not make a difference whether we
apply the unit conversion to the numerator or the inverse unit conversion to the denominator since (x / y) / z = x / (y * z). But as the denominator is typically a larger value and we are rounding both the numerator and denominator to integer values using the later method gives us a better precision (E.g. the relative error is smaller if we round 8000.3 to 8000 rather than rounding 8.3 to 8).
This is where in inverse unit conversion macros will be used.
Marked for stable as used by some upcoming fixes.
--- include/linux/iio/iio.h | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
include/linux/iio/iio.h +17 -0
@@ -569,6 +569,15 @@ int iio_str_to_fixpoint(const char *str,#define IIO_DEGREE_TO_RAD (deg) (((deg) * 314159ULL + 9000000ULL) / 18000000ULL)/** +* IIO_RAD_TO_DEGREE() - Convert rad to degree +* @rad: A value in rad +* +* Returns the given value converted from rad to degree +*/ +#define IIO_RAD_TO_DEGREE (rad) \ + (((rad) * 18000000ULL + 314159ULL / 2) / 314159ULL) + +/** * IIO_G_TO_M_S_2() - Convert g to meter / second**2 * @g: A value in g *
@@ -576,4 +585,12 @@ int iio_str_to_fixpoint(const char *str,*/ #define IIO_G_TO_M_S_2 (g) ((g) * 980665ULL / 100000ULL) +/** +* IIO_M_S_2_TO_G() - Convert meter / second**2 to g +* @ms2: A value in meter / second**2 +* +* Returns the given value converted from meter / second**2 to g +*/ +#define IIO_M_S_2_TO_G (ms2) (((ms2) * 100000ULL + 980665ULL / 2) / 980665ULL) +#endif /* _INDUSTRIAL_IO_H_ */
Greg Kroah-Hartman
maintainerPATCH 4/20 iio: adis16480: Fix scale factors
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit 7abad1063deb0f77d275c61f58863ec319c58c5c upstream.
The different devices support by the adis16480 driver have slightly different scales for the gyroscope and accelerometer channels.
--- drivers/iio/imu/adis16480.c | 39 +++++++++++++++++++++++++++++++++------ 1 file changed, 33 insertions(+), 6 deletions(-)
drivers/iio/imu/adis16480.c +33 -6
@@ -110,6 +110,10 @@struct adis16480_chip_info {unsigned int num_channels;const struct iio_chan_spec *channels; +unsigned int gyro_max_val; +unsigned int gyro_max_scale; +unsigned int accel_max_val; +unsigned int accel_max_scale; };struct adis16480 {
@@ -533,19 +537,21 @@ static int adis16480_set_filter_freq(strstatic int adis16480_read_raw (struct iio_dev *indio_dev,const struct iio_chan_spec *chan,int *val,int *val2,long info) { +struct adis16480 *st =iio_priv (indio_dev); +switch (info) {case IIO_CHAN_INFO_RAW :return adis_single_conversion (indio_dev, chan,0 , val);case IIO_CHAN_INFO_SCALE :switch (chan->type) {case IIO_ANGL_VEL : - *val =0 ; - *val2 =IIO_DEGREE_TO_RAD (20000 );/* 0.02 degree/sec */ -return IIO_VAL_INT_PLUS_MICRO ; + *val = st->chip_info->gyro_max_scale; + *val2 = st->chip_info->gyro_max_val; +return IIO_VAL_FRACTIONAL ;case IIO_ACCEL : - *val =0 ; - *val2 =IIO_G_TO_M_S_2 (800 );/* 0.8 mg */ -return IIO_VAL_INT_PLUS_MICRO ; + *val = st->chip_info->accel_max_scale; + *val2 = st->chip_info->accel_max_val; +return IIO_VAL_FRACTIONAL ;case IIO_MAGN : *val =0 ; *val2 =100 ;/* 0.0001 gauss */
@@ -702,18 +708,39 @@ static const struct adis16480_chip_info [ADIS16375 ] = { .channels = adis16485_channels, .num_channels =ARRAY_SIZE (adis16485_channels), +/* +* storing the value in rad/degree and the scale in degree +* gives us the result in rad and better precession than +* storing the scale directly in rad. +*/ + .gyro_max_val =IIO_RAD_TO_DEGREE (22887 ), + .gyro_max_scale =300 , + .accel_max_val =IIO_M_S_2_TO_G (21973 ), + .accel_max_scale =18 , }, [ADIS16480 ] = { .channels = adis16480_channels, .num_channels =ARRAY_SIZE (adis16480_channels), + .gyro_max_val =IIO_RAD_TO_DEGREE (22500 ), + .gyro_max_scale =450 , + .accel_max_val =IIO_M_S_2_TO_G (12500 ), + .accel_max_scale =5 , }, [ADIS16485 ] = { .channels = adis16485_channels, .num_channels =ARRAY_SIZE (adis16485_channels), + .gyro_max_val =IIO_RAD_TO_DEGREE (22500 ), + .gyro_max_scale =450 , + .accel_max_val =IIO_M_S_2_TO_G (20000 ), + .accel_max_scale =5 , }, [ADIS16488 ] = { .channels = adis16480_channels, .num_channels =ARRAY_SIZE (adis16480_channels), + .gyro_max_val =IIO_RAD_TO_DEGREE (22500 ), + .gyro_max_scale =450 , + .accel_max_val =IIO_M_S_2_TO_G (22500 ), + .accel_max_scale =18 , }, };
Greg Kroah-Hartman
maintainerPATCH 5/20 clk: versatile: off by one in clk_sp810_timerclken_of_get()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 3294bee87091be5f179474f6c39d1d87769635e2 upstream.
The ">" should be ">=" or we end up reading beyond the end of the array.
--- drivers/clk/versatile/clk-sp810.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/clk/versatile/clk-sp810.c +2 -2
@@ -128,8 +128,8 @@ struct clk *clk_sp810_timerclken_of_get( {struct clk_sp810 *sp810 = data; -if (WARN_ON (clkspec->args_count !=1 || clkspec->args[0 ] > -ARRAY_SIZE (sp810->timerclken))) +if (WARN_ON (clkspec->args_count !=1 || + clkspec->args[0 ] >=ARRAY_SIZE (sp810->timerclken)))return NULL ;return sp810->timerclken[clkspec->args[0 ]].clk;
Greg Kroah-Hartman
maintainerPATCH 6/20 PCI: Fix TI816X class code quirk
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bjorn Helgaas <[email protected]>
commit d1541dc977d376406f4584d8eb055488655c98ec upstream.
In fixup_ti816x_class(), we assigned "class = PCI_CLASS_MULTIMEDIA_VIDEO". But PCI_CLASS_MULTIMEDIA_VIDEO is only the two-byte base class/sub-class and needs to be shifted to make space for the low-order interface byte.
Shift PCI_CLASS_MULTIMEDIA_VIDEO to set the correct class code.
--- drivers/pci/quirks.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/pci/quirks.c +6 -3
@@ -2796,12 +2796,15 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INstatic void fixup_ti816x_class (struct pci_dev *dev) { +u32 class = dev->class; +/* TI 816x devices do not have class code set when in PCIe boot mode */ -dev_info (&dev->dev,"Setting PCI class for 816x PCIe device\n" ); - dev->class =PCI_CLASS_MULTIMEDIA_VIDEO ; + dev->class =PCI_CLASS_MULTIMEDIA_VIDEO <<8 ; +dev_info (&dev->dev,"PCI class overridden (%#08x -> %#08x)\n" , + class, dev->class); }DECLARE_PCI_FIXUP_CLASS_EARLY (PCI_VENDOR_ID_TI ,0xb800 , -PCI_CLASS_NOT_DEFINED ,0 , fixup_ti816x_class); +PCI_CLASS_NOT_DEFINED ,0 , fixup_ti816x_class);/* Some PCIe devices do not work reliably with the claimed maximum * payload size supported.
Greg Kroah-Hartman
maintainerPATCH 7/20 USB: symbolserial: Use usb_get_serial_port_data
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Philipp Hachtmann <[email protected]>
commit 951d3793bbfc0a441d791d820183aa3085c83ea9 upstream.
The driver used usb_get_serial_data(port->serial) which compiled but resulted in a NULL pointer being returned (and subsequently used). I did not go deeper into this but I guess this is a regression.
port_probe")
--- drivers/usb/serial/symbolserial.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/usb/serial/symbolserial.c +3 -3
@@ -97,7 +97,7 @@ exit:static int symbol_open (struct tty_struct *tty,struct usb_serial_port *port) { -struct symbol_private *priv =usb_get_serial_data (port->serial); +struct symbol_private *priv =usb_get_serial_port_data (port);unsigned long flags;int result =0 ;
@@ -123,7 +123,7 @@ static void symbol_close(struct usb_seristatic void symbol_throttle (struct tty_struct *tty) {struct usb_serial_port *port = tty->driver_data; -struct symbol_private *priv =usb_get_serial_data (port->serial); +struct symbol_private *priv =usb_get_serial_port_data (port);spin_lock_irq (&priv->lock); priv->throttled = true;
@@ -133,7 +133,7 @@ static void symbol_throttle(struct tty_sstatic void symbol_unthrottle (struct tty_struct *tty) {struct usb_serial_port *port = tty->driver_data; -struct symbol_private *priv =usb_get_serial_data (port->serial); +struct symbol_private *priv =usb_get_serial_port_data (port);int result;bool was_throttled;
Greg Kroah-Hartman
maintainerPATCH 17/20 auxdisplay: ks0108: fix refcount
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sudip Mukherjee <[email protected]>
commit bab383de3b84e584b0f09227151020b2a43dc34c upstream.
parport_find_base() will implicitly do parport_get_port() which increases the refcount. Then parport_register_device() will again increment the refcount. But while unloading the module we are only doing parport_unregister_device() decrementing the refcount only once. We add an parport_put_port() to neutralize the effect of parport_get_port().
--- drivers/auxdisplay/ks0108.c | 1 + 1 file changed, 1 insertion(+)
drivers/auxdisplay/ks0108.c +1 -0
@@ -139,6 +139,7 @@ static int __init ks0108_init(void) ks0108_pardevice =parport_register_device (ks0108_parport,KS0108_NAME ,NULL ,NULL ,NULL ,PARPORT_DEV_EXCL ,NULL ); +parport_put_port (ks0108_parport);if (ks0108_pardevice ==NULL ) { printk(KERN_ERR KS0108_NAME ": ERROR: " "parport didn't register new device\n");
Greg Kroah-Hartman
maintainerPATCH 18/20 of/address: Dont loop forever in of_find_matching_node_by_address().
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Daney <[email protected]>
commit 3a496b00b6f90c41bd21a410871dfc97d4f3c7ab upstream.
If the internal call to of_address_to_resource() fails, we end up looping forever in of_find_matching_node_by_address(). This can be caused by a defective device tree, or calling with an incorrect matches argument.
Fix by calling of_find_matching_node() unconditionally at the end of the loop.
--- drivers/of/address.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/of/address.c +3 -3
@@ -629,10 +629,10 @@ struct device_node *of_find_matching_nodstruct resource res;while (dn) { -if (of_address_to_resource (dn,0 , &res)) -continue ; -if (res.start == base_address) +if (!of_address_to_resource (dn,0 , &res) && + res.start == base_address)return dn; + dn =of_find_matching_node (dn, matches); }
Greg Kroah-Hartman
maintainerPATCH 19/20 drivercore: Fix unregistration path of platform devices
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Grant Likely <[email protected]>
commit 7f5dcaf1fdf289767a126a0a5cc3ef39b5254b06 upstream.
The unregister path of platform_device is broken. On registration, it will register all resources with either a parent already set, or type==IORESOURCE_{IO,MEM}. However, on unregister it will release everything with type==IORESOURCE_{IO,MEM}, but ignore the others. There are also cases where resources don't get registered in the first place, like with devices created by of_platform_populate()*.
Fix the unregister path to be symmetrical with the register path by checking the parent pointer instead of the type field to decide which resources to unregister. This is safe because the upshot of the registration path algorithm is that registered resources have a parent pointer, and non-registered resources do not.
* It can be argued that of_platform_populate() should be registering it's resources, and they argument has some merit. However, there are quite a few platforms that end up broken if we try to do that due to overlapping resources in the device tree. Until that is fixed, we need to solve the immediate problem.
--- drivers/base/platform.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
drivers/base/platform.c +2 -6
@@ -347,9 +347,7 @@ int platform_device_add(struct platform_while (--i >=0 ) {struct resource *r = &pdev->resource[i]; -unsigned long type =resource_type (r); - -if (type ==IORESOURCE_MEM || type ==IORESOURCE_IO ) +if (r->parent)release_resource (r); }
@@ -380,9 +378,7 @@ void platform_device_del(struct platformfor (i =0 ; i < pdev->num_resources; i++) {struct resource *r = &pdev->resource[i]; -unsigned long type =resource_type (r); - -if (type ==IORESOURCE_MEM || type ==IORESOURCE_IO ) +if (r->parent)release_resource (r); } }
Greg Kroah-Hartman
maintainerPATCH 16/20 devres: fix devres_get()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Masahiro Yamada <[email protected]>
commit 64526370d11ce8868ca495723d595b61e8697fbf upstream.
Currently, devres_get() passes devres_free() the pointer to devres, but devres_free() should be given with the pointer to resource data.
--- drivers/base/devres.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/base/devres.c +2 -2
@@ -296,10 +296,10 @@ void * devres_get(struct device *dev, voif (!dr) {add_dr (dev, &new_dr->node); dr = new_dr; - new_dr =NULL ; + new_res =NULL ; }spin_unlock_irqrestore (&dev->devres_lock, flags); -devres_free (new_dr); +devres_free (new_res);return dr->data; }
Greg Kroah-Hartman
maintainerPATCH 20/20 hpfs: update ctime and mtime on directory modification
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mikulas Patocka <[email protected]>
commit f49a26e7718dd30b49e3541e3e25aecf5e7294e2 upstream.
Update ctime and mtime when a directory is modified. (though OS/2 doesn't update them anyway)
--- fs/hpfs/namei.c | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-)
fs/hpfs/namei.c +24 -1
@@ -8,6 +8,17 @@#include <linux/sched.h> #include "hpfs_fn.h" +static void hpfs_update_directory_times (struct inode *dir) +{ +time_t t =get_seconds (); +if (t == dir->i_mtime.tv_sec && + t == dir->i_ctime.tv_sec) +return ; + dir->i_mtime.tv_sec = dir->i_ctime.tv_sec = t; + dir->i_mtime.tv_nsec = dir->i_ctime.tv_nsec =0 ; +hpfs_write_inode_nolock (dir); +} +static int hpfs_mkdir (struct inode *dir,struct dentry *dentry,umode_t mode) {const unsigned char *name = dentry->d_name.name;
@@ -99,6 +110,7 @@ static int hpfs_mkdir(struct inode *dir, result->i_mode = mode |S_IFDIR ;hpfs_write_inode_nolock (result); } +hpfs_update_directory_times (dir);d_instantiate (dentry, result);hpfs_unlock (dir->i_sb);return 0 ;
@@ -187,6 +199,7 @@ static int hpfs_create(struct inode *dir result->i_mode = mode |S_IFREG ;hpfs_write_inode_nolock (result); } +hpfs_update_directory_times (dir);d_instantiate (dentry, result);hpfs_unlock (dir->i_sb);return 0 ;
@@ -262,6 +275,7 @@ static int hpfs_mknod(struct inode *dir,insert_inode_hash (result);hpfs_write_inode_nolock (result); +hpfs_update_directory_times (dir);d_instantiate (dentry, result);brelse (bh);hpfs_unlock (dir->i_sb);
@@ -340,6 +354,7 @@ static int hpfs_symlink(struct inode *diinsert_inode_hash (result);hpfs_write_inode_nolock (result); +hpfs_update_directory_times (dir);d_instantiate (dentry, result);hpfs_unlock (dir->i_sb);return 0 ;
@@ -423,6 +438,8 @@ again: out1:hpfs_brelse4 (&qbh); out: +if (!err) +hpfs_update_directory_times (dir);hpfs_unlock (dir->i_sb);return err; }
@@ -477,6 +494,8 @@ static int hpfs_rmdir(struct inode *dir, out1:hpfs_brelse4 (&qbh); out: +if (!err) +hpfs_update_directory_times (dir);hpfs_unlock (dir->i_sb);return err; }
@@ -595,7 +614,7 @@ static int hpfs_rename(struct inode *old goto end1; } - end: +end:hpfs_i (i)->i_parent_dir = new_dir->i_ino;if (S_ISDIR (i->i_mode)) {inc_nlink (new_dir);
@@ -610,6 +629,10 @@ static int hpfs_rename(struct inode *oldbrelse (bh); } end1: +if (!err) { +hpfs_update_directory_times (old_dir); +hpfs_update_directory_times (new_dir); + }hpfs_unlock (i->i_sb);return err; }
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
Build results:
total: 121 pass: 121 fail: 0 Qemu test results: total: 70 pass: 70 fail: 0
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
defconfig and allmodconfig with xtensa failed. With 3.10.88-rc1 I reported that 123f15e669d5 ("xtensa: don't use echo -e needlessly") is required to fix the build failure.
Build at:
https://travis-ci.org/sudipm-mukherjee/parport/builds/81232373
regards
sudip
Quoted 6 lines · Sudip Mukherjee
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Quoted 6 lines
Quoted 2 lines
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
defconfig and allmodconfig with xtensa failed. With 3.10.88-rc1 I reported that
123f15e669d5("xtensa: don't use echo -e needlessly") is required to fix the build failure.
Note that it probably only fails to build for you because you use dash as default shell.
Guenter
Quoted 9 lines · Guenter Roeck
Quoted 8 lines · Sudip Mukherjee
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
Quoted 7 lines
Quoted 4 lines
defconfig and allmodconfig with xtensa failed. With 3.10.88-rc1 I reported that
123f15e669d5("xtensa: don't use echo -e needlessly") is required to fix the build failure.Note that it probably only fails to build for you because you use dash as default shell.
Which I think Debian does :(
I've queued this up, thanks.
greg k-h
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
Compiled and booted on x86_32. No errors in dmesg.
regards
sudip
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.89 release. There are 20 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Mon Sep 21 17:16:03 UTC 2015. Anything received after that time might be too late.
Quoted 8 lines
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.89-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Signature · 5 lines
Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) [email protected] | (970) 217-8978
Re: [PATCH 3.10 02/20] iio: bmg160: IIO_BUFFER and IIO_TRIGGERED_BUFFER are required
In reply to Greg Kroah-HartmanQuoted 23 lines · Greg Kroah-Hartman
3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Pargmann <[email protected]>
commit
06d2f6ca5a38abe92f1f3a132b331eee773868c3upstream.This patch adds selects for
IIO_BUFFERandIIO_TRIGGERED_BUFFER. WithoutIIO_BUFFER, the driver does not compile.Signed-off-by Markus Pargmann <[email protected]>Reviewed-by Srinivas Pandruvada <[email protected]>Signed-off-by Jonathan Cameron <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>--- drivers/iio/gyro/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/iio/gyro/Kconfig config IIO_ST_GYRO_SPI_3AXIS · line 73
Quoted 1 line
drivers/iio/gyro/Kconfig +0
-0@@ -73,7 +73,8 @@ config IIO_ST_GYRO_SPI_3AXIS config ITG3200
I know it's a bit too late as this kernel has been released already, but this patch doesn't look right to me. The original patch is changing the BMG160 driver, not the ITG3200.
The same applies to the 3.14 kernel -- it's changing the wrong driver.
Cheers,
--
Lu�s
Quoted 14 lines
drivers/iio/gyro/Kconfig +2
-2tristate "InvenSense ITG3200 Digital 3-Axis Gyroscope I2C driver" depends on I2C - select IIO_TRIGGERED_BUFFER if IIO_BUFFER + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER help Say yes here to add support for the InvenSense ITG3200 digital 3-axis gyroscope sensor. --To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 3.10 02/20] iio: bmg160: IIO_BUFFER and IIO_TRIGGERED_BUFFER are required
Hi,
Quoted 30 lines · Luis Henriques
Quoted 23 lines · Greg Kroah-Hartman
3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Pargmann <[email protected]>
commit
06d2f6ca5a38abe92f1f3a132b331eee773868c3upstream.This patch adds selects for
IIO_BUFFERandIIO_TRIGGERED_BUFFER. WithoutIIO_BUFFER, the driver does not compile.Signed-off-by Markus Pargmann <[email protected]>Reviewed-by Srinivas Pandruvada <[email protected]>Signed-off-by Jonathan Cameron <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>--- drivers/iio/gyro/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)drivers/iio/gyro/Kconfig config IIO_ST_GYRO_SPI_3AXIS · line 73
Quoted 1 line
drivers/iio/gyro/Kconfig +0
-0@@ -73,7 +73,8 @@ config IIO_ST_GYRO_SPI_3AXIS config ITG3200I know it's a bit too late as this kernel has been released already, but this patch doesn't look right to me. The original patch is changing the BMG160 driver, not the ITG3200.
Quoted 2 lines
The same applies to the 3.14 kernel -- it's changing the wrong driver.
Thanks, this is right. I didn't notice this but the driver was introduced in 3.18:
22b46c45fb9b (iio:gyro:bmg160 Gyro Sensor driver)
Best Regards,
Markus
Quoted 20 lines
Cheers,
--
LuísQuoted 14 lines
drivers/iio/gyro/Kconfig +2
-2tristate "InvenSense ITG3200 Digital 3-Axis Gyroscope I2C driver" depends on I2C - select IIO_TRIGGERED_BUFFER if IIO_BUFFER + select IIO_BUFFER + select IIO_TRIGGERED_BUFFER help Say yes here to add support for the InvenSense ITG3200 digital 3-axis gyroscope sensor. --To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 4 lines
Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |