From: "Srinivas, Vidya" <vidya.srinivas@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 01/14] drm/i915: Check for platform specific GPIO config
Date: Wed, 8 Feb 2017 10:30:28 +0000 [thread overview]
Message-ID: <F653A0A18852B74D88578FA2EB7094EA8B502573@BGSMSX108.gar.corp.intel.com> (raw)
In-Reply-To: <87bmvgfsf1.fsf@intel.com>
> -----Original Message-----
> From: Jani Nikula [mailto:jani.nikula@linux.intel.com]
> Sent: Monday, January 9, 2017 3:48 PM
> To: Srinivas, Vidya <vidya.srinivas@intel.com>; intel-
> gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH 01/14] drm/i915: Check for platform specific
> GPIO config
>
> On Mon, 09 Jan 2017, Vidya Srinivas <vidya.srinivas@intel.com> wrote:
> > From: Uma Shankar <uma.shankar@intel.com>
> >
> > Panel GPIO control should be done based on platform. Add a check to
> > restrict VLV and CHT specific GPIO confirguration, so that they dont
> > apply to other platforms.
>
> There are no code paths that would have
> dev_priv->vbt.dsi.config->pwm_blc == PPS_BLC_PMIC on platforms other
> than VLV/CVH.
This particular field is by default 0 which triggers a redundant gpio get operation
for BXT. Hence limiting this to BYT/CHT platforms.
Regards
Vidya
>
> BR,
> Jani.
>
> >
> > Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_dsi.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_dsi.c
> > b/drivers/gpu/drm/i915/intel_dsi.c
> > index 16732e7..27d8f95 100644
> > --- a/drivers/gpu/drm/i915/intel_dsi.c
> > +++ b/drivers/gpu/drm/i915/intel_dsi.c
> > @@ -1560,7 +1560,8 @@ void intel_dsi_init(struct drm_i915_private
> *dev_priv)
> > * In case of BYT with CRC PMIC, we need to use GPIO for
> > * Panel control.
> > */
> > - if (dev_priv->vbt.dsi.config->pwm_blc == PPS_BLC_PMIC) {
> > + if ((IS_VALLEYVIEW(dev_priv) || IS_CHERRYVIEW(dev_priv)) &&
> > + (dev_priv->vbt.dsi.config->pwm_blc == PPS_BLC_PMIC)) {
> > intel_dsi->gpio_panel =
> > gpiod_get(dev->dev, "panel", GPIOD_OUT_HIGH);
>
> --
> Jani Nikula, Intel Open Source Technology Center
_______________________________________________
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-08 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 9:15 [PATCH 01/14] drm/i915: Check for platform specific GPIO config Vidya Srinivas
2017-01-09 10:18 ` Jani Nikula
2017-02-08 10:30 ` Srinivas, Vidya [this message]
2017-02-08 10:41 ` Jani Nikula
2017-02-08 10:58 ` Srinivas, Vidya
2017-02-08 11:11 ` Jani Nikula
2017-02-08 11:31 Shankar, Uma
2017-02-08 12:28 ` Jani Nikula
2017-02-09 8:34 ` Shankar, Uma
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=F653A0A18852B74D88578FA2EB7094EA8B502573@BGSMSX108.gar.corp.intel.com \
--to=vidya.srinivas@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 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.