Signed-off-by: Federico Vaga <federico.vaga@gmail.com>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Federico Vaga <federico.vaga@gmail.com>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

When declared, extended attributes can't be NULL inside the
extended attributes array
Signed-off-by: Federico Vaga <federico.vaga@gmail.com>
Acked-by: Alessandro Rubni <rubini@gnudd.com>

We didn't free the input blocks if dev->input_block() or
buf->store_block() fails.
Signed-off-by: Federico Vaga <federico.vaga@gmail.com>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

From this commit onwards the whole thing compiles and works (from
2.6.34 onwards). We chose to save you from the past history of
internal zio development.

Signed-off by: Federico Vaga <federico.vaga@gmail.com>
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The tools shows how to use control and data, and can work with any
ZIO input channel.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

This is a working driver, with one cset and three channels that return
8-bit data. It is the demonstration that the ZIO abstraction is a good
way to avoid complexity in the low-level drivers.

Signed-off by: Federico Vaga <federico.vaga@gmail.com>
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This trivial trigger simply arms a timer to run zio_fire_trigger()
for a cset with a specified rate.  It is currently the default
trigger, until we have "app-request".
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

The file exports a few functions that can be used by specific buffers
to handle read, poll, release. Write is not supported at this time.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

This is the default buffer: it manages a list of data blocks
(the lenght is fixed at 16 blocks by now) for any device and
any trigger.  The actual file operations in this case are
generic, and live in zio-buf.c (zio-core.ko).
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

These files are the heart of zio-core. The handle all issues of sysfs
and char devices (excluding the file operations.

Signed-off by: Federico Vaga <federico.vaga@gmail.com>
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

These two headers devine the structures and operations for buffers
and trigger. Additionally, zio-buffer.h defines the control structure
and the data block.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off by: Federico Vaga <federico.vaga@gmail.com>

This includes all the sysfs definitions and structures, together with
the main data structures for devices, csets and channels.

Signed-off by: Federico Vaga <federico.vaga@gmail.com>
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off-by: Federico Vaga <federico.vaga@gmail.com>

These files document how ZIO works. They are still subject
to modification while we are writing code, and some information,
for example how devices work, are still missing.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
Signed-off-by: Federico Vaga <federico.vaga@gmail.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>