20 Jun, 2015
1 commit
-
The platform_device_id is not modified by the driver and core uses it as
const.Signed-off-by: Krzysztof Kozlowski
Signed-off-by: Alexandre Belloni
23 Feb, 2015
1 commit
-
Add additional flag to read in async mode. In this mode the caller will get
reply via registered callback for capture_sample. Callbacks can be registered
using sensor_hub_register_callback function. The usage id parameter of the
capture_sample can be matched with the usage id of the requested attribute.Signed-off-by: Srinivas Pandruvada
Acked-by: Jonathan Cameron
Signed-off-by: Jiri Kosina
20 Oct, 2014
1 commit
-
A platform_driver does not need to set an owner, it will be populated by the
driver core.Signed-off-by: Wolfram Sang
15 Nov, 2013
3 commits
-
Use this new function to make code more comprehensible, since we are
reinitialzing the completion, not initializing.[akpm@linux-foundation.org: linux-next resyncs]
Signed-off-by: Wolfram Sang
Acked-by: Linus Walleij (personally at LCE13)
Cc: Ingo Molnar
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Enable the processing of HID input records before the RTC will be
registered, in order to allow the RTC register function to read clock.
Without doing that the clock can only be read after the probe function
has finished.Signed-off-by: Alexander Holler
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly. This is a cosmetic change to
make the code simpler and enhance the readability.Signed-off-by: Jingoo Han
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
02 Oct, 2013
1 commit
-
Open sensor hub when module is loaded and close when module is removed.
This helps saving power by opening HID transport only when there is an
user.Signed-off-by: Srinivas Pandruvada
Acked-by: Alessandro Zummo
Signed-off-by: Jonathan Cameron
12 Sep, 2013
2 commits
-
Stop processing hid input when registering the RTC fails and handle a NULL
returned from devm_rtc_device_register() as a failure too.Signed-off-by: Alexander Holler
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
In order to get the module automatically loaded by hotplug mechanisms a
MODULE_DEVICE_TABLE is needed.Therefore add one.
This makes it also possible to use a module name other than
HID-SENSOR-2000a0 which isn't very descriptive in kernel messages.Signed-off-by: Alexander Holler
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
04 Jul, 2013
2 commits
-
There is no real reason to not support 16 or 32 bit values too.
Signed-off-by: Alexander Holler
Cc: Alessandro Zummo
Cc: Lars-Peter Clausen
Cc: Jonathan Cameron
Cc: Jiri Kosina
Cc: John Stultz
Cc: Jingoo Han
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
The draft for HID-sensors (HUTRR39) currently doesn't define the range
for the attribute year. Asking one of the authors revealed that full
years (e.g. 2013 instead of just 13) were meant.So we now allow both, 8 bit and 16 bit values for the attribute year and
assuming full years when the value is 16 bits wide.We will still support 8 bit values until the specification gets final
(and maybe defines a way to set the time too).Signed-off-by: Alexander Holler
Cc: Alessandro Zummo
Cc: Lars-Peter Clausen
Cc: Jonathan Cameron
Cc: Jiri Kosina
Cc: John Stultz
Cc: Jingoo Han
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
30 Apr, 2013
1 commit
-
devm_rtc_device_register() is device managed and makes cleanup paths
simpler.Signed-off-by: Jingoo Han
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
26 Jan, 2013
1 commit
-
Signed-off-by: Axel Lin
Acked-by: Alexander Holler
Signed-off-by: Jonathan Cameron
06 Jan, 2013
2 commits
-
The structure with common attributes for hid-sensors isn't specific
to the iio-subsystem, so rename it to hid_sensor_common.Signed-off-by: Alexander Holler
Acked-by: Jiri Kosina
Signed-off-by: Jonathan Cameron -
This driver makes the time from HID sensors (hubs) which are offering
such available like any other RTC does.It is necessary that all values like year, month etc, are send as
8bit values (1 byte each) and all of them in 1 report. Also the
spec HUTRR39b doesn't define the range of the year field, we
tread it as 0 - 99 because that's what most RTCs I know about are
offering.Currently the time can only be read. Setting the time must be done
through sending a report (or a feature). The spec currently doesn't
define how and I'm not sure if I just should define something by myself.Signed-off-by: Alexander Holler
Signed-off-by: Jonathan Cameron