public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/i915/bxt: HPD long/short pulse detect support on port A
Date: Wed, 22 Jul 2015 10:45:29 +0200	[thread overview]
Message-ID: <20150722084529.GY16722@phenom.ffwll.local> (raw)
In-Reply-To: <1437500531.3787.2.camel@intel.com>

On Tue, Jul 21, 2015 at 10:42:11AM -0700, Imre Deak wrote:
> On Tue, 2015-07-21 at 11:40 +0530, Jindal, Sonika wrote:
> > For the patch 3, the commit message can be changed to only "long pulse 
> > detection" instead of "long/short" because you are not adding support 
> > for short pulse detection.
> 
> Well it is support for differentiating between long and short pulses. We
> don't check for the short pulse HW flag, but we do imply it in
> intel_hpd_irq_handler() if the long pulse flag is not set.

Entire series merged, thanks.
-Daniel

> 
> > 
> > Otherwise, this series looks good to me.
> > 
> > Reviewed-by: Sonika Jindal <sonika.jindal@intel.com>
> > 
> > On 7/21/2015 3:13 AM, Imre Deak wrote:
> > > This patchset is a dependency for enabling generic HPD support on the
> > > port A pin.
> > >
> > > Imre Deak (3):
> > >    drm/i915: combine i9xx_get_hpd_pins and pch_get_hpd_pins
> > >    drm/i915: don't use HPD_PORT_A as an alias for HPD_NONE
> > >    drm/i915/bxt: add support for HPD long/short pulse detection on
> > >      HPD_PORT_A pin
> > >
> > >   drivers/gpu/drm/i915/i915_drv.h      |  4 +-
> > >   drivers/gpu/drm/i915/i915_irq.c      | 72 ++++++++++++++++++------------------
> > >   drivers/gpu/drm/i915/i915_reg.h      |  5 +++
> > >   drivers/gpu/drm/i915/intel_hotplug.c | 20 ++++++----
> > >   4 files changed, 55 insertions(+), 46 deletions(-)
> > >
> 
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-07-22  8:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 21:43 [PATCH 0/3] drm/i915/bxt: HPD long/short pulse detect support on port A Imre Deak
2015-07-20 21:43 ` [PATCH 1/3] drm/i915: combine i9xx_get_hpd_pins and pch_get_hpd_pins Imre Deak
2015-07-21  8:20   ` Sivakumar Thulasimani
2015-07-21 17:58     ` Imre Deak
2015-07-22  8:13       ` Sivakumar Thulasimani
2015-07-21 22:32   ` [PATCH v2 " Imre Deak
2015-07-22  8:16     ` Sivakumar Thulasimani
2015-07-20 21:43 ` [PATCH 2/3] drm/i915: don't use HPD_PORT_A as an alias for HPD_NONE Imre Deak
2015-07-21  8:21   ` Sivakumar Thulasimani
2015-07-21 18:03     ` Imre Deak
2015-07-21 22:32   ` [PATCH v2 " Imre Deak
2015-07-22  8:28     ` Sivakumar Thulasimani
2015-07-20 21:43 ` [PATCH 3/3] drm/i915/bxt: add support for HPD long/short pulse detection on HPD_PORT_A pin Imre Deak
2015-07-22  8:31   ` Sivakumar Thulasimani
2015-07-21  6:10 ` [PATCH 0/3] drm/i915/bxt: HPD long/short pulse detect support on port A Jindal, Sonika
2015-07-21 17:42   ` Imre Deak
2015-07-22  8:45     ` Daniel Vetter [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=20150722084529.GY16722@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=imre.deak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox