All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Oliver King-Smith <oliverks@elementalsemi.com>,
	linux-iio@vger.kernel.org, Rich.Surprenant@nuvation.com
Subject: Re: Back porting bmg160 driver to 3.10.9 kernel
Date: Sat, 23 May 2015 10:50:08 +0200	[thread overview]
Message-ID: <55603F40.2030709@metafoo.de> (raw)
In-Reply-To: <435F7C92-8E78-4BF9-8477-2032CE54AD04@elementalsemi.com>

On 05/22/2015 08:31 PM, Oliver King-Smith wrote:
> I am trying to back port the bmg160 driver to the 3.10.9 kernel to work on an Android 4.4.x device.
>
> The API for in ii_info has changed quite a bit between the 3.18 and the 3.10 kernel.  So this function won’t compile
>
> static int bmg160_read_event(struct iio_dev *indio_dev,
>                               const struct iio_chan_spec *chan,
>                               enum iio_event_type type,
>                               enum iio_event_direction dir,
>                               enum iio_event_info info,
>                               int *val, int *val2)
> {
>          struct bmg160_data *data = iio_priv(indio_dev);
>
>          *val2 = 0;
>          switch (info) {
>          case IIO_EV_INFO_VALUE:
>                  *val = data->slope_thres & BMG160_SLOPE_THRES_MASK;
>                  break;
>          default:
>                  return -EINVAL;
>          }
>
>          return IIO_VAL_INT;
> }
>
> The 3.10 prototype for this function is
>          int (*read_event_value)(struct iio_dev *indio_dev,
>                                  u64 event_code,
>                                  int *val);
>
> My question is what does IIO_EV_INFO_VALUE map to in the old event_code in the 3.10.9 kernel

Nothing. With the old API events could only have values and no other attributes.

- Lars


  reply	other threads:[~2015-05-23  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 18:31 Back porting bmg160 driver to 3.10.9 kernel Oliver King-Smith
2015-05-23  8:50 ` Lars-Peter Clausen [this message]
2015-05-23 20:10   ` Oliver King-Smith
2015-05-24 20:38     ` Lars-Peter Clausen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55603F40.2030709@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Rich.Surprenant@nuvation.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=oliverks@elementalsemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.