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>

ZIO uses the device-level spinlock to protect device registers
during access; a buffer or a trigger instance can be assigned to
only one device on ZIO and if they are hardware implemented they
also live on the same perihperals. So we serialize all the
configuration operations on device, trigger and buffer by using
zio_device->lock.

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>

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>
Acked-by: Federico Vaga <federico.vaga@gmail.com>

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

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

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

We don't have file_operations in the trigger since 5e3c6c8b

,
remove the related comment too (we forgot earlier).

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

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

The program receives from the command line the name of a zio
data file and a number of blocks. It retrieves the blocks
and sends them to stdout. It gets zio data using mmap() if
available, otherwise read.

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

This buffer uses vmalloc and allows mmap from user space.  It started
as a copy of buf-kmalloc, so you can diff to change what is needed
to support mmap over a read/write buffer type.

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

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

I used a wrong dev_data in free_irq. Now it works properly on unload.

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

The vmalloc buffer uses the same names for structure (to ease "diff"
users in understanding it) so the slab name can't be the structure name.

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

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

We will have buffers that use the default operations (the majority) and
buffers without file operations for in-kernel activities, like the
input subsystem. In the latter case we want the cdev to refuse being
openend, so NULL is reserved for that case.

Also, add v_op to the buffer, so it can support mmap.

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

If you only read one channel, alloc_block commonly fails (with
byte-oriented buffers; block-oriented ones fails on store_block).
So don't print to the console when it happens.

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

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

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

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

If a trigger instance is busy, so you cannot change the trigger. You
must wait until data_done, or diasable the trigger before.

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

It didn't put the buffer type after the switch. Now it does. Moreover
some internal change within this function

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

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>

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

The flag ZTI_STATUS is now called ZTI_BUSY and we get a spinlock when we
change this flag

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

this also rename the zio class "zio" to "zio-char-devices" to make
the sysfs structure more readable.

On some old version of udev it does not work; it set read/write
permission on every char device.

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

Some buffers count size in blocks, and some in data space.
I need this to size the vmalloc in zio-buf-vmalloc.c

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

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

zio_free_control is needed by external buffers.

zio_alloc_control will be needed by external triggers that don't rely
on zio_fire_trigger(). It will also be needed by in-kernel sources
of output data.

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

This saves another 0.1 usec for each block lifetime.

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

Some of them don't apply any more (we made our choices, or the problem
has been addressed and fixed elsewhere). Some do but I reworded them.
Some still apply unchanged, and are not touched by this patch.

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

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

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

Testing /dev/urandom versus zzero-0-1-data (the random device)
shows this increases performance by 0.1 usecs per block. We
are now just over 0.7 usecs per block on my development PC.

This also introduces zio-core.c with generic stuff. We agree that zio-sys
will become zio-sysfs over time.

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

Conflicts:

	Makefile

Now that the default trigger and default buffer are includes,
the module shoud be called zio.ko. zio-core.c will be the non-sysfs
stuff currently in zio-sys.c

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

We introduced -DDEBUG in two makefiles by error. One error each of us.

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

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

This changes the content of the control structure to use
the new arrangement for attributes, shorter names and the
added fields we proposed. This also changes the minor version number
so user space cannot be confused (it will spit an error instead).

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