public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Mathai, Minu" <minu.mathai@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Correcting the reg definitions for PORT_DFT
Date: Tue, 9 Jun 2015 15:16:42 +0300	[thread overview]
Message-ID: <20150609121642.GJ5176@intel.com> (raw)
In-Reply-To: <F828B0ED84EBE04889B57CBA706013A31A3ACD77@irsmsx105.ger.corp.intel.com>

On Tue, Jun 09, 2015 at 12:06:36PM +0000, Mathai, Minu wrote:
> The hardware composer test which found the problem with this register definition is used in Android testing and isn't open source. 
> However fixing this register definition will stop potential problems for  future use cases and would reduce the rebase effort for our Android tree.

What are you testing with this register? The register isn't even listed
in any VLV/CHV documentation so I have no idea what you would even do
with it.

> 
> -----Original Message-----
> From: Jani Nikula [mailto:jani.nikula@linux.intel.com] 
> Sent: Monday, June 8, 2015 2:48 PM
> To: Mathai, Minu; Ville Syrjälä
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Correcting the reg definitions for PORT_DFT
> 
> On Mon, 08 Jun 2015, "Mathai, Minu" <minu.mathai@intel.com> wrote:
> > This change is needed for some hardware composer tests in chv.
> 
> As Ville said, this #define is not used by the upstream kernel on byt/chv. Maybe you have some out-of-tree patches using that?
> 
> BR,
> Jani.
> 
> 
> >
> > -----Original Message-----
> > From: Ville Syrjälä [mailto:ville.syrjala@linux.intel.com]
> > Sent: Friday, June 5, 2015 2:08 PM
> > To: Mathai, Minu
> > Cc: intel-gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Correcting the reg 
> > definitions for PORT_DFT
> >
> > On Fri, Jun 05, 2015 at 02:00:24PM +0100, Minu Mathai wrote:
> >> From: Minu <minu.mathai@intel.com>
> >> 
> >> Display CRCs were not readable because the register defintions for 
> >> PORT_DFT_I9XX and PORT_DFT2_G4X were wrong.
> >> MMIO offset needs to be added to these register offsets to fix them.
> >> 
> >> Issue: GMINL-6869
> >> Signed-off-by: Minu Mathai <minu.mathai@intel.com>
> >> ---
> >>  drivers/gpu/drm/i915/i915_reg.h | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >> 
> >> diff --git a/drivers/gpu/drm/i915/i915_reg.h 
> >> b/drivers/gpu/drm/i915/i915_reg.h index 7213224..c327c7c 100644
> >> --- a/drivers/gpu/drm/i915/i915_reg.h
> >> +++ b/drivers/gpu/drm/i915/i915_reg.h
> >> @@ -3193,7 +3193,7 @@ enum skl_disp_power_wells {
> >>  #define PCH_HDMIC	0xe1150
> >>  #define PCH_HDMID	0xe1160
> >>  
> >> -#define PORT_DFT_I9XX				0x61150
> >> +#define PORT_DFT_I9XX				(dev_priv->info.display_mmio_offset + 0x61150)
> >
> > PORT_DFT_I9XX isn't used on VLV/CHV, so this doesn't change anything.
> >
> >
> >>  #define   DC_BALANCE_RESET			(1 << 25)
> >>  #define PORT_DFT2_G4X		(dev_priv->info.display_mmio_offset + 0x61154)
> >>  #define   DC_BALANCE_RESET_VLV			(1 << 31)
> >> --
> >> 1.9.1
> >> 
> >> ---------------------------------------------------------------------
> >> Intel Corporation (UK) Limited
> >> Registered No. 1134945 (England)
> >> Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47
> >> 
> >> This e-mail and any attachments may contain confidential material for 
> >> the sole use of the intended recipient(s). Any review or distribution 
> >> by others is strictly prohibited. If you are not the intended 
> >> recipient, please contact the sender and delete all copies.
> >> 
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> > --
> > Ville Syrjälä
> > Intel OTC
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> --
> Jani Nikula, Intel Open Source Technology Center

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-09 12:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 13:00 [PATCH] drm/i915: Correcting the reg definitions for PORT_DFT Minu Mathai
2015-06-05 13:08 ` Ville Syrjälä
2015-06-08 13:23   ` Mathai, Minu
2015-06-08 13:48     ` Jani Nikula
2015-06-09 12:06       ` Mathai, Minu
2015-06-09 12:16         ` Ville Syrjälä [this message]
2015-06-09 13:32           ` Mathai, Minu
2015-06-09 15:01   ` Dave Gordon
2015-06-09 15:24     ` Ville Syrjälä
2015-06-10  8:09     ` Jani Nikula
2015-06-10 12:27       ` Dave Gordon
2015-06-10 12:50         ` Jani Nikula

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=20150609121642.GJ5176@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=minu.mathai@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