From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH v1] drm/i915: Call intel_edp_init_connector only for eDP.
Date: Tue, 11 Feb 2020 14:27:26 +0000 [thread overview]
Message-ID: <24eea19d0aee5fed1610c27c11e6b5246d923b4a.camel@intel.com> (raw)
In-Reply-To: <87d0alyzzg.fsf@intel.com>
On Tue, 2020-02-11 at 16:12 +0200, Jani Nikula wrote:
> On Tue, 11 Feb 2020, "Lisovskiy, Stanislav" <
> stanislav.lisovskiy@intel.com> wrote:
> > Well, you can just take all those checks and put them into separate
> > function. Something like:
> >
> > bool intel_dp_supports_mst(intel_dp) {
> > if (HAS_DP_MST(i915) && !intel_dp_is_edp(intel_dp)) &&
> > !(INTEL_GEN(i915) < 12 && port == PORT_A) &&
> > !(INTEL_GEN(i915) < 11 && port == PORT_E))
> > return true;
> > return false;
> > }
> >
> > so, then you would have it nicely looking and understandable:
> >
> > if (intel_dp_supports_mst(intel_dp))
> > intel_dp_mst_encoder_init(intel_dig_port,
> > intel_connector->base.base.id);
> >
> > Anyway, I'm _not_ stating that this is _always_ the best way, but
> > I don't see at least any reasons currently why it couldn't be done
> > so.
>
> It's fine, until you realize you need to call a function with the
> condition from more than one place, and you need to remember to have
> the
> same conditions in all the places. So the condition is no longer in
> one
> isolated place. It's not like we haven't thought about this before.
> ;)
Well, that is why I didn't say that this is always a best approach. :)
Sure, if I had to do lots of calls of this function(even though this
should be reviewed then, why we have to do it in a multiple places),
I would then just put this check and init together into some helper
function.
Stan
>
> BR,
> Jani.
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-11 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 11:40 [Intel-gfx] [PATCH v1] drm/i915: Call intel_edp_init_connector only for eDP Stanislav Lisovskiy
2020-02-11 12:16 ` Imre Deak
2020-02-11 13:03 ` Jani Nikula
2020-02-11 13:33 ` Lisovskiy, Stanislav
2020-02-11 13:55 ` Jani Nikula
2020-02-11 14:03 ` Lisovskiy, Stanislav
2020-02-11 14:12 ` Jani Nikula
2020-02-11 14:27 ` Lisovskiy, Stanislav [this message]
2020-02-11 14:21 ` Imre Deak
2020-02-13 15:11 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=24eea19d0aee5fed1610c27c11e6b5246d923b4a.camel@intel.com \
--to=stanislav.lisovskiy@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;
as well as URLs for NNTP newsgroup(s).