From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915/sdvo: Fix AVI infoframe TX rate readout
Date: Wed, 10 Apr 2019 13:27:50 +0300 [thread overview]
Message-ID: <20190410102750.GF3888@intel.com> (raw)
In-Reply-To: <155484456468.32659.16193117222663482451@skylake-alporthouse-com>
On Tue, Apr 09, 2019 at 10:16:04PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-04-09 15:40:48)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > The AVI infoframe readout code currently issues a
> > SDVO_CMD_GET_HBUF_TXRATE before SDVO_CMD_SET_HBUF_INDEX, which is
> > not the correct order for these two operations. So far this wasn't
> > a problem since we left the index pointing at the AVI infoframe
> > buffer at the end of the modeset. However once we start to write
> > to other buffers (namely ELD) that is no longer going to be true.
> > Fix up the order so that we always read out the TX rate for the
> > correct buffer.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_sdvo.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo.c
> > index 0e3d91d9ef13..61db07244296 100644
> > --- a/drivers/gpu/drm/i915/intel_sdvo.c
> > +++ b/drivers/gpu/drm/i915/intel_sdvo.c
> > @@ -1001,6 +1001,11 @@ static ssize_t intel_sdvo_read_infoframe(struct intel_sdvo *intel_sdvo,
> > if (av_split < if_index)
> > return 0;
> >
> > + if (!intel_sdvo_set_value(intel_sdvo,
> > + SDVO_CMD_SET_HBUF_INDEX,
> > + set_buf_index, 2))
> > + return -ENXIO;
>
> That is consistent with write_infoframe and makes a modicum of sense.
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Why is the av_split separate from the if_index? What does that mean, at
> some point I might have to read the docs!
av_split specifies how the set of available buffers is split
between video and audio. if_index specifies which buffers the
other commands operate on.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-10 10:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:40 [PATCH 0/7] drm/i915: Fix SDVO HDMI audio Ville Syrjala
2019-04-09 14:40 ` [PATCH 1/7] drm/i915/sdvo: Fix AVI infoframe TX rate readout Ville Syrjala
2019-04-09 21:16 ` Chris Wilson
2019-04-10 10:27 ` Ville Syrjälä [this message]
2019-04-09 14:40 ` [PATCH 2/7] drm/i915/sdvo: Implement proper HDMI audio support for SDVO Ville Syrjala
2019-04-09 20:00 ` Ville Syrjälä
2019-06-06 14:43 ` Imre Deak
2019-04-09 14:40 ` [PATCH 3/7] drm/i915: Rename SDVO_AUDIO_ENABLE to HDMI_AUDIO_ENABLE Ville Syrjala
2019-04-09 21:32 ` Chris Wilson
2019-04-09 14:40 ` [PATCH 4/7] drm/i915/sdvo: Check that we have space for the infoframe Ville Syrjala
2019-04-09 19:46 ` Chris Wilson
2019-04-09 19:59 ` Ville Syrjälä
2019-04-09 21:08 ` Chris Wilson
2019-04-10 17:08 ` [PATCH v2 " Ville Syrjala
2019-04-22 18:37 ` Sripada, Radhakrishna
2019-04-23 14:34 ` Ville Syrjälä
2019-04-23 16:46 ` Sripada, Radhakrishna
2019-04-09 14:40 ` [PATCH 5/7] drm/i915/sdvo: Don't unpack stack garbage Ville Syrjala
2019-04-09 19:37 ` Chris Wilson
2019-04-09 14:40 ` [PATCH 6/7] drm/i915/sdvo: Don't write stack garbage into the hbuf Ville Syrjala
2019-04-09 19:39 ` Chris Wilson
2019-04-09 14:40 ` [PATCH 7/7] drm/i915/sdvo: Actually print the reason why the SDVO command failed Ville Syrjala
2019-04-09 19:44 ` Chris Wilson
2019-04-09 20:35 ` Ville Syrjälä
2019-04-10 17:09 ` [PATCH v2 " Ville Syrjala
2019-04-09 16:26 ` ✓ Fi.CI.BAT: success for drm/i915: Fix SDVO HDMI audio Patchwork
2019-04-10 2:52 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-04-10 19:35 ` ✓ Fi.CI.BAT: success for drm/i915: Fix SDVO HDMI audio (rev3) Patchwork
2019-04-11 5:46 ` ✗ Fi.CI.IGT: failure " Patchwork
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=20190410102750.GF3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).