From: "Kumar, Shobhit" <shobhit.kumar@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Imre Deak <imre.deak@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: vlv/chv: fix DSI sideband register accessing
Date: Mon, 02 Jun 2014 19:09:44 +0530 [thread overview]
Message-ID: <538C7EA0.1060200@intel.com> (raw)
In-Reply-To: <87ppj0itwl.fsf@intel.com>
On 5/26/2014 6:22 PM, Jani Nikula wrote:
> On Mon, 19 May 2014, Imre Deak <imre.deak@intel.com> wrote:
>> So far we used the wrong opcodes to access the DSI registers, so the
>> register writes during DSI programming didn't actually succeed and left
>> the registers unchanged. This wasn't a problem for the initial modeset,
>> where the BIOS-programmed values happened to work, but after resuming
>> from s0ix these registers are reset and failing to program them results
>> in a blank screen.
>
> Shobhit, this was already merged, did you have a chance to test it?
>
Sorry just saw this today. Yeah I have pulled this in my test tree and
suspend/resume was working perfect, but then I was not doing display
powergate. In the internal code though S0ix was implemented. I will
double check if the internal code had correct opcodes and somehow wrong
opcodes trickled into intel-gfx. As of now looks okay and works fine for me.
Regards
Shobhit
> Jani.
>
>
>>
>> Signed-off-by: Imre Deak <imre.deak@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_sideband.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_sideband.c b/drivers/gpu/drm/i915/intel_sideband.c
>> index f3909d5..01d841e 100644
>> --- a/drivers/gpu/drm/i915/intel_sideband.c
>> +++ b/drivers/gpu/drm/i915/intel_sideband.c
>> @@ -270,13 +270,13 @@ void intel_sbi_write(struct drm_i915_private *dev_priv, u16 reg, u32 value,
>> u32 vlv_flisdsi_read(struct drm_i915_private *dev_priv, u32 reg)
>> {
>> u32 val = 0;
>> - vlv_sideband_rw(dev_priv, DPIO_DEVFN, IOSF_PORT_FLISDSI, SB_MRD_NP,
>> + vlv_sideband_rw(dev_priv, DPIO_DEVFN, IOSF_PORT_FLISDSI, SB_CRRDDA_NP,
>> reg, &val);
>> return val;
>> }
>>
>> void vlv_flisdsi_write(struct drm_i915_private *dev_priv, u32 reg, u32 val)
>> {
>> - vlv_sideband_rw(dev_priv, DPIO_DEVFN, IOSF_PORT_FLISDSI, SB_MWR_NP,
>> + vlv_sideband_rw(dev_priv, DPIO_DEVFN, IOSF_PORT_FLISDSI, SB_CRWRDA_NP,
>> reg, &val);
>> }
>> --
>> 1.8.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
next prev parent reply other threads:[~2014-06-02 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 8:41 [PATCH 1/2] drm/i915: rename IOSF sideband opcodes according to the spec Imre Deak
2014-05-19 8:41 ` [PATCH 2/2] drm/i915: vlv/chv: fix DSI sideband register accessing Imre Deak
2014-05-19 15:01 ` Jesse Barnes
2014-05-19 15:10 ` Imre Deak
2014-05-19 15:33 ` Jesse Barnes
2014-05-19 15:50 ` Daniel Vetter
2014-05-26 12:52 ` Jani Nikula
2014-06-02 13:39 ` Kumar, Shobhit [this message]
2014-05-19 15:00 ` [PATCH 1/2] drm/i915: rename IOSF sideband opcodes according to the spec Jesse Barnes
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=538C7EA0.1060200@intel.com \
--to=shobhit.kumar@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 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.