3.2.2. Additional classes for side-band signals

The following classes and interfaces are defined to model side-band signals. There are variants with or without get_state() access function to passively query the current state of the signal:

signal_export_base<>

This is the Signal export base class.

signal_from_sc_bridge<>

This is the generic bridge module from sc_signal<> to Signal.

signal_if<>

This is the user-layer interface for Signal.

signal_master_port<>

This is the port to be instantiated on the Signal master side.

signal_request<>

This is the Signal request type.

signal_response<>

This is the Signal response type.

signal_slave_export<>

This is the export to be instantiated on the Signal slave side.

signal_slave_base<>

This is the base class for Signal slave modules.

signal_state_if<>

This is the user-layer interface for SignalState.

signal_state_nonblocking_transport_if<>

This is the core non-blocking transport interface for SignalState.

signal_state_to_sc_bridge<>

This is a generic bridge module from SignalState to sc_signal<>.

signal_state_from_sc_bridge<>

This is the generic bridge module from sc_signal<> to SignalState.

signal_state_master_port<>

This is the port to be instantiated on the SignalState master side.

signal_state_slave_base<>

This is the base class for SignalState slave modules.

signal_state_slave_export<>

This is the export to be instantiated on the SignalState slave side.

signal_to_sc_bridge<>

This is the generic bridge module between Signal and sc_signal<>.

signal_nonblocking_transport_if<>

This is the core non-blocking transport interface for the Signal.

The templated Signal classes and interfaces have a STATE parameter.

Copyright © 2009-2013 ARM. All rights reserved.ARM DUI 0455H
Non-ConfidentialID112213