From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, manuel.stahl@iis.fraunhofer.de,
jonathan.kunkee@gmail.com, michael.hennerich@analog.com
Subject: Re: [PATCH 0/3 V2] staging:iio:Documentation via dummy driver
Date: Fri, 30 Sep 2011 10:54:08 +0100 [thread overview]
Message-ID: <4E8591C0.7000009@cam.ac.uk> (raw)
In-Reply-To: <1316534313-20212-1-git-send-email-jic23@cam.ac.uk>
Only feedback on this version was generally positive (thanks Maxime).
Manuel, have you had a chance to look at this? I'd like to push it
on fairly soon as rumour says there is a rapidly approaching merge
window.
Jonathan
>
> This has v2 of the dummy driver introduction to start with,
> main changes are responses to Manuels review and a kernel doc
> fixes (as I remembered the format wrong whilst writing the
> original code - oops).
>
> The second patch is somewhat evil in that it uses an additional
> helper module purely to fake event 'interupts'. This is the best
> option I have come up with for how to write a 'standard' looking
> driver that will work without hardware. It's hacky, but I don't
> really want to spend much time on it if it will simply work.
>
> The code in the actual dummy driver is pretty simple and standard.
> Note I have glossed over having a top half to the interrupt as
> the evgen driver can't run one as currently stands. We talked
> a while ago about a workaround for that in the core, but nothing
> is in place as yet.
>
> The third patch puts basic example buffered support in place.
> I haven't provided a trigger because that would require either
> extending the nasty evgen module, or writing another.
>
> Whilst it is decidely 'unusual' we do have a hardware free trigger
> in the iio-trig-sysfs. I'd not advise people look at that one
> to get an idea of how a normal one works though.
>
> So at the end of this, the weak point is the lack of an example
> trigger, but those vary so much anyway I inclined to tell people
> to look for a driver that happens to do roughly what their hardware
> needs and copy that!
>
> What do people think?
>
> I propose to drop the 3 files I moaned about the other day from
> the documentation directory in favour of a short description
> of what this driver does but only once this is in place.
>
> Thanks,
>
> Jonathan
>
> p.s. found a few bugs in the test prog, so I'll send a series
> out cleaning those up soonish.
>
> Jonathan Cameron (3):
> staging:iio:Documentation Simple dummy driver to explain the basics
> staging:iio:dummy Add event support + fake event generator
> staging:iio:dummy Add buffered reading support
>
> drivers/staging/iio/Kconfig | 27 ++
> drivers/staging/iio/Makefile | 7 +
> drivers/staging/iio/iio_core.h | 6 +-
> drivers/staging/iio/iio_dummy_evgen.c | 217 ++++++++++
> drivers/staging/iio/iio_dummy_evgen.h | 2 +
> drivers/staging/iio/iio_simple_dummy.c | 540 +++++++++++++++++++++++++
> drivers/staging/iio/iio_simple_dummy.h | 108 +++++
> drivers/staging/iio/iio_simple_dummy_buffer.c | 206 ++++++++++
> drivers/staging/iio/iio_simple_dummy_events.c | 190 +++++++++
> 9 files changed, 1300 insertions(+), 3 deletions(-)
> create mode 100644 drivers/staging/iio/iio_dummy_evgen.c
> create mode 100644 drivers/staging/iio/iio_dummy_evgen.h
> create mode 100644 drivers/staging/iio/iio_simple_dummy.c
> create mode 100644 drivers/staging/iio/iio_simple_dummy.h
> create mode 100644 drivers/staging/iio/iio_simple_dummy_buffer.c
> create mode 100644 drivers/staging/iio/iio_simple_dummy_events.c
>
prev parent reply other threads:[~2011-09-30 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 15:58 [PATCH 0/3 V2] staging:iio:Documentation via dummy driver Jonathan Cameron
2011-09-20 15:58 ` [PATCH 1/3] staging:iio:Documentation Simple dummy driver to explain the basics Jonathan Cameron
2011-09-20 15:58 ` [PATCH 2/3] staging:iio:dummy Add event support + fake event generator Jonathan Cameron
2011-09-21 9:59 ` Jonathan Cameron
2011-09-20 15:58 ` [PATCH 3/3] staging:iio:dummy Add buffered reading support Jonathan Cameron
2011-09-27 10:54 ` [PATCH 0/3 V2] staging:iio:Documentation via dummy driver Jonathan Cameron
2011-09-30 9:54 ` Jonathan Cameron [this message]
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=4E8591C0.7000009@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=jonathan.kunkee@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=michael.hennerich@analog.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 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).