From: Thierry Reding <thierry.reding@gmail.com>
To: Jose Abreu <Jose.Abreu@synopsys.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 3/3] drm/edid: Implement SCDC Read Request capability detection
Date: Mon, 5 Dec 2016 12:14:56 +0100 [thread overview]
Message-ID: <20161205111456.GD19891@ulmo.ba.sec> (raw)
In-Reply-To: <2c9513c5-2b71-e786-f202-eb1acc027578@synopsys.com>
[-- Attachment #1.1: Type: text/plain, Size: 3904 bytes --]
On Mon, Dec 05, 2016 at 11:06:15AM +0000, Jose Abreu wrote:
> Hi Thierry,
>
>
> Do you think while you are at it you could implement a
> set_scrambling() callback? It should be pretty straight forward:
> you read the SCDC_TMDS_CONFIG reg, do a mask, and then write it
> again.
>
>
> I think this is an important feature that we should have.
Yeah, agreed. I was actually thinking about going one step further and
provide more of the polling functionality as a helper. Even if we have
accessors that wrap the low-level functionality, most drivers would
still have to provide their own delayed workqueue to deal with sinks
(or sources) that don't support read requests. Having this in standard
helpers would help reduce the boilerplate a lot further.
Does your hardware by any chance support read requests on SCDC? It'd be
interesting to see how that works in practice. Unfortunately Tegra does
not seem to support it.
Thierry
> On 02-12-2016 19:24, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > Sinks that support SCDC can optionally have the capability to initiate
> > read requests, which are a mechanism by which a sink can notify its
> > source that it should read the Update Flags. If either the sink or the
> > source are not Read Request capable, polling of the Update Flags shall
> > be employed.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - new patch
> >
> > drivers/gpu/drm/drm_edid.c | 36 ++++++++++++++++++++++++++++++++++++
> > include/drm/drm_edid.h | 1 +
> > 2 files changed, 37 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > index 369961597ee5..8211cce3e09e 100644
> > --- a/drivers/gpu/drm/drm_edid.c
> > +++ b/drivers/gpu/drm/drm_edid.c
> > @@ -3736,6 +3736,42 @@ bool drm_detect_hdmi_scdc(struct edid *edid)
> > EXPORT_SYMBOL(drm_detect_hdmi_scdc);
> >
> > /**
> > + * drm_detect_hdmi_scdc_rr_capable - detect whether an HDMI sink is capable of
> > + * initiating an SCDC Read Request
> > + * @edid: sink EDID information
> > + *
> > + * Parse the CEA extension according to CEA-861-B to find an HF-VSDB as
> > + * defined in HDMI 2.0, section 10.3.2 "HDMI Forum Vendor Specific Data
> > + * Block" and checks if the RR_Capable bit (bit 6 of byte 6) is set.
> > + *
> > + * Returns:
> > + * True if the sink is capable of initiating an SCDC Read Request, false
> > + * otherwise.
> > + */
> > +bool drm_detect_hdmi_scdc_rr_capable(struct edid *edid)
> > +{
> > + unsigned int start, end, i;
> > + const u8 *cea;
> > +
> > + cea = drm_find_cea_extension(edid);
> > + if (!cea)
> > + return false;
> > +
> > + if (cea_db_offsets(cea, &start, &end))
> > + return false;
> > +
> > + for_each_cea_db(cea, i, start, end) {
> > + if (cea_db_is_hdmi_forum_vsdb(&cea[i])) {
> > + if (cea[i + 6] & 0x40)
> > + return true;
> > + }
> > + }
> > +
> > + return false;
> > +}
> > +EXPORT_SYMBOL(drm_detect_hdmi_scdc_rr_capable);
> > +
> > +/**
> > * drm_detect_monitor_audio - check monitor audio capability
> > * @edid: EDID block to scan
> > *
> > diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
> > index 7ea7e90846d8..d1c29586035e 100644
> > --- a/include/drm/drm_edid.h
> > +++ b/include/drm/drm_edid.h
> > @@ -441,6 +441,7 @@ u8 drm_match_cea_mode(const struct drm_display_mode *to_match);
> > enum hdmi_picture_aspect drm_get_cea_aspect_ratio(const u8 video_code);
> > bool drm_detect_hdmi_monitor(struct edid *edid);
> > bool drm_detect_hdmi_scdc(struct edid *edid);
> > +bool drm_detect_hdmi_scdc_rr_capable(struct edid *edid);
> > bool drm_detect_monitor_audio(struct edid *edid);
> > bool drm_rgb_quant_range_selectable(struct edid *edid);
> > int drm_add_modes_noedid(struct drm_connector *connector,
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-05 11:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 19:24 [PATCH v2 1/3] drm: Add SCDC helpers Thierry Reding
2016-12-02 19:24 ` [PATCH v2 2/3] drm/edid: Implement SCDC support detection Thierry Reding
2016-12-03 4:35 ` Sharma, Shashank
2016-12-05 7:57 ` Thierry Reding
2016-12-05 8:16 ` Daniel Vetter
2016-12-05 11:11 ` Thierry Reding
2016-12-05 13:35 ` Ville Syrjälä
2016-12-05 16:21 ` Daniel Vetter
2016-12-05 17:11 ` Thierry Reding
2016-12-06 8:19 ` Daniel Vetter
2016-12-07 19:23 ` Jani Nikula
2016-12-19 8:15 ` Sharma, Shashank
2016-12-02 19:24 ` [PATCH v2 3/3] drm/edid: Implement SCDC Read Request capability detection Thierry Reding
2016-12-05 11:06 ` Jose Abreu
2016-12-05 11:14 ` Thierry Reding [this message]
2016-12-05 14:19 ` Jose Abreu
2016-12-05 16:37 ` Thierry Reding
2016-12-06 8:23 ` Daniel Vetter
2016-12-06 10:32 ` Jose Abreu
2016-12-05 10:12 ` [PATCH v2 1/3] drm: Add SCDC helpers Jose Abreu
2016-12-05 11:16 ` Thierry Reding
2016-12-05 13:31 ` Ville Syrjälä
2016-12-05 14:10 ` Jose Abreu
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=20161205111456.GD19891@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=Jose.Abreu@synopsys.com \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.