aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/input/misc/bma150.c (follow)
AgeCommit message (Expand)AuthorFilesLines
2019-10-29Input: bma150 - switch to using polled mode of input devicesDmitry Torokhov1-111/+44
2019-10-29Input: bma150 - use managed resources helpersJonathan Bakker1-37/+14
2019-05-24treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 61Thomas Gleixner1-14/+1
2019-02-06Input: bma150 - register input device after setting private dataJonathan Bakker1-4/+5
2017-04-01Input: bma150 - remove support for bma150H. Nikolaus Schaller1-10/+1
2016-12-27Input: bma150 - switch to using usleep_range instead of msleepAniroop Mathur1-2/+2
2016-11-16Input: bma150 - avoid binding to bma180 if IIO bma180 driver presentHans de Goede1-1/+8
2016-01-02Input: bma150 - constify bma150_cfg structureJulia Lawall1-1/+1
2015-07-17Input: drop owner assignment from i2c_driverKrzysztof Kozlowski1-1/+0
2015-07-07Input: bma150 - use sign_extend32() for sign extendingMartin Kepplinger1-4/+3
2014-04-24Input: bma150 - extend chip detection for bma180Dr. H. Nikolaus Schaller1-1/+3
2013-12-06Input: use dev_get_platdata()Jingoo Han1-1/+2
2013-02-15Input: bma150 - make some defines public and fix some commentsMichael Trimarchi1-12/+0
2013-02-15Input: bma150 - fix checking pm_runtime_get_sync() return valueMichael Trimarchi1-1/+1
2012-11-24Input: remove use of __devexitBill Pemberton1-1/+1
2012-11-24Input: remove use of __devinitBill Pemberton1-11/+11
2012-11-24Input: remove use of __devinitdataBill Pemberton1-1/+1
2012-11-24Input: remove use of __devexit_pBill Pemberton1-1/+1
2012-03-16Input: convert I2C drivers to use module_i2c_driver()Axel Lin1-12/+1
2011-08-09Input: add driver for Bosch Sensortec's BMA150 accelerometerEric Andersson1-0/+691
generated by cgit v1.2.3 (git 2.39.1) at 2026-01-03 08:34:56 +0000
-y since it is a very exceptional case which does not support UAPI. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-03-17kbuild: warn redundant generic-yMasahiro Yamada12-13/+6 The generic-y is redundant under the following condition: - arch has its own implementation - the same header is added to generated-y - the same header is added to mandatory-y If a redundant generic-y is found, the warning like follows is displayed: scripts/Makefile.asm-generic:20: redundant generic-y found in arch/arm/include/asm/Kbuild: timex.h I fixed up arch Kbuild files found by this. Suggested-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-03-17Revert "modsign: Abort modules_install when signing fails"Douglas Anderson1-1/+1 This reverts commit caf6fe91ddf62a96401e21e9b7a07227440f4185. The commit was fine but is no longer needed as of commit 3a2429e1faf4 ("kbuild: change if_changed_rule for multi-line recipe"). Let's go back to using ";" to be consistent. For some discussion, see: https://lkml.kernel.org/r/CAK7LNASde0Q9S5GKeQiWhArfER4S4wL1=R_FW8q0++_X3T5=hQ@mail.gmail.com Signed-off-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-03-17kbuild: Make NOSTDINC_FLAGS a simply expanded variableDouglas Anderson1-1/+1 During a simple no-op (nothing changed) build I saw 39 invocations of the C compiler with the argument "-print-file-name=include". We don't need to call the C compiler 39 times for this--one time will suffice. Let's change NOSTDINC_FLAGS to a simply expanded variable to avoid this since there doesn't appear to be any reason it should be recursively expanded. On my build this shaved ~400 ms off my "no-op" build. Note that the recursive expansion seems to date back to the (really old) commit e8f5bdb02ce0 ("[PATCH] Makefile include path ordering"). It's a little unclear to me if the point of that patch was to switch the variable to be recursively expanded (which it did) or to avoid directly assigning to NOSTDINC_FLAGS (AKA to switch to +=) because someone else (out of tree?) was setting it. I presume later since if the only goal was to switch to recursive expansion the patch would have just removed the ":". Signed-off-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> 2019-03-17kbuild: deb-pkg: avoid implicit effectsArseny Maslennikov1-1/+4 * The man page for dpkg-source(1) notes: > -b, --build directory [format-specific-parameters] > Build a source package (--build since dpkg 1.17.14). > <...> > > dpkg-source will build the source package with the first > format found in this ordered list: the format indicated > with the --format command line option, the format > indicated in debian/source/format, “1.0”. The fallback > to “1.0” is deprecated and will be removed at some point > in the future, you should always document the desired > source format in debian/source/format. See section > SOURCE PACKAGE FORMATS for an extensive description of > the various source package formats. Thus it would be more foolproof to explicitly use 1.0 (as we always did) than to rely on dpkg-source's defaults. * In a similar vein, debian/rules is not made executable by mkdebian, and dpkg-source warns about that but still silently fixes the file. Let's be explicit once again. Signed-off-by: Arseny Maslennikov <ar@cs.msu.ru> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>