- 20 Sep, 2016 1 commit
-
-
Greg Kroah-Hartman authored
Merge tag 'iio-for-4.9c' of git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio into staging-next Jonathan writes: Third set of new device support, functionality and cleanups for IIO in the 4.9 cycle. Given Linus is hinting (strongly!) at an rc8 this last set is hopefully in time for the 4.9 merge window. The zpa2326 and si1145 drivers provide fine illustrations that devices aren't getting any simpler! I'm also particularly pleased Linus Walliej did such a thorough job of cleaning up one of my old drivers. New device support * mCube MC3230 accelerometer - new fairly minimal driver. * Murata zpa2326 - extensive new driver supporting the rather 'novel' buffering of data this device provides and handling both it's own data ready trigger and other triggers rather elegantly. * si1141, si1142, si1143, si1145, si1146 and si1147 proximity, UV, visible and IR sensors. - another extensive new driver supporting all the key bits of what this set of devices supplies including dataready triggers, buffers and all the various data channels. Functionality * kxsd9 - Linus brought this scratch driver I wrote in one afternoon years ago up to date adding lots of good stuff along the way. - SPI support after extensive rework of the driver. - Triggered buffer capture support. - Runtime PM. - Regulator handling. - Mounting matrix support. * mma7660 - Add MODULE_DEVICE_TABLE to support autoprobing. Cleanups * ad5933 - Align some function arguements nicely. * med_z188 - Constify iio_info structure. * sca3000 - Implement IIO_CHAN_INFO_SAMP_FREQ rather than a hand rolled attr. There are still quite a few drivers that would benefit from similar updates. * ssp_sensors - Constify iio_info structures in accel and gyro drivers.
-
- 19 Sep, 2016 39 commits
-
-
Greg Kroah-Hartman authored
This merges the greybus branch into staging-testing. It contains the drivers/staging/greybus/ subsystem and related drivers and has passed the 0-day bot tests so no builds should break. Signed-off-by:Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Rui Miguel Silva authored
Add me to some Greybus protocol drivers maintainers, spi, sdio, power supply, light and gpio. Signed-off-by:
Rui Miguel Silva <rmfrfs@gmail.com> Signed-off-by:
-
Greg Kroah-Hartman authored
Johan and Alex and I are going to maintain the greybus code, so add it to MAINTAINERS so we get cc:ed on patches. Acked-by:
Johan Hovold <johan@kernel.org> Acked-by:
Alex Elder <elder@kernel.org> Signed-off-by:
-
Greg Kroah-Hartman authored
The last thing remaining in kernel_ver.h was the setting of CONFIG_PM_RUNTIME, which isn't needed in a in-tree implementation. So remove the setting of this value, and the .h file entirely as that was the last thing left in it. Signed-off-by:Greg Kroah-Hartman <gregkh@google.com>
-
Rui Miguel Silva authored
Remove BROKEN keyword to allow the light driver to be select now that we fixed the kernel version dependencies. Also fix the module name in the help section. Signed-off-by:
Rui Miguel Silva <rui.silva@linaro.org> Signed-off-by:
-
Rui Miguel Silva authored
Greybus SPI driver depends on gb-spilib and we need to state that at makefile to make it link correctly. Signed-off-by:
-
Rui Miguel Silva authored
No need to support older kernel versions in the Greybus Power Supply driver, so remove the checks as needed, we can now rely on all of the correct Power Supply core apis being present. Also move some properties definitions to the power supply greybus code. Signed-off-by:
-
Rui Miguel Silva authored
No need to support older kernel versions in the Greybus SDIO driver, so remove the checks as needed, we can now rely on all of the correct SDIO core apis being present. Signed-off-by:
-
Rui Miguel Silva authored
No need to support older kernel versions in the Greybus Light driver, so remove the checks as needed, we can now rely on all of the correct LED core apis being present. And compile only if flash and v4l2 flash is reachable. Signed-off-by:
-
Greg Kroah-Hartman authored
The 0-day bot pointed out a type difference in one min() call, so fix it up by being explicit about the type being compared. Reported-by:
kbuild test robot <fengguang.wu@intel.com> Signed-off-by:
-
Greg Kroah-Hartman authored
No need to support older kernel versions in the Greybus SPI and spilib driver, so remove the checks as needed, we can now rely on all of the correct SPI core apis being present. Signed-off-by: -
Greg Kroah-Hartman authored
The GPIO dependancy is CONFIG_GPIOLIB, not CONFIG_GPIO, no wonder it wasn't building properly... Signed-off-by: -
Greg Kroah-Hartman authored
No need to support older kernel versions in the Greybus GPIO driver, so remove the checks as needed, we can now rely on all of the correct GPIO core apis being present. Signed-off-by: -
Greg Kroah-Hartman authored
No need to support older kernel versions in the Greybus Vibrator driver, so remove the checks as needed, we can now rely on all of the correct driver core apis being present. Signed-off-by: -
Greg Kroah-Hartman authored
No need to support older kernel versions in the Greybus HID driver, so remove the checks as needed, we can now rely on all of the "new" apis being present. Signed-off-by: -
Greg Kroah-Hartman authored
Now that we do not care about the kernel version we are building against, we can strip out lots of backward compatibilty that was added to kernel_ver.h in order to write semi-portable driver code. To start with, remove the functions and #defines that are now in the kernel tree, no need to have duplicate copies of them all. Signed-off-by: -
Greg Kroah-Hartman authored
This adds a proper Kconfig file for drivers/staging/greybus and fixes up the Makefile to work correctly within the kernel build system (modules depend on the .config options, etc.) Signed-off-by: -
Greg Kroah-Hartman authored
The Toshiba ES1 chip is no longer around, so remove the USB descriptor documentation for it as no one cares anymore. Signed-off-by: -
Greg Kroah-Hartman authored
Only the tools subdirectory needs a .gitignore entry, so move it there and fix it up to only list the needed file. Signed-off-by: -
Greg Kroah-Hartman authored
We don't need yet-another-copy of the GPLv2 in the tree, and the README is now pointless, so remove both of these files. Signed-off-by: -
Greg Kroah-Hartman authored
We do not need an example of the sysfs tree in the kernel code itself, so remove these files, as they are now pointless. Signed-off-by: -
Greg Kroah-Hartman authored
When the greybus tree was external, it contained a copy of checkpatch.pl to keep everyone "in line". This is no longer needed and can now be removed. Signed-off-by: -
Greg Kroah-Hartman authored
This pulls the external greybus driver tree into 4.8-rc6 as it should be part of the main kernel tree and not live outside in some lonely github repo, never to be reunited with it's true love... Signed-off-by: -
James Simmons authored
With all of the the missing patches from the lustre 2.7 version merged upstream its time to update the upstream clients version. Signed-off-by:
James Simmons <jsimmons@infradead.org> Signed-off-by:
-
Doug Oucharek authored
The previous patch, http://review.whamcloud.com/21304/, removed a check needed until LU-5718 is properly addressed. With the check, LU-5718 results in an error message and a lost RDMA operation. Without it, we have memory corruption and a crash (much harder to debug). Putting the check back in case LU-5718 is not fixed soon. Signed-off-by:
Doug Oucharek <doug.s.oucharek@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7650 Reviewed-on: http://review.whamcloud.com/22281Reviewed-by:
James Simmons <uja.ornl@yahoo.com> Reviewed-by:
Olaf Weber <olaf@sgi.com> Reviewed-by:
Oleg Drokin <oleg.drokin@intel.com> Signed-off-by:
-
Doug Oucharek authored
The code to allow peer_credits to be set per NI was originally "left inactive" because there were concerns about peer_credits interfering with the ability for IB nodes to connect to each other when peer_credits are not the same (peer_credits controls the queue depth for IB). With LU-3322, the values do not have to match so it is now safe to enable this code so peer_credits can be set per NI. This patch enables existing code for setting per NI peer_credits. Second this patch fixes a long standing bug in that the conf data was not being used to set variables in the lnet_ni structure until after lnd_startup() was called which meant LND drivers were ignoring struct lnet_ni tunable values being set. Now we change struct lnet_ni data fields based on conf data before calling lnd_startup(). Signed-off-by:
Dmitry Eremin <dmitry.eremin@intel.com> Reviewed-by:
-
Doug Oucharek authored
In lnet_rtrpools_enable(), a mistake was made and routing was not being turned on when the rtrpools are being allocated for the first time. This patch fixes that routine so we remember to turn on routing after allocating the rtrpools. Signed-off-by:
Amir Shehata <amir.shehata@intel.com> Reviewed-by:
-
Sebastien Buisson authored
Add new 'ni_net_ns' field to struct lnet_ni to hold a reference to original net namespace in which ni is created. In LNetDist(), check if ni was created in same net namespace as current's one. If not, assign order above 0xffff0000, to make this ni not a priority. Signed-off-by:
Sebastien Buisson <sbuisson@ddn.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7845 Reviewed-on: http://review.whamcloud.com/21884Reviewed-by:
-
Quentin Bouget authored
Fixes potential deadlock in LNetMDAttach Signed-off-by:
Quentin Bouget <quentin.bouget.ocre@cea.fr> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8249 Reviewed-on: http://review.whamcloud.com/20676Reviewed-by:
Henri Doreau <henri.doreau@cea.fr> Reviewed-by:
-
wang di authored
If the migrating directory is under striped directory, it needs to set right stripe FID for its parent. Signed-off-by:
wang di <di.wang@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6263 Reviewed-on: http://review.whamcloud.com/13817Reviewed-by:
John L. Hammond <john.hammond@intel.com> Reviewed-by:
Andreas Dilger <andreas.dilger@intel.com> Reviewed-by:
Fan Yong <fan.yong@intel.com> Reviewed-by:
Lai Siyao <lai.siyao@intel.com> Signed-off-by:
-
Ned Bass authored
The client_obd::cl_default_mds_easize field should track the largest observed EA size advertised by the MDT, subject to a reasonable upper bound. The MDC uses cl_default_mds_easize to calculate the initial size of request buffers. The default value should be small enough to avoid wasted memory and excessive use of vmalloc(), yet large enough to accommodate the common use case. In the current code, the default value is only updated if client_obd::cl_max_mds_easize is strictly less than mdt_body::mbo_max_mdsize. This condition is almost never met, because client_obd::cl_max_mds_easize is computed at client mount-time based on the number of OSTs in the filesystem, so the MDT won't ever observe and advertise an EA size larger than that. As a result, client_obd::cl_default_mds_easize indefinitely retains its initial value, which is computed at client mount-time based on the filesystem's default stripe width. Any getattr() requests for widely striped files will consequently allocate a request buffer that is too small, forcing reallocations on both the client and server side. To avoid this, update client_obd::cl_default_mds_easize independently of the value of client_obd::cl_max_mds_easize. In addition, this patch includes these changes: - Add comments to the client_obd structure to clarify what the cl_{default,max}_mds_{cookie,ea}size values mean. - Prevent mdc_get_info() from storing uninitialized data in client_obd::cl_max_mds_cookiesize. - Use 4096 as an upper bound for the default values. The former bound of PAGE_CACHE_SIZE is too large on 64k-page platforms (i.e. PPC), so it fails to prevent the vmalloc() spinlock contention described in LU-3338. The new value was chosen to be large enough to accommodate common use cases while staying well below the 16k threshold at which allocations start using vmalloc(). Signed-off-by:Ned Bass <bass6@llnl.gov> Signed-off-by:
Kyle Blatter <kyleblatter@llnl.gov> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5549 Reviewed-on: http://review.whamcloud.com/11614Reviewed-by:
-
Ned Bass authored
Allow default_easize to be tuned via /sysfs. A system administrator might want this if a rare access to widely striped files drives up the value on a filesystem where narrowly striped files are the more common case. In practice, however, this is wanted primarily to facilitate a test case for LU-5549. - Plumb the necessary interfaces through the LMV and MDC layers to expose write access to this value by higher layers. - Add block comments to modified functions. Signed-off-by:
-
wang di authored
Add indexing option to default dirstripe EA. If MDT find out the client send the create req to the wrong MDT because of default stripeEA, it will return -EREMOTE, then client will retrieve default stripeEA through xattr cache, and re-create the object. Also merged patch for LU-6341 to resolve the following problem. Use ll_dir_getstripe to get default stripeEA in ll_new_node(), Because ll_getxattr_common requires admin rights for retrieving default LMVEA (because of trusted- prefix), which might cause mkdir (from normal user) failure. If parent does not have default stripeEA, then child should always be in the same MDT for mkdir. Otherwise MDT should return -EREMOTE, then client will refresh the default stripe index, and recreate the object. Signed-off-by:
-
Mikhail Pershin authored
Patch fixes the issue seen on the client with growing request timeout which occurred after the server side patch landed for LU-5079. While commit itself is correct, it reveals another issue. If request is being processed for a long time on server then client adaptive timeouts will adapt to that after receiving reply and new requests will have bigger timeout. Another problem is that server AT history is corrupted by recovery request processing time which not pure service time but includes also waiting time for clients to recover. Patch prevents the AT stats update from early replies on client and from recovering requests processing time on server. The ptlrpc_at_recv_early_reply() still updates the current request timeout as asked by server, but don't include this into AT stats. The real reply will bring that data from server after all. Signed-off-by:
Mikhail Pershin <mike.pershin@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6084 Reviewed-on: http://review.whamcloud.com/13520Reviewed-by:
Jian Yu <jian.yu@intel.com> Reviewed-by:
-
James Simmons authored
When a parameter is permanently changed on the MGS the MGS send a changelog packet to the proper nodes that are affected by the change. Once the nodes receive the change they then call the userland utility lctl to change its local value. When calling a userland application from the kernel you specify a flag to control the interaction with the application. Originally by default the flag was set to 0 which is UMH_NO_WAIT which meant lctl was being called asynchronously. In older kernels this was fine since UHM_NO_WAIT and UHM_WAIT_PROC had nearly the same logic. This changed with newer kernels which broke updating our parameters. Plus doing a UHM_NO_WAIT doesn't report back a error if something goes wrong with lctl. The fix is to set the flag to UHM_WAIT_PROC so kernel space waits until lctl has finished and we get a proper error code if something does go wrong with lctl. Signed-off-by:
James Simmons <uja.ornl@gmail.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6063 Reviewed-on: http://review.whamcloud.com/13677Reviewed-by:
Bob Glossman <bob.glossman@intel.com> Reviewed-by:
-
frank zago authored
A lot of symbols don't need to be exported at all because they are only used in the module they belong to. Signed-off-by:
frank zago <fzago@cray.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5829 Reviewed-on: http://review.whamcloud.com/12510Reviewed-by:
-
wang di authored
Because the inode and its connected dentries will be cleared out of the cache after migration, the inode needs to be locked during the migration. Signed-off-by:
-
frank zago authored
A lot of symbols don't need to be exported at all because they are only used in the module they belong to. Signed-off-by:
-
frank zago authored
A lot of symbols don't need to be exported at all because they are only used in the module they belong to. Signed-off-by:
-
