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

This patch renames ZIO_CONTROL_SIZE to __ZIO_CONTROL_SIZE and it
introduces the function zio_control_size(chan).

At a future time, the function will return a channel-dependent value,
when we implement TLV to extend the control structure.

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

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

This patch introduces ZIO_RW_PERM and ZIO_RO_PERM, which are used in
all attributes. Prevoously we had write-all for writeable attributes,
now we only allos the owner and the group.

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

This device accepts zero-sized output blocks: it uses the timestamp
in the control to fire an event, which in this case is a printk message.

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>

This has two csets, with one channel each. The first returns timestamps
in the data area, the second channel returns zero-sized blocks, with
the timestamp in the control.

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

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

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

zio-mini is a very simple driver, with no attributes, that can be used
to get accustomed with how ZIO and the ZIO bus work. You can create
as many devices as you want, with as many channels as you want.
Each device has only one input cset, that returns the struct timespec
collected at raw_io() time.

The driver always returns one sample only, even if the trigger
asks for more.

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

The driver supports an output cset that loops to an input cset, and
two output csets of 1 channel each, whose output is returned to two
char devices.  Intended for demonstration and testing.

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

This patch removes the union field priv in the zio_attribute and it
introduces the id field. From our experience, the priv.ptr pointer
is useless; the priv.addr field can be used for every purpose, also
if you have your own private structure.

The new field id replaces the role of priv.addr. It can represent a
register address, a register offset, an index of a vector of private
structure which describe how to gain access to a register, or whatever
can describe uniquely a register (or register field)

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: 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>

This function can be used outside the ZIO core (e.g. AD788x driver). A
driver can be interested to know how many channel are active during an
acquisition to allocate the proper buffer/structure

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

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

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

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

This is more in line with current kernel practices. We do
not use zio_ here because the context is always clear when this
macro is used.

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

The helper zio_trigger_abort() is introduced; it can be used to abort a
data transfer.

The bit flag ZTI_COMPLETING is introduced: if high ZIO is completing the
transfert operation by invokng the data_done() function; if low the
transfer is running or the trigger is waiting for event. If abort() is
called when this glag is high, the functions does nothing.

The helper zio_trigger_data_done() is introduced; insted of call the
data_done() function with cset->ti->t_op->data_done() and manually set
the ZTI_COMPLETING flag, this hellper must be used. If the trigger
operation data_done is not set, then use the __zio_internal_data_done

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

This patch introduces zio_driver and zio_device_id structure,
which are used to define a zio's driver. ZIO uses these
structures to handle the match between devices and drivers
connected on the zio bus.

To make ZIO work on the Linux bus mechanism, ZIO creates two
zio_device structures. The first zio_device is allocated and it is
registered by the module which wants to declare the existence
of a new ZIO device. This first zio_device is only used by
ZIO to match the device with a driver. When the first zio
device matchs with a driver, ZIO creates a new zio device child
of the first one. The new device is filled with all the device
information and sysfs attributes. This second zio device
represents the real device to use; ZIO passes this zio device
as argument to the driver probe function, so the driver can
use the real zio device for its operations.
From the user space point of view, both ZIO devices are
available at /sys/bus/zio/devices/; the first zio device has
the prefix "hwdev-", the second zio device (the real one) has
the prefix "zio-"

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>

Now all the zio objects are handled with the device structure

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>

ad7887 and ad7888 are now handled by the same driver.
The driver requires data only for enabled channels

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

Every device must has the zio attribute "resolution-bits" on any level of
the device hierarchy. Internally, the preferred name for fields
and variables is "nbits".

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

When a device has several input or output csets, we usually want
a different data-transfer function for each of them. Using a function
specific to each cset simplifies things a little.

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 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>

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

(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: 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>

New input cset, at most 8 gpio pins in 1-byte-per-sample.
(Unlikely the previous one, this has been completed and tested)

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

This reverts commit d0515205

.

The input gpio driver is not ready, and it was pushed upstream in error.

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

New input cset, at most 8 gpio pins in 1-byte-per-sample

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

This introduces ZIO_PARAM_TRIGGER(_name)  and ZIO_PARAM_BUFFER(_name)
and uses them in zio-zero.  We'd love most software-driven devices
to use the buffer= and trigger= parameters to override the default, thus
the centralized macros.

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>