From: Peter Meerwald <pmeerw@pmeerw.net>
To: linux-iio@vger.kernel.org
Subject: [PATCH 0/6] some staging:iio:access:sca3000 cleanup
Date: Mon, 13 Jan 2014 22:16:56 +0100 [thread overview]
Message-ID: <1389647817-31320-1-git-send-email-pmeerw@pmeerw.net> (raw)
Hi,
sca3000 seems to be broken, esp. for the chip variant that supports
temperature (no event_attribute_group, no channels at all registered,
this variant seem to be ... not popular :)
this series cleans kerneldoc and comments (patches 1, 2), adds the
event_attribute_group for the temp_output case (patch 3), registers channels
for the temp_output case (patch 4), uses IIO_TEMP instead of DEV_ATTR_TEMP
(patch 5), and cleans sca3000.h
I'm not sure if it is worth cleaning up this old sensor
driver, but still...
my motivation was to get rid of DEV_ATTR_TEMP which is only used in staging by
accel/sca3000 and meter/ade7* and superceeded (?) by IIO_TEMP
ciao, p.
Peter Meerwald (6):
staging:iio:accel:sca3000: Fix kerneldoc
staging:iio:accel:sca3000: Fix format of comments
staging:iio:accel:sca3000: Event_attribute_group seems to be missing
for _info_with_temp
staging:iio:accel:sca3000: Channels missing in temp_output case
staging:iio:accel:sca3000: Move temperature attribute to channels
staging:iio:accel:sca3000: Cleanup sca3000.h
drivers/staging/iio/accel/sca3000.h | 26 +++--
drivers/staging/iio/accel/sca3000_core.c | 172 +++++++++++++------------------
2 files changed, 90 insertions(+), 108 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-01-13 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 21:16 Peter Meerwald [this message]
2014-01-13 21:16 ` [PATCH 1/6] staging:iio:accel:sca3000: Fix kerneldoc Peter Meerwald
2014-01-18 11:05 ` 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=1389647817-31320-1-git-send-email-pmeerw@pmeerw.net \
--to=pmeerw@pmeerw.net \
--cc=linux-iio@vger.kernel.org \
/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).