From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Lee, Chon Ming" <chon.ming.lee@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/vlv: Rename VLV DPIO register to be more structure to match configdb document.
Date: Thu, 7 Nov 2013 14:43:32 +0200 [thread overview]
Message-ID: <20131107124332.GI5986@intel.com> (raw)
In-Reply-To: <20131107022544.GD2637@clee30-mobl2.gar.corp.intel.com>
On Thu, Nov 07, 2013 at 10:25:44AM +0800, Lee, Chon Ming wrote:
> On 11/06 14:02, Ville Syrjälä wrote:
>
> > > -#define _DPIO_IREF_CTL_A 0x8040
> > > -#define _DPIO_IREF_CTL_B 0x8060
> > > -#define DPIO_IREF_CTL(pipe) _PIPE(pipe, _DPIO_IREF_CTL_A, _DPIO_IREF_CTL_B)
> > > +#define _VLV_PLL_DW10_CH0 0x8040
> > > +#define _VLV_PLL_DW10_CH1 0x8060
> > > +#define VLV_PLL_DW10(ch) _PIPE(ch, _VLV_PLL_DW10_CH0, _VLV_PLL_DW10_CH1)
> >
> > Configdb starts counting from DW8 at 0x8040/60, which kind of make sense
> > since the first PLL block ends at DW7.
> >
> The spreadsheet I refer to is using DW10. The spreadsheet might be incorrect.
> Looking at the register offset, it won't be anymore space left after first PLL
> block. Make sense for DW8 for second PLL block.
The spreadsheet is a bit weird. I was just looking at the web configdb.
That at least has some sense in the offsets (apart from the ref block).
The spreadsheet also uses hex numbers to count the dwords, which doesn't
match what you've done for the > 8 numbers. So I'd go with the web
configdb numbers since they're a bit more consistent.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-11-07 12:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 3:11 [PATCH 1/2] drm/i915/vlv: Make the vlv_dpio_read/vlv_dpio_write more PHY centric Chon Ming Lee
2013-10-30 3:11 ` [PATCH 2/2] drm/i915/vlv: Rename VLV DPIO register to be more structure to match configdb document Chon Ming Lee
2013-11-06 6:37 ` Chon Ming Lee
2013-11-06 12:02 ` Ville Syrjälä
2013-11-07 2:25 ` Lee, Chon Ming
2013-11-07 12:43 ` Ville Syrjälä [this message]
2013-11-07 2:43 ` [PATCH v3 " Chon Ming Lee
2013-11-08 9:25 ` Ville Syrjälä
2013-11-08 16:42 ` Daniel Vetter
2013-10-31 12:20 ` [PATCH 1/2] drm/i915/vlv: Make the vlv_dpio_read/vlv_dpio_write more PHY centric Ville Syrjälä
2013-11-06 6:36 ` Chon Ming Lee
2013-11-06 10:51 ` Ville Syrjälä
2013-11-11 9:23 ` Daniel Vetter
2013-11-26 23:10 ` Jesse Barnes
2013-11-26 23:18 ` Jesse Barnes
2013-11-27 6:51 ` 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=20131107124332.GI5986@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chon.ming.lee@intel.com \
--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