linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: linux-iio@vger.kernel.org
Cc: Device-drivers-devel@blackfin.uclinux.org,
	manuel.stahl@iis.fraunhofer.de,
	Jonathan Cameron <jic23@cam.ac.uk>
Subject: [PATCH 00/11] IIO: resolvers - first round of cleanups.
Date: Fri, 30 Sep 2011 11:14:43 +0100	[thread overview]
Message-ID: <1317377694-9001-1-git-send-email-jic23@cam.ac.uk> (raw)

Hi All,

Mostly straight forward, but that change I suggested yesterday
IIO_GYRO -> IIO_ANGL_VEL and in_gyro_x_* -> in_anglvel_x_*
is in here.  I'm interested to hear peoples opinions on that
in particular.

Note the ad2s1210 is still definitely a work in progress.
There are numerous weird and wonderful corners of its abi
a the moment that need sorting out.

Thanks,

Jonathan

Jonathan Cameron (11):
  staging:iio:resolver:ad2s90 fix registration of null pointer
  staging:iio:resolver:ad2s90 ensure name is passed to iio_core.
  stagiong:iio:resolver:ad2s90 chan spec conversion
  staging:iio: rename gyro channels to anglvel
  staging:iio:Documentation gyro -> anglvel updates in attribute names
  staging:iio:resolver:ad2s120x chan spec conversion
  staging:iio:resolver rename ad2s120x ->ad2s1200
  staging:iio:resolver:ad2s1210 ensure iio_dev->name is set
  staging:iio:resolver:ad2s1210 minimal chan spec conversion.
  staging:iio:resolver:ad2s1210 drop raw config register access
  staging:iio:resolver:ad2s1210 cleanup gpio handling.

 drivers/staging/iio/Documentation/sysfs-bus-iio |  108 ++++++------
 drivers/staging/iio/gyro/adis16060_core.c       |    2 +-
 drivers/staging/iio/gyro/adis16080_core.c       |    2 +-
 drivers/staging/iio/gyro/adis16130_core.c       |    2 +-
 drivers/staging/iio/gyro/adis16260_core.c       |    8 +-
 drivers/staging/iio/gyro/adxrs450_core.c        |    4 +-
 drivers/staging/iio/iio.h                       |    2 +-
 drivers/staging/iio/imu/adis16400_core.c        |   22 ++--
 drivers/staging/iio/industrialio-core.c         |    2 +-
 drivers/staging/iio/resolver/Kconfig            |    4 +-
 drivers/staging/iio/resolver/Makefile           |    2 +-
 drivers/staging/iio/resolver/ad2s1200.c         |  187 ++++++++++++++++++++
 drivers/staging/iio/resolver/ad2s120x.c         |  178 -------------------
 drivers/staging/iio/resolver/ad2s1210.c         |  216 +++++++++-------------
 drivers/staging/iio/resolver/ad2s90.c           |   57 +++---
 15 files changed, 382 insertions(+), 414 deletions(-)
 create mode 100644 drivers/staging/iio/resolver/ad2s1200.c
 delete mode 100644 drivers/staging/iio/resolver/ad2s120x.c

-- 
1.7.3.4


             reply	other threads:[~2011-09-30 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 10:14 Jonathan Cameron [this message]
2011-09-30 10:14 ` [PATCH 01/11] staging:iio:resolver:ad2s90 fix registration of null pointer Jonathan Cameron
2011-09-30 10:14 ` [PATCH 02/11] staging:iio:resolver:ad2s90 ensure name is passed to iio_core Jonathan Cameron
2011-09-30 10:14 ` [PATCH 03/11] stagiong:iio:resolver:ad2s90 chan spec conversion Jonathan Cameron
2011-09-30 10:14 ` [PATCH 04/11] staging:iio: rename gyro channels to anglvel Jonathan Cameron
2011-09-30 10:14 ` [PATCH 05/11] staging:iio:Documentation gyro -> anglvel updates in attribute names Jonathan Cameron
2011-09-30 10:14 ` [PATCH 06/11] staging:iio:resolver:ad2s120x chan spec conversion Jonathan Cameron
2011-09-30 10:14 ` [PATCH 07/11] staging:iio:resolver rename ad2s120x ->ad2s1200 Jonathan Cameron
2011-09-30 10:14 ` [PATCH 08/11] staging:iio:resolver:ad2s1210 ensure iio_dev->name is set Jonathan Cameron
2011-09-30 10:14 ` [PATCH 09/11] staging:iio:resolver:ad2s1210 minimal chan spec conversion Jonathan Cameron
2011-09-30 10:14 ` [PATCH 10/11] staging:iio:resolver:ad2s1210 drop raw config register access Jonathan Cameron
2011-09-30 10:14 ` [PATCH 11/11] staging:iio:resolver:ad2s1210 cleanup gpio handling Jonathan Cameron
2011-10-05  6:58 ` [PATCH 00/11] IIO: resolvers - first round of cleanups Hennerich, Michael
2011-10-05 14:34   ` Jonathan Cameron

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=1317377694-9001-1-git-send-email-jic23@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=manuel.stahl@iis.fraunhofer.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).