- Feb 01, 2012
-
-
Federico Vaga authored
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>
-
Federico Vaga authored
Signed-off-by:
-
Federico Vaga authored
The flag ZTI_STATUS is now called ZTI_BUSY and we get a spinlock when we change this flag Signed-off-by:
-
Federico Vaga authored
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:
-
Alessandro Rubini authored
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 authored
Signed-off-by:
-
- Jan 31, 2012
-
-
Alessandro Rubini authored
The argument is a relic of original design and was used incorrectly. Signed-off-by:
-
Alessandro Rubini authored
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 authored
This saves another 0.1 usec for each block lifetime. Signed-off-by:
-
Alessandro Rubini authored
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 authored
Signed-off-by:
-
Alessandro Rubini authored
Signed-off-by:
-
Alessandro Rubini authored
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 authored
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 authored
We introduced -DDEBUG in two makefiles by error. One error each of us. Signed-off-by:
-
- Jan 30, 2012
-
-
Alessandro Rubini authored
Signed-off-by:
-
- Jan 29, 2012
-
-
Alessandro Rubini authored
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 authored
Move the structures needed from user space to their own header. User space can now only include zio.h (for version and name lenghts and zio-user.h). Several files are changed to reflect the new order. Signed-off-by:
-
Alessandro Rubini authored
I always had a hard time understanding ZIO_NAME_OBJ. Since it's only used internally, let it have "LEN" in it's own name. Signed-off-by:
-
- Jan 24, 2012
-
-
Alessandro Rubini authored
The cset needs a spinlock for I/O operations. Locking the whole device seems overdue. The cset and channel need some private data, because they are allocated as arrays (while ti and bi don't need it, as container_of can be used). This adds a device-private pointer to both cset and channel, and a trigger-private pointer to the channel (this is used e.g. by the ldisc demultiplexer, to be committed later). Signed-off-by:
-
Alessandro Rubini authored
This moves zio-dump to the tools directory. The Makefiles are suitable for out-of-kenrel compilation but not for in-kernel compilation, at this point. Signed-off-by:
-
Signed-off-by:
-
A zio object can be enabled or disabled Signed-off-by:
-
The instance are created independently, so you can check if apply it or destroy it. Moreover, instances associated to cset and channel can be changed from sysfs Signed-off-by:
-
Signed-off-by:
-
ZIO check if the declared attrbutes within a device (zdev, cset, chan) are a valid set of attributes. Signed-off-by:
-
When an attribute change, zio copy the new value to the zio_ctrl_attr within the control structure. Signed-off-by:
-
The zio_ctrl_attr structure will be used to store the current value of the zio attributes in use by device and trigger. This is used within zio_control to provide these informations to user space. Signed-off-by:
-
When a trigger fire it is set to STATUS_ON until data_done(); so, one transfer at time is allowed. Signed-off-by:
-
Signed-off-by:
-
Signed-off-by:
-
Each zio object gets its own spinlock Signed-off-by:
-
Signed-off-by:
-
Signed-off-by:
-
Signed-off-by:
-
Alessandro Rubini authored
Signed-off-by:
-
Alessandro Rubini authored
Signed-off-by:
-
- Jan 06, 2012
-
-
Alessandro Rubini authored
Signed-off-by:
-
- Jan 05, 2012
-
-
Federico Vaga authored
Signed-off-by:
-
Federico Vaga authored
(input|output)_cset change returned value: * 0 if the acquisition is already done * -EAGAIN if the acquisition will be completed in the future (must use data_done) * Other error code if needed Signed-off-by:
-
