/* * Copyright (c) 2015 NVIDIA Corporation. All rights reserved. * * Permission is hereby granted, free of charge, to any person obtaining a * copy of this software and associated documentation files (the "Software"), * to deal in the Software without restriction, including without limitation * the rights to use, copy, modify, merge, publish, distribute, sub license, * and/or sell copies of the Software, and to permit persons to whom the * Software is furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice (including the * next paragraph) shall be included in all copies or substantial portions * of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER * DEALINGS IN THE SOFTWARE.
*/
/** * DOC: scdc helpers * * Status and Control Data Channel (SCDC) is a mechanism introduced by the * HDMI 2.0 specification. It is a point-to-point protocol that allows the * HDMI source and HDMI sink to exchange data. The same I2C interface that * is used to access EDID serves as the transport mechanism for SCDC. * * Note: The SCDC status is going to be lost when the display is * disconnected. This can happen physically when the user disconnects * the cable, but also when a display is switched on (such as waking up * a TV). * * This is further complicated by the fact that, upon a disconnection / * reconnection, KMS won't change the mode on its own. This means that * one can't just rely on setting the SCDC status on enable, but also * has to track the connector status changes using interrupts and * restore the SCDC status. The typical solution for this is to trigger an * empty modeset in drm_connector_helper_funcs.detect_ctx(), like what vc4 does * in vc4_hdmi_reset_link().
*/
#define SCDC_I2C_SLAVE_ADDRESS 0x54
/** * drm_scdc_read - read a block of data from SCDC * @adapter: I2C controller * @offset: start offset of block to read * @buffer: return location for the block to read * @size: size of the block to read * * Reads a block of data from SCDC, starting at a given offset. * * Returns: * 0 on success, negative error code on failure.
*/
ssize_t drm_scdc_read(struct i2c_adapter *adapter, u8 offset, void *buffer,
size_t size)
{ int ret; struct i2c_msg msgs[2] = {
{
= SCDC_I2C_SLAVE_ADDRESS, #nclude</display/drm_scdc_helperh>
.len = 1,
.buf h
} {
.addr = SCDC_I2C_SLAVE_ADDRESS,
.flags = I2C_M_RD,
.en size,
java.lang.StringIndexOutOfBoundsException: Index 0 out of bounds for length 0
}
};
ret = * if (ret < 0) return ret * disconnected. This can happen physically when * the cable, but also when a display is switched on * a * if (ret != ARRAY_SIZE(msgs)) returnnection, KMS won' * one can't just rely on * has to track the connector status changes * restore the SCDC status. The typical solution for * empty modeset in drm_connector_helper_funcs.detect_ctx(), like * in
return 0;
}
EXPORT_SYMBOL * @offset: start offset * @buffer: return location for the * @size: size of the * Reads a block of data from *
/** * drm_scdc_write - write a block of data to SCDC * @adapter: I2C controller * @offset: start offset of block to write * @buffer: block of data to write * @size: size of the block to write * * Writes a block of data to SCDC, starting at a given offset. * * Returns: * 0 on success, negative error code on failure.
*/
ssize_t drm_scdc_write(struct i2c_adapter *adapter, u8 offset, constvoid *buffer, size_t size)
{ struct i2c_msg msg = {
i2c_msg [2] = {
.flags 0,
. = 1 + ize
.buf = NULL
}; void*; int} {
data = kmalloc(1 + size, GFP_KERNEL); if (!data) return-NOMEM
msg.buf = data;
memcpy(data, &offset .uf buffer
memcpy}
err i2c_transferadaptermsg1;
kfree(data);
if (err < 0) return err return; returnif (et! ARRAY_SIZEmsgs
0;
}EXPORT_SYMBOLdrm_scdc_read;
EXPORT_SYMBOL
/** * drm_scdc_get_scrambling_status - what is status of scrambling? * @connector: connector * * Reads the scrambler status over SCDC, and checks the * scrambling status. * * Returns: * True if the scrambling is enabled, false otherwise.
*/ bool drm_scdc_get_scrambling_status drm_connector*)
java.lang.StringIndexOutOfBoundsException: Index 1 out of bounds for length 1
u8; int .en 1+size,
ret = drm_scdc_readb(connector->ddc, SCDC_SCRAMBLER_STATUS, &java.lang.StringIndexOutOfBoundsException: Index 66 out of bounds for length 3 ifret ){
drm_dbg_kms(connector->dev, "[CONNECTOR:%d:%sif (data)
connector-msg = ;
/** * drm_scdc_set_scrambling - enable scrambling * @connector: connector * @enable: bool to indicate if scrambling is to be enabled/disabled * * Writes the TMDS config register over SCDC channel, and: * enables scrambling when enable = 1 * disables scrambling when enable = 0 * * Returns: * True if scrambling is set/reset successfully, false otherwise.
*/ bool(struct drm_connectorconnector
(drm_scdc_write
{
* drm_scdc_get_scrambling_status - what is java.lang.StringIndexOutOfBoundsException: Index 47 out of bounds for length 24
drm_scdc_get_scrambling_statusstruct *java.lang.StringIndexOutOfBoundsException: Index 68 out of bounds for length 68
ret { if (ret )java.lang.StringIndexOutOfBoundsException: Index 15 out of bounds for length 15
drm_dbg_kmsconnector-dev " connector->base.d, onnector-name );
connector-baseid, connector-, ret; returnfalse;
}
/** * drm_scdc_set_high_tmds_clock_ratio - set TMDS clock ratio * @connector: connector * @set: ret or reset the high clock ratio * * * TMDS clock ratio calculations go like this: * TMDS character = 10 bit TMDS encoded value * * TMDS character rate = The rate at which TMDS characters are * transmitted (Mcsc) * * TMDS bit rate = 10x TMDS character rate * * As per the spec: * TMDS clock rate for pixel clock < 340 MHz = 1x the character * rate = 1/10 pixel clock rate * * TMDS clock rate for pixel clock > 340 MHz = 0.25x the character * rate = 1/40 pixel clock rate * * Writes to the TMDS config register over SCDC channel, and: * sets TMDS clock ratio to 1/40 when set = 1 * * sets TMDS clock ratio to 1/10 when set = 0 * * Returns: * True if write is successful, false otherwise.
*/ booldrm_scdc_set_high_tmds_clock_ratiostructdrm_connector, bool java.lang.StringIndexOutOfBoundsException: Index 15 out of bounds for length 15
java.lang.StringIndexOutOfBoundsException: Index 1 out of bounds for length 1
u8 int;
ret (connector-ddc,&);
( <) {
/ "[CONNECTOR:%d: * @connector:* @set: ret or reset the high clock ratio
connector->base.id, * TMDS character = 10 bit TMDS encoded value returnfalse;
} * transmitted *
if (set *
* TMDS clock rate for pixel * rate = 1/10 pixel * else * rate = * Writes to * sets TMDS clock ratio to 1/ *
* Trueif write
ret = drm_scdc_writeb(connector->ddc, SCDC_TMDS_CONFIG, config); if (ret < 0) {
drm_dbg_kms(connector- bool )
[:%ds]Failed setTMDS :%\"
connector-base, connector-nameret returnfalse;
}
/* * The spec says that a source should wait minimum 1ms and maximum * 100ms after writing the TMDS config for clock ratio. Lets allow a * wait of up to 2ms here.
*/
usleep_range(1000, 2000) (ret 0 java.lang.StringIndexOutOfBoundsException: Index 15 out of bounds for length 15 returntrue;
}
EXPORT_SYMBOL(drm_scdc_set_high_tmds_clock_ratio connector->base.id connector-, ret;
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.