From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: jose.abreu@synopsys.com, daniel.vetter@intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm: scrambling support in drm layer
Date: Thu, 2 Feb 2017 11:18:51 +0530 [thread overview]
Message-ID: <b134486c-eb3e-2941-2305-e88c18f72740@intel.com> (raw)
In-Reply-To: <20170201163213.GZ31595@intel.com>
Regards
Shashank
On 2/1/2017 10:02 PM, Ville Syrjälä wrote:
> On Wed, Feb 01, 2017 at 06:14:39PM +0530, Shashank Sharma wrote:
>> HDMI 2.0 spec mandates scrambling for modes with pixel clock higher
>> than 340Mhz. This patch adds few new functions in drm layer for
>> core drivers to enable/disable scrambling.
>>
>> This patch adds:
>> - A function to detect scrambling support parsing HF-VSDB
>> - A function to check scrambling status runtime using SCDC read.
>> - Two functions to enable/disable scrambling using SCDC read/write.
>> - Few new bools to reflect scrambling support and status.
>>
>> Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
>> ---
>> drivers/gpu/drm/drm_edid.c | 131 +++++++++++++++++++++++++++++++++++++++++++-
>> include/drm/drm_connector.h | 24 ++++++++
>> include/drm/drm_edid.h | 6 +-
>> 3 files changed, 159 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
>> index 37902e5..f0d940a 100644
>> --- a/drivers/gpu/drm/drm_edid.c
>> +++ b/drivers/gpu/drm/drm_edid.c
>> @@ -37,6 +37,7 @@
>> #include <drm/drm_edid.h>
>> #include <drm/drm_encoder.h>
>> #include <drm/drm_displayid.h>
>> +#include <drm/drm_scdc_helper.h>
>>
>> #define version_greater(edid, maj, min) \
>> (((edid)->version > (maj)) || \
>> @@ -3814,6 +3815,132 @@ static void drm_detect_hdmi_scdc(struct drm_connector *connector,
>> }
>> }
>>
>> +static void drm_detect_hdmi_scrambling(struct drm_connector *connector,
>> + const u8 *hf_vsdb)
> That names seems off. Should probably be drm_parse_hdmi_forum_vsdb() or
> something.
Actually, unlike the last patch set, we are not parsing the whole
hf_vsdb, but parsing it only for
scrambling status byte (hf_vsdb[5]). But may be I can make it
drm_detect_scrambling_from_hfvsdb
ot something similar. We will have more hf_vsdb parsing for 3d flags,
yuv420_deep_color etc.
>> +{
>> + struct drm_display_info *display = &connector->display_info;
>> + struct drm_hdmi_info *hdmi = &display->hdmi_info;
>> +
>> + /*
>> + * All HDMI 2.0 monitors must support scrambling at rates > 340M.
>> + * And as per the spec, three factors confirm this:
>> + * * Availability of a HF-VSDB block in EDID (check)
>> + * * Non zero Max_TMDS_Char_Rate filed in HF-VSDB
>> + * * SCDC support available
>> + * Lets check it out.
>> + */
>> +
>> + if (hf_vsdb[5]) {
>> + display->max_tmds_clock = hf_vsdb[5] * 5000;
>> + DRM_DEBUG_KMS("HF-VSDB: max TMDS clock %d kHz\n",
>> + display->max_tmds_clock);
> I wonder if we should be a little paranoid and ignore this if it's
> <=340?
Sure, will do it.
>
>> +
>> + if (hdmi->scdc_supported) {
>> + hdmi->scr_info.supported = true;
>> +
>> + /* Few sinks support scrambling for cloks < 340M */
>> + if ((hf_vsdb[6] & 0x8))
>> + hdmi->scr_info.low_clocks = true;
>> + }
>> + }
>> +}
>> +
>> +/**
>> + * drm_check_scrambling_status - what is status of scrambling?
>> + * @adapter: i2c adapter for SCDC channel
>> + *
>> + * Read the scrambler status over SCDC channel, and check the
>> + * scrambling status.
>> + *
>> + * Return: True if the scrambling is enabled, false otherwise.
>> + */
>> +
>> +bool drm_check_scrambling_status(struct i2c_adapter *adapter)
> The name is again a little wonky. And it looks like something that
> should live alognside the SCDC helper stuff.
Yep, Thierry also suggested the same, to move it along with SCDC. Will
do it.
>> +{
>> + u8 status;
>> +
>> + if (drm_scdc_readb(adapter, SCDC_SCRAMBLER_STATUS, &status) < 0) {
>> + DRM_ERROR("Failed to read scrambling status\n");
>> + return false;
>> + }
>> +
>> + status &= SCDC_SCRAMBLING_STATUS;
>> + return status != 0;
> return status & SCDC_SCRAMBLING_STATUS
Sure.
>> +}
>> +
>> +/**
>> + * drm_enable_scrambling - enable scrambling
>> + * @connector: target drm_connector
>> + * @adapter: i2c adapter for SCDC channel
>> + * @force: enable scrambling, even if its already enabled
>> + *
>> + * Write the TMDS config over SCDC channel, and enable scrambling
>> + * Return: True if scrambling is successfully enabled, false otherwise.
>> + */
>> +
>> +bool drm_enable_scrambling(struct drm_connector *connector,
>> + struct i2c_adapter *adapter, bool force)
>> +{
>> + u8 config;
>> + struct drm_hdmi_info *hdmi_info = &connector->display_info.hdmi_info;
>> +
>> + if (hdmi_info->scr_info.status && !force) {
>> + DRM_DEBUG_KMS("Scrambling already enabled\n");
>> + return true;
>> + }
> I don't think we want to track any dynamic state in the display info.
> That belongs to the atomic state stuff.
Hummm, ok.
>
> And the function again looks like something that belongs in the SCDC
> helper.
Agree.
>
> Since the two pieces of infromaton in this registrer are the scramble
> control and the clock ratio, I think we might want to just have one
> function to configure both.
That's a good suggestion, thanks.
- Shashank
>
>> +
>> + if (drm_scdc_readb(adapter, SCDC_TMDS_CONFIG, &config) < 0) {
>> + DRM_ERROR("Failed to read tmds config\n");
>> + return false;
>> + }
>> +
>> + config |= SCDC_SCRAMBLING_ENABLE;
>> +
>> + if (drm_scdc_writeb(adapter, SCDC_TMDS_CONFIG, config) < 0) {
>> + DRM_ERROR("Failed to enable scrambling, write error\n");
>> + return false;
>> + }
>> +
>> + hdmi_info->scr_info.status = drm_check_scrambling_status(adapter);
>> + return hdmi_info->scr_info.status;
>> +}
>> +
>> +/**
>> + * drm_disable_scrambling - disable scrambling
>> + * @connector: target drm_connector
>> + * @adapter: i2c adapter for SCDC channel
>> + * @force: disable scrambling, even if its already disabled
>> + *
>> + * Write the TMDS config over SCDC channel, and disable scrambling
>> + * Return: True if scrambling is successfully disabled, false otherwise.
>> + */
>> +bool drm_disable_scrambling(struct drm_connector *connector,
>> + struct i2c_adapter *adapter, bool force)
>> +{
>> + u8 config;
>> + struct drm_hdmi_info *hdmi_info = &connector->display_info.hdmi_info;
>> +
>> + if (!hdmi_info->scr_info.status && !force) {
>> + DRM_DEBUG_KMS("Scrambling already disabled\n");
>> + return true;
>> + }
>> +
>> + if (drm_scdc_readb(adapter, SCDC_TMDS_CONFIG, &config) < 0) {
>> + DRM_ERROR("Failed to read tmds config\n");
>> + return false;
>> + }
>> +
>> + config &= ~SCDC_SCRAMBLING_ENABLE;
>> +
>> + if (drm_scdc_writeb(adapter, SCDC_TMDS_CONFIG, config) < 0) {
>> + DRM_ERROR("Failed to enable scrambling, write error\n");
>> + return false;
>> + }
>> +
>> + hdmi_info->scr_info.status = drm_check_scrambling_status(adapter);
>> + return !hdmi_info->scr_info.status;
>> +}
>> +
>> static void drm_parse_hdmi_deep_color_info(struct drm_connector *connector,
>> const u8 *hdmi)
>> {
>> @@ -3928,8 +4055,10 @@ static void drm_parse_cea_ext(struct drm_connector *connector,
>>
>> if (cea_db_is_hdmi_vsdb(db))
>> drm_parse_hdmi_vsdb_video(connector, db);
>> - if (cea_db_is_hdmi_forum_vsdb(db))
>> + if (cea_db_is_hdmi_forum_vsdb(db)) {
>> drm_detect_hdmi_scdc(connector, db);
>> + drm_detect_hdmi_scrambling(connector, db);
>> + }
>> }
>> }
>>
>> diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
>> index 2435598..b9735bd 100644
>> --- a/include/drm/drm_connector.h
>> +++ b/include/drm/drm_connector.h
>> @@ -90,6 +90,26 @@ enum subpixel_order {
>>
>> };
>>
>> +
>> +/**
>> + * struct scrambling: sink's scrambling support.
>> + */
>> +struct scrambling {
>> + /**
>> + * @supported: scrambling supported for rates > 340Mhz.
>> + */
>> + bool supported;
>> + /**
>> + * @low_clocks: scrambling supported for rates <= 340Mhz.
>> + */
>> + bool low_clocks;
>> + /**
>> + * @status: scrambling enabled/disabled ?
>> + */
>> + bool status;
>> +};
>> +
>> +
>> /**
>> * struct drm_hdmi_info - runtime data about the connected sink
>> *
>> @@ -108,6 +128,10 @@ struct drm_hdmi_info {
>> * @scdc_rr: sink is capable of generating scdc read request.
>> */
>> bool scdc_rr;
>> + /**
>> + * scr_info: sink's scrambling support and capabilities.
>> + */
>> + struct scrambling scr_info;
>> };
>>
>> /**
>> diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
>> index 43fb0ac..d24c974 100644
>> --- a/include/drm/drm_edid.h
>> +++ b/include/drm/drm_edid.h
>> @@ -462,5 +462,9 @@ void drm_edid_get_monitor_name(struct edid *edid, char *name,
>> struct drm_display_mode *drm_mode_find_dmt(struct drm_device *dev,
>> int hsize, int vsize, int fresh,
>> bool rb);
>> -
>> +bool drm_enable_scrambling(struct drm_connector *connector,
>> + struct i2c_adapter *adapter, bool force);
>> +bool drm_disable_scrambling(struct drm_connector *connector,
>> + struct i2c_adapter *adapter, bool force);
>> +bool drm_check_scrambling_status(struct i2c_adapter *adapter);
>> #endif /* __DRM_EDID_H__ */
>> --
>> 1.9.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-02 5:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 12:44 [PATCH 0/6] HDMI 2.0: Scrambling support in DRM layer Shashank Sharma
2017-02-01 12:44 ` [PATCH 1/6] drm: Add SCDC helpers Shashank Sharma
2017-02-02 11:25 ` Jani Nikula
2017-02-02 11:47 ` Sharma, Shashank
2017-02-01 12:44 ` [PATCH 2/6] drm/edid: check for HF-VSDB block Shashank Sharma
2017-02-01 12:44 ` [PATCH 3/6] drm/edid: detect SCDC support in HF-VSDB Shashank Sharma
2017-02-01 16:10 ` Thierry Reding
2017-02-02 5:28 ` Sharma, Shashank
2017-02-02 18:02 ` Thierry Reding
2017-02-01 16:33 ` Ville Syrjälä
2017-02-02 5:40 ` Sharma, Shashank
2017-02-01 12:44 ` [PATCH 4/6] drm: scrambling support in drm layer Shashank Sharma
2017-02-01 16:32 ` Thierry Reding
2017-02-02 5:38 ` Sharma, Shashank
2017-02-02 18:13 ` Thierry Reding
2017-02-03 4:03 ` Sharma, Shashank
2017-02-01 16:32 ` Ville Syrjälä
2017-02-02 5:48 ` Sharma, Shashank [this message]
2017-02-02 9:51 ` Ville Syrjälä
2017-02-02 10:16 ` Sharma, Shashank
2017-02-02 10:28 ` Ville Syrjälä
2017-02-02 10:35 ` Sharma, Shashank
2017-02-01 19:53 ` Pandiyan, Dhinakaran
2017-02-02 5:55 ` [Intel-gfx] " Sharma, Shashank
2017-02-01 12:44 ` [PATCH 5/6] drm/i915: enable scrambling Shashank Sharma
2017-02-01 16:36 ` Ville Syrjälä
2017-02-02 5:53 ` Sharma, Shashank
2017-02-02 10:02 ` Ville Syrjälä
2017-02-02 10:45 ` Sharma, Shashank
2017-02-02 12:27 ` Ville Syrjälä
2017-02-01 12:44 ` [PATCH 6/6] drm/i915: allow HDMI 2.0 clock rates Shashank Sharma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b134486c-eb3e-2941-2305-e88c18f72740@intel.com \
--to=shashank.sharma@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.abreu@synopsys.com \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox