From: "Antti Koskipää" <antti.koskipaa@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Clean up display pipe register accesses
Date: Mon, 27 Jan 2014 13:17:09 +0200 [thread overview]
Message-ID: <52E64035.4090302@linux.intel.com> (raw)
In-Reply-To: <20140124125236.GD9454@intel.com>
On 01/24/14 14:52, Ville Syrjälä wrote:
> On Fri, Jan 24, 2014 at 02:13:14PM +0200, Antti Koskipaa wrote:
>> +#define PIPE_A_OFFSET 0x70000
>> +#define PIPE_B_OFFSET 0x71000
>> +#define PIPE_C_OFFSET 0x72000
>
> I'd like a comment here to explain what PIPE_EDP_OFFSET
> actually means. Eg.:
>
> /*
> * There's actually no pipe EDP. Some pipe registers have
> * simply shifted from the pipe to the transcoder, while
> * keeping their original offset. Thus we need PIPE_EDP_OFFSET
> * to access such registers in transcoder EDP.
> */
Ok.
>> #define TRANS_DDI_FUNC_CTL_B 0x61400
>> #define TRANS_DDI_FUNC_CTL_C 0x62400
>> #define TRANS_DDI_FUNC_CTL_EDP 0x6F400
>> -#define TRANS_DDI_FUNC_CTL(tran) _TRANSCODER(tran, TRANS_DDI_FUNC_CTL_A, \
>> - TRANS_DDI_FUNC_CTL_B)
>> +#define TRANS_DDI_FUNC_CTL(tran) (dev_priv->info->trans_ddi_func_offsets[tran])
>> +
>
> Why is there a separate offset for these? They're all within the
> normal transcoder range, aren't they?
Yes, they are. Will use _TRANSCODER2 for those too.
>> #define TRANS_DDI_FUNC_ENABLE (1<<31)
>> /* Those bits are ignored by pipe EDP since it can only connect to DDI A */
>> #define TRANS_DDI_PORT_MASK (7<<28)
>> @@ -5343,10 +5362,12 @@
>> #define TRANS_CLK_SEL_DISABLED (0x0<<29)
>> #define TRANS_CLK_SEL_PORT(x) ((x+1)<<29)
>>
>> -#define _TRANSA_MSA_MISC 0x60410
>> -#define _TRANSB_MSA_MISC 0x61410
>> -#define TRANS_MSA_MISC(tran) _TRANSCODER(tran, _TRANSA_MSA_MISC, \
>> - _TRANSB_MSA_MISC)
>> +#define TRANSA_MSA_MISC 0x60410
>> +#define TRANSB_MSA_MISC 0x61410
>> +#define TRANSC_MSA_MISC 0x62410
>> +#define TRANS_EDP_MSA_MISC 0x6f410
>> +#define TRANS_MSA_MISC(tran) (dev_priv->info->trans_msa_misc_offsets[tran])
>
> ditto
Ditto.
--
- Antti
prev parent reply other threads:[~2014-01-27 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 12:13 [PATCH v2] drm/i915: Clean up display pipe register accesses Antti Koskipaa
2014-01-24 12:52 ` Ville Syrjälä
2014-01-27 11:17 ` Antti Koskipää [this message]
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=52E64035.4090302@linux.intel.com \
--to=antti.koskipaa@linux.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 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.