From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Shobhit Kumar <shobhit.kumar@intel.com>
Subject: Re: [PATCH] drm/i915: Correct the variable holding the value for EOT to write
Date: Tue, 03 Feb 2015 16:40:42 +0200 [thread overview]
Message-ID: <87r3u7xdlh.fsf@intel.com> (raw)
In-Reply-To: <1422946055-12255-1-git-send-email-shobhit.kumar@intel.com>
On Tue, 03 Feb 2015, Shobhit Kumar <shobhit.kumar@intel.com> wrote:
> This isuue got introduced in -
>
> commit 24ee0e64909bf7f1953d87d3e1e29d93eafcad73
> Author: Gaurav K Singh <gaurav.k.singh@intel.com>
> Date: Fri Dec 5 14:24:21 2014 +0530
>
> drm/i915: Update the DSI enable path to support dual
>
> Signed-off-by: Shobhit Kumar <shobhit.kumar@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dsi.c b/drivers/gpu/drm/i915/intel_dsi.c
> index ef3df5e..6ce9c45 100644
> --- a/drivers/gpu/drm/i915/intel_dsi.c
> +++ b/drivers/gpu/drm/i915/intel_dsi.c
> @@ -855,7 +855,7 @@ static void intel_dsi_prepare(struct intel_encoder *intel_encoder)
>
>
> /* recovery disables */
> - I915_WRITE(MIPI_EOT_DISABLE(port), val);
> + I915_WRITE(MIPI_EOT_DISABLE(port), tmp);
>
> /* in terms of low power clock */
> I915_WRITE(MIPI_INIT_COUNT(port), intel_dsi->init_count);
> --
> 2.1.0
>
--
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-02-03 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 6:47 [PATCH] drm/i915: Correct the variable holding the value for EOT to write Shobhit Kumar
2015-02-03 9:52 ` shuang.he
2015-02-03 14:40 ` Jani Nikula [this message]
2015-02-03 16:07 ` 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=87r3u7xdlh.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=shobhit.kumar@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