search for: infofram

This is an initial implementation of HDMI 3D mode support for the nouveau kernel driver. It works on all of the hardware that I have available to test at the moment, but I am unsure as to the overall approach taken for setting HDMI InfoFrames, there's no support for g84 or gf119 disps, and the criteria for enabling stereo support for an output seems a bit iffy. The first four patches arrange to set the HDMI InfoFrames for gt215 and gk104 disps, and provide the parsing side of support for g84 and gf119 disps. The fifth patch remo...

HDMI 3D mode support, round two. Revisions include no longer dealing with audio InfoFrames, passing infoframe data to NVKM as bags of bytes rather than as data pre-packed for the hardware, more-normal return value checking for drm_hdmi_*_infoframe_from_display_mode() results, Frame-Packing mode support, more-principled logic for enabling stereo mode support on a connector, and support...

Now that we have mechanism by which to pass mode-dependent HDMI InfoFrames to the low-level hardware driver, it is incumbent upon us to do so. Experimentation on a gt215 device suggests that the Audio InfoFrame is not required here, possibly being provided by the HDA device when necessary (because where else would it come from?). Signed-off-by: Alastair Bridgewater &l...

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Make life easier for drivers by simply passing the connector to drm_hdmi_avi_infoframe_from_display_mode() and drm_hdmi_avi_infoframe_quant_range(). That way drivers don't need to worry about is_hdmi2_sink mess. v2: Make is_hdmi2_sink() return true for sil-sii8620 Adapt to omap/vc4 changes Cc: Alex Deucher <alexander.deucher at amd.com> Cc: "Christian König&quot...

https://bugs.freedesktop.org/show_bug.cgi?id=49061 Bug #: 49061 Summary: HDMI output clipped since commit of 'enable sending of avi/audio infoframes' Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at...

On Tue, 20 Nov 2018, Ville Syrjala <ville.syrjala at linux.intel.com> wrote: > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > Make life easier for drivers by simply passing the connector > to drm_hdmi_avi_infoframe_from_display_mode() and > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > need to worry about is_hdmi2_sink mess. Overall looks about right and nice, Reviewed-by: Jani Nikula <jani.nikula at intel.com> But please do take that with a grain of salt for everything ou...

I have bugzilla'ed a problem with the 3.3 kernel and my 1920x1200 LCD display here: https://bugzilla.redhat.com/show_bug.cgi?id=806091 Since the InfoFrames appear to be confusing my display, I'm looking for a way to disable them. Is it possible to use the override_conntype parameter to make the driver treat the DisplayPort connector as a DVI connector (which would presumably stop it from sending the InfoFrames)? I can't find any documentati...

From: Ville Syrjälä <ville.syrjala at linux.intel.com> Make life easier for drivers by simply passing the connector to drm_hdmi_avi_infoframe_from_display_mode() and drm_hdmi_avi_infoframe_quant_range(). That way drivers don't need to worry about is_hdmi2_sink mess. Cc: Alex Deucher <alexander.deucher at amd.com> Cc: "Christian König" <christian.koenig at amd.com> Cc: "David (ChunMing) Zhou" <Davi...

On Mon, Mar 27, 2017 at 05:57:57PM -0400, Alastair Bridgewater wrote: > HDMI 3D mode support, round two. Revisions include no longer dealing > with audio InfoFrames, passing infoframe data to NVKM as bags of bytes > rather than as data pre-packed for the hardware, more-normal return > value checking for drm_hdmi_*_infoframe_from_display_mode() results, > Frame-Packing mode support, more-principled logic for enabling stereo > mode support on a con...

.... Thanks to Roy Spliet for assistance (mostly background information) in working out what was going on with m->v.blankus. Alastair Bridgewater (10): drm/nouveau: Clean up nv50_head_atomic_check_mode() and fix blankus calculation drm/nouveau: Extend NVKM HDMI power control method to set InfoFrames drm/nouveau: Pass mode-dependent AVI and Vendor HDMI InfoFrames to NVKM drm/nouveau: Add mechanism to convert HDMI InfoFrames to hardware format drm/nouveau: Use supplied HDMI InfoFrames on G84 hardware drm/nouveau: Use supplied HDMI InfoFrames on GT215 hardware drm/nouveau: Use...

Prior to this change, some screen models would display a 2px-large purple line along left screen border, likely to complain about invalid InfoFrame content. The following bug report seems to trigger this issue: https://bugs.freedesktop.org/show_bug.cgi?id=75203 Running mmiotrace on a GTX 650 (GK107) produces the following trace, regardless of which output is used (HDMI-1, DVI-D-1, DVI-D-2), to initialise InfoFrame with blob version 340.32 a...

...rm/bridge/sil-sii8620.c > >>>>> index a6e8f4591e63..0cc293a6ac24 100644 > >>>>> --- a/drivers/gpu/drm/bridge/sil-sii8620.c > >>>>> +++ b/drivers/gpu/drm/bridge/sil-sii8620.c > >>>>> @@ -1104,8 +1104,7 @@ static void sii8620_set_infoframes(struct sii8620 *ctx, > >>>>> int ret; > >>>>> > >>>>> ret = drm_hdmi_avi_infoframe_from_display_mode(&frm.avi, > >>>>> - mode, > >>>>> - true); > >>>>> +...

Hi. (sorry for non-threaded reply, I expected to receive my own "git send-email"-generated post) This patch is an RFC, with at least 3 things to change before it could be committed: - commented-out NV84_DISP_SOR_HDMI_PWR_STATE_ON test: what is this needed for ? I couldn't find an equivalent in my trace, but maybe I just didn't do what is needed to generate these writes -

The nouveau driver, in the Linux 3.7 days, used to try and set the AVI InfoFrame based on the selected display mode. These days, it uses a fixed set of InfoFrames. Start to correct that, by providing a mechanism whereby InfoFrame data may be passed to the NVKM functions that do the actual configuration. At this point, only establish the new parameters and their parsing, don...

...ge/sil-sii8620.c b/drivers/gpu/drm/bridge/sil-sii8620.c > >>> index a6e8f4591e63..0cc293a6ac24 100644 > >>> --- a/drivers/gpu/drm/bridge/sil-sii8620.c > >>> +++ b/drivers/gpu/drm/bridge/sil-sii8620.c > >>> @@ -1104,8 +1104,7 @@ static void sii8620_set_infoframes(struct sii8620 *ctx, > >>> int ret; > >>> > >>> ret = drm_hdmi_avi_infoframe_from_display_mode(&frm.avi, > >>> - mode, > >>> - true); > >>> + NULL, mode); > >>> if (...

...l-sii8620.c >>>>>>> index a6e8f4591e63..0cc293a6ac24 100644 >>>>>>> --- a/drivers/gpu/drm/bridge/sil-sii8620.c >>>>>>> +++ b/drivers/gpu/drm/bridge/sil-sii8620.c >>>>>>> @@ -1104,8 +1104,7 @@ static void sii8620_set_infoframes(struct sii8620 *ctx, >>>>>>> int ret; >>>>>>> >>>>>>> ret = drm_hdmi_avi_infoframe_from_display_mode(&frm.avi, >>>>>>> - mode, >>>>>>> - true); >>>&g...

...;>>>>>> index a6e8f4591e63..0cc293a6ac24 100644 > >>>>>>> --- a/drivers/gpu/drm/bridge/sil-sii8620.c > >>>>>>> +++ b/drivers/gpu/drm/bridge/sil-sii8620.c > >>>>>>> @@ -1104,8 +1104,7 @@ static void sii8620_set_infoframes(struct sii8620 *ctx, > >>>>>>> int ret; > >>>>>>> > >>>>>>> ret = drm_hdmi_avi_infoframe_from_display_mode(&frm.avi, > >>>>>>> - mode, > >>>>>>> -...

...20.c b/drivers/gpu/drm/bridge/sil-sii8620.c >>>>> index a6e8f4591e63..0cc293a6ac24 100644 >>>>> --- a/drivers/gpu/drm/bridge/sil-sii8620.c >>>>> +++ b/drivers/gpu/drm/bridge/sil-sii8620.c >>>>> @@ -1104,8 +1104,7 @@ static void sii8620_set_infoframes(struct sii8620 *ctx, >>>>> int ret; >>>>> >>>>> ret = drm_hdmi_avi_infoframe_from_display_mode(&frm.avi, >>>>> - mode, >>>>> - true); >>>>> + NULL, mode); >&g...

...vember 2018 18:13:42 EET Ville Syrjala wrote: >>>>>>> From: Ville Syrjälä <ville.syrjala at linux.intel.com> >>>>>>> >>>>>>> Make life easier for drivers by simply passing the connector >>>>>>> to drm_hdmi_avi_infoframe_from_display_mode() and >>>>>>> drm_hdmi_avi_infoframe_quant_range(). That way drivers don't >>>>>>> need to worry about is_hdmi2_sink mess. >>>>>> While this is good for display controller drivers, the change isn't >>>&g...

...40:43PM +0200, Jani Nikula wrote: > On Tue, 20 Nov 2018, Ville Syrjala <ville.syrjala at linux.intel.com> wrote: > > From: Ville Syrjälä <ville.syrjala at linux.intel.com> > > > > Make life easier for drivers by simply passing the connector > > to drm_hdmi_avi_infoframe_from_display_mode() and > > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > > need to worry about is_hdmi2_sink mess. > > Overall looks about right and nice, > > Reviewed-by: Jani Nikula <jani.nikula at intel.com> > > But please do take tha...