18 Jul, 2015

1 commit


08 Jul, 2015

1 commit


25 Apr, 2014

1 commit


06 Dec, 2013

1 commit

  • 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
    Acked-by: Fugang Duan
    Signed-off-by: Dmitry Torokhov

    Jingoo Han
     

16 Feb, 2013

2 commits

  • Make the constants referring to range and bandwidth public so they can
    be used when initializing the platform data fields in the platform code.

    Fix also some comments regarding the unit of measurement to use for the
    range and bandwidth fields, the values are not actually expected to be
    in G or HZ, the code in bma150.c just uses the BMA150_RANGE_xxx and
    BMA150_BW_xxx constants like they are with no translation from actual
    values in G or HZ.

    Signed-off-by: Michael Trimarchi
    Signed-off-by: Antonio Ospite
    Signed-off-by: Dmitry Torokhov

    Michael Trimarchi
     
  • When PM_RUNTIME is not defined, pm_runtime_get_sync() returns 1, see
    include/linux/pm_runtime.c::__pm_runtime_resume(), and the check of the
    return value was overlooking this, in this case bma150_open() would
    return 1 which is not expected by upper layers.

    Maybe the check for != -ENOSYS (Function not implemented) was meant to
    cover this, but pm_runtime_get_sync() does not return this value.

    For now fix the issue locally by checking explicitly for negative return
    values.

    Signed-off-by: Michael Trimarchi
    Signed-off-by: Antonio Ospite
    Signed-off-by: Dmitry Torokhov

    Michael Trimarchi
     

24 Nov, 2012

4 commits


17 Mar, 2012

1 commit


09 Aug, 2011

1 commit