From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Check dual_link instead of port==A|C for DSI
Date: Thu, 10 Sep 2015 16:37:26 +0300 [thread overview]
Message-ID: <20150910133726.GH29811@intel.com> (raw)
In-Reply-To: <87bndal7n3.fsf@intel.com>
On Thu, Sep 10, 2015 at 04:35:12PM +0300, Jani Nikula wrote:
> On Thu, 10 Sep 2015, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Everywhere else we check for intel_dsi->dual_link instead of the
> > port mask. So do the same when setting up the lane configuration
> > in MIPI_PORT_CTRL.
> >
> > Cc: Gaurav K Singh <gaurav.k.singh@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.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 781c267..57768c0 100644
> > --- a/drivers/gpu/drm/i915/intel_dsi.c
> > +++ b/drivers/gpu/drm/i915/intel_dsi.c
> > @@ -304,7 +304,7 @@ static void intel_dsi_port_enable(struct intel_encoder *encoder)
> > temp &= ~LANE_CONFIGURATION_MASK;
> > temp &= ~DUAL_LINK_MODE_MASK;
> >
> > - if (intel_dsi->ports == ((1 << PORT_A) | (1 << PORT_C))) {
> > + if (intel_dsi->dual_link) {
>
> I think having the whole intel_dsi->dual_link field is an unnecessary
> extra level of indirection. If there's more than one port, it's dual
> link. There could be a helper to get that info from ->ports.
I considered it, but then I realized that intel_dsi->dual_link actually
houses the dual link mode (of which there are two), so we still need it.
>
> That said, being in line for the time being is more important than doing
> the above.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
>
> > temp |= (intel_dsi->dual_link - 1)
> > << DUAL_LINK_MODE_SHIFT;
> > temp |= intel_crtc->pipe ?
> > --
> > 2.4.6
> >
> > _______________________________________________
> > 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
prev parent reply other threads:[~2015-09-10 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 12:53 [PATCH 1/2] drm/i915: Check dual_link instead of port==A|C for DSI ville.syrjala
2015-09-10 12:53 ` [RFC][PATCH 2/2] drm/i915: Don't write shared DSI port bits multiple time ville.syrjala
2015-09-10 13:35 ` [PATCH 1/2] drm/i915: Check dual_link instead of port==A|C for DSI Jani Nikula
2015-09-10 13:37 ` Ville Syrjälä [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=20150910133726.GH29811@intel.com \
--to=ville.syrjala@linux.intel.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