Lines Matching refs:Counter

4 Generic Counter Interface
10 Counter devices are prevalent among a diverse spectrum of industries.
15 Generic Counter interface enables drivers to support and expose a common
21 Counter devices can vary greatly in design, but regardless of whether
25 the Generic Counter interface.
45 When the Signal data is available for user access, the Generic Counter
64 count data. The Generic Counter interface provides the following
83 context of the Generic Counter interface, a counter consists of Counts
94 Counter interface represents the count data as a natural number.
97 for the count data. The Generic Counter interface provides the following
229 Driver authors may utilize the Generic Counter interface in their code
247 Counter Signals via counter_signal structures. These Signals should
249 allocated counter_device structure before the Counter is registered to
252 Counter Counts may be allocated via counter_count structures, and
253 respective Counter Signal associations (Synapses) made via
258 before the Counter is registered to the system.
282 the provided macros for standard Counter subsystem attributes in order
345 Counter drivers pass and take data natively (i.e. ``u8``, ``u64``, etc.)
348 counter drivers, and enables a Generic Counter chrdev interface via a
353 registered to the Counter core component for use by the Counter
359                         | Counter device driver      |
370                         | Counter core         |
385         | Counter sysfs      |          | Counter chrdev      |
388         | standard Counter   |          | standard Counter    |
392 Thereafter, data can be transferred directly between the Counter device
393 driver and Counter userspace interface::
398                         / Counter device       \
409                         | Counter device driver      |
425         | Counter sysfs      |          | Counter chrdev      |
428         | standard Counter   |          | standard Counter    |
455 Counter device driver
460 Counter core
465 Counter sysfs
467 Translates counter data to the standard Counter sysfs interface format
471 for a detailed breakdown of the available Generic Counter interface
474 Counter chrdev
476 Translates Counter events to the standard Counter character device; data
477 is transferred via standard character device read calls, while Counter
483 Several sysfs attributes are generated by the Generic Counter interface,
487 on each Generic Counter interface sysfs attribute.
490 the Generic Counter paradigm Counts, Signals, and Synapses of respective
493 Counter Character Device
496 Counter character device nodes are created under the ``/dev`` directory
498 Defines for the standard Counter data types are exposed via the
501 Counter events
503 Counter device drivers can support Counter events by utilizing the
511 called, the Counter data associated with the respective event is
515 Counter events can be configured by users to report various Counter
516 data of interest. This can be conceptualized as a list of Counter
544 Userspace applications can configure Counter events via ioctl operations
545 on the Counter character device node. There following ioctl codes are
554 To configure events to gather Counter data, users first populate a
556 and the information for the desired Counter component from which to
560 Note that an event can be watched without gathering Counter data by
562 ``COUNTER_COMPONENT_NONE``. With this configuration the Counter
567 The ``COUNTER_ADD_WATCH_IOCTL`` command will buffer these Counter
569 may be used to activate these Counter watches.
572 calling ``poll`` first) on the Counter character device node to retrieve