no existing trigger uses the file_operations, and the design
evolved towards a pipeline, where there always is a buffer
exchanging data with the trigger

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

The argument is a relic of original design and was used incorrectly.

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

Randy Dunlap authored 13 years ago and Alessandro Rubini committed 13 years ago

Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
Acked-by: Alessandro Rubini <rubini@gnudd.com>

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

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

Manohar Vanga authored 13 years ago and Alessandro Rubini committed 13 years ago

Signed-off-by: Manohar Vanga <manohar.vanga@cern.ch>

This changes some method and stuff, in order to make all input and
output be cset-based. This solves a number of issues with the previous
setup. Thus, even drivers must be made differentlym abd this fixes
zio-zero accordingly.

As a side effect, we have a data_done method in trigger ops, so the device
can tell when it is done. And the fire_trigger returns void, since it
cannot wait for stuff to be done. See documentation for details.

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

docs for general-cset

Federico Vaga authored 13 years ago and Alessandro Rubini committed 13 years ago

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>