From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/4] drm/i915: Store aux power domain in intel_dp
Date: Mon, 06 Feb 2017 09:41:01 +0200 [thread overview]
Message-ID: <1486366861.2434.1.camel@gmail.com> (raw)
In-Reply-To: <87zii3wdjl.fsf@intel.com>
On Fri, 2017-02-03 at 16:32 +0200, Jani Nikula wrote:
> On Fri, 03 Feb 2017, Ander Conselvan de Oliveira <ander.conselvan.de.oliveira@
> intel.com> wrote:
> > The aux power domain only makes sense in the DP code. Storing it in
> > struct intel_dp avoids some indirection.
>
> This seems to make a whole lot of sense. I've just got one detail I
> wanted to track down but don't have time for it now:
>
> > - case INTEL_OUTPUT_DP:
> > - case INTEL_OUTPUT_EDP:
> > - intel_dig_port = enc_to_dig_port(&intel_encoder->base);
> > - return port_to_aux_power_domain(intel_dig_port->port);
> > - case INTEL_OUTPUT_DP_MST:
> > - intel_dig_port = enc_to_mst(&intel_encoder->base)->primary;
> > - return port_to_aux_power_domain(intel_dig_port->port);
>
> Is the difference between DP and DP MST not significant, don't we need
> to take it into account? Or does it go away with avoiding the
> indirection?
This goes away with avoiding the indirection. The primary field of an MST
encoder points to "real" struct intel_digital_port, whose intel_dp struct will
have aux_power_domain properly initialized. Moreover, the MST code never
references the AUX power domains.
Ander
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-06 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 14:03 [PATCH v2 1/4] drm/i915: Remove WA for swapped HPD pins in broxton A stepping Ander Conselvan de Oliveira
2017-02-03 14:03 ` [PATCH v2 2/4] drm/i915/dp: Move initialization of hpd_pin to a new function Ander Conselvan de Oliveira
2017-02-03 14:22 ` Jani Nikula
2017-02-09 8:25 ` Ander Conselvan De Oliveira
2017-02-03 14:03 ` [PATCH v2 3/4] drm/i915: Store aux power domain in intel_dp Ander Conselvan de Oliveira
2017-02-03 14:32 ` Jani Nikula
2017-02-06 7:41 ` Ander Conselvan De Oliveira [this message]
2017-02-03 14:03 ` [PATCH v2 4/4] drm/i915: Store encoder power domain in struct intel_encoder Ander Conselvan de Oliveira
2017-02-03 14:21 ` [PATCH v2 1/4] drm/i915: Remove WA for swapped HPD pins in broxton A stepping Jani Nikula
2017-02-03 16:26 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] " Patchwork
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=1486366861.2434.1.camel@gmail.com \
--to=conselvan2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox