From: Jani Nikula <jani.nikula@intel.com>
To: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/dp: there is no audio on port A on non-DDI platforms
Date: Tue, 05 May 2015 12:09:26 +0300 [thread overview]
Message-ID: <877fsn8k6x.fsf@intel.com> (raw)
In-Reply-To: <554855B4.2080808@intel.com>
On Tue, 05 May 2015, Sivakumar Thulasimani <sivakumar.thulasimani@intel.com> wrote:
> On 5/4/2015 7:50 PM, Jani Nikula wrote:
>> The eDP port A register on PCH split platforms has a slightly different
>> register layout from the other ports, with bit 6 being either alternate
>> scrambler reset or reserved, depending on the generation. Our
>> misinterpretation of the bit as audio has lead to warnings.
>>
>> Fix this by not enabling audio on port A on non-DDI platforms. The check
>> could be made more specific, but this corresponds to the audio codec
>> enabling code which emits the warning for port A.
> shouldn't we disable audio for eDP on all platforms , including DDI ones ?
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=89958
>> Reported-and-tested-by: Chris Bainbridge <chris.bainbridge@gmail.com>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 937ba31d8dde..fa71fb4d6542 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -1355,7 +1355,8 @@ intel_dp_compute_config(struct intel_encoder *encoder,
>>
>> pipe_config->has_dp_encoder = true;
>> pipe_config->has_drrs = false;
>> - pipe_config->has_audio = intel_dp->has_audio;
>> + if (HAS_DDI(dev) || port != PORT_A)
>> + pipe_config->has_audio = intel_dp->has_audio;
>>
> this still enables audio for PORT_A on for HSW/BDW/etc . the following
> is better IMO
>
> + if (!is_edp(encoder))
> + pipe_config->has_audio = intel_dp->has_audio;
I wanted the check to match what's in intel_audio.c for these
platforms. And those only need the pipe.
Perhaps it's a theoretical question, but is it impossible for edp to
have audio?
Jani.
>
>
>
> --
> regards,
> Sivakumar
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-05 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 14:20 [PATCH 1/2] drm/i915/dp: there is no audio on port A on non-DDI platforms Jani Nikula
2015-05-04 14:20 ` [PATCH 2/2] drm/i915/audio: do not mess with audio registers if port is invalid Jani Nikula
2015-05-04 20:45 ` shuang.he
2015-05-05 5:33 ` Sivakumar Thulasimani
2015-05-06 11:11 ` Daniel Vetter
2015-05-05 5:31 ` [PATCH 1/2] drm/i915/dp: there is no audio on port A on non-DDI platforms Sivakumar Thulasimani
2015-05-05 9:09 ` Jani Nikula [this message]
2015-05-05 12:18 ` Sivakumar Thulasimani
2015-05-05 13:32 ` Jani Nikula
2015-05-05 13:38 ` Sivakumar Thulasimani
2015-05-05 13:43 ` Sivakumar Thulasimani
2015-05-06 9:30 ` Jani Nikula
2015-05-06 11:11 ` Daniel Vetter
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=877fsn8k6x.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sivakumar.thulasimani@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