Using the address cycles defined in onfi parameter page than
hardcoding this value to 5 for read and write operations in
XNandPs_SendCommand API.
Signed-off-by: Shakti Bhatnagar <shaktib@xilinx.com>
Removed the alignment check for the adjacent BD gap as the controller
expects all the BDs are organized in linear order.
Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
Modified to use single BD for both rx and tx for avoiding the
multiple version checks and probabaly create another example
for multiple BD processing.
Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
updated cpu driver to use hsi::format_xparam_name to convert
hierarchical external interface names to valid compilable xparam names
Signed-off-by: Kinjal Pravinbhai Patel <patelki@xilinx.com>
updated intc driver to use hsi::format_xparam_name to convert
hierarchical names in xparam names to compilable names
Signed-off-by: Kinjal Pravinbhai Patel <patelki@xilinx.com>
updated driver to use hsi::utils::format_xparam_name to convert
hierarchical names to valid compilable xparameter names
Signed-off-by: Kinjal Pravinbhai Patel <patelki@xilinx.com>
Color format better describes the represented RGB/YUV444/YUV422/YUV420 formats.
Color space would be YUV/RGB.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
It seems that monitors capable of MST, upon switching to SST mode in the monitor
options menu, respond with NACK when the segment pointer is written.
These same monitors ACK segment pointer writes when running in MST mode.
Tested monitors that are SST only monitors also ACK segment pointer writes.
The issue here is that MST monitors running in SST mode will error out when the
I2C read function is called because the segment pointer is always being written
to 0 (segment pointer is reset), and thus receives a NACK.
This patch prevents this from happening.
From now on, if the user changes the segment pointer, it is up to them to reset
it to 0.
The I2C read will only increment the segment pointer when required to do a read
outside of the base EDID block.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
It seems that monitors capable of MST, upon switching to SST mode in the monitor
options menu, respond with NACK when the segment pointer is written.
These same monitors ACK segment pointer writes when running in MST mode.
Tested monitors that are SST only monitors also ACK segment pointer writes.
The issue here is that MST monitors running in SST mode will error out when the
I2C read function is called because the segment pointer is always being written
to 0 (segment pointer is reset), and thus receives a NACK.
This patch prevents this from happening.
From now on, if the user changes the segment pointer, it is up to them to reset
it to 0.
The I2C read will only increment the segment pointer when required to do a read
outside of the base EDID block.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
In interlaced mode, the vertical total lines for frames 0 and 1 may not
necessarily be equal (off by 1). The pixel clock calculation needs to take this
into account by taking their average.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
This function checks if a video timing with a supplied ID from the video mode
table is interlaced or not.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Removed 25 Hz and 30 Hz refresh rates since they have identical video timings to
the 50 Hz and 60 Hz varients. The 50/60Hz refresh rates take into account both
frames for interlaced.
The common video functions use the 50/60Hz refresh rates and divide by 2 where
needed to get the frame rate for each frame.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
For compliance, training pattern 0 should be written without using a burst write
for voltage swing and pre-emphasis values.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
For compliance purposes, training pattern 0 needs to be sent between
downshifting of lane count and link rates.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Since the RX handler initialization functions assert that the core is of type
RX, the configuration initialization function must be called prior to the
handlers being set.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Functions now assert the core context upon which they operate.
XDp_Tx* functions are meant to be used with the DisplayPort core in the TX mode
of operation.
XDp_Rx* functions are meant to be used with the DisplayPort core in the RX mode
of operation.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
Rather than on the configuration structure pointer.
This makes it cleaner and easier to use as this function is an API function.
Signed-off-by: Andrei-Liviu Simion <andrei.simion@xilinx.com>
