As per specification.
- Always enable enhanced framing mode.
- Declare training pattern 3 support if core is DP v1.2.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
If an interrupt occurs without a user defined callback, don't invoke the
function.
Otherwise, unexpected behavior will be seen due to running code from 0x0 (NULL).
Prior to this, it was the responsibility of the user to ensure all callbacks for
interrupts were set.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
The interrupt mask and interrupt cause registers are independent. The interrupt
handler has been modified to ignore interrupts that have been masked out.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Added new interrupts, callbacks, and macros related to HDCP (High-bandwidth
Digital Content Protection).
Added new interrupts, callbacks, and macros for an unplug event.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Fixed compilation warnings when using:
-Wall -Wextra
No need for ">=0" assertions on arguments that are of unsigned type.
Removed unused variables.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
The naming of this example is better described as SST with DP159
functionality.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
The programming sequence required by the DP159 retimer has been
added.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Set the reset value for the timer upon initialization.
Use the timer ID as an argument for consistency with the other
device IDs.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Using the DP159 solution, 8 ms needs to be used as the AUX training
interval.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
RX initialization is not dependent on PLL and reset checks.
- Training will not be initiated until the RX is ready.
The clock is transmitted only once the cable is connected.
- This means that the CPLLs will never lock if no cable is plugged
in resulting in DP RX core initialization time out.
Moved core and interrupt mask enables towards end of function.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Reviewed-by: Hyun Kwon <hyun.kwon@xilinx.com>
Issuing a GUID is done internally by topology discovery. The GUID was already
obtained by the LINK_ADDRESS sideband message.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
- Consistency in indentation.
- All definitions values of the same field should (i.e. interrupt status) have
the same number of digits.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Previously, the number of ports was only being set when setting an input port.
If there are multiple input ports, the number of ports wasn't being accurately
reflected.
The user application was required to update the number of ports when setting a
downstream port.
This is now done within the driver.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
When setting the configuration of a port, always keep the port number of the
port structure to the same value as the index of the structure's index in the
port structure array.
This simplifies functions that operate on the port structure since they don't
need to search each port structure in the array for the port number, the port
number is known from the index.
Note: The existence of the port number member in the port structure is required
since the TX populates this structure when receiving LINK_ADDRESS sideband
messages.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
When the upstream device issues an ALLOCATE_PAYLOAD sideband message request,
this table is updated to represent the allocated bandwidth for each stream.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
The "I2C map" terminology is used to refer to a set of I2C entries for a given
port. Each I2C entry contains an I2C address associated with that entry,
alongside a user-defined data structure which is to be pointed to.
This is the mechanism for which the driver allows the RX application to control
what data to be sent for a given I2C address when a REMOTE_I2C_READ is issued
by an upstream device.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
