From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/i915/irq: move hotplug even debug print to second connector loop
Date: Thu, 18 Jun 2015 13:43:30 +0300 [thread overview]
Message-ID: <87d20ti9f1.fsf@intel.com> (raw)
In-Reply-To: <20150618102142.GF24012@nuc-i3427.alporthouse.com>
On Thu, 18 Jun 2015, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Subject s/even/event/
Oops.
> On Thu, Jun 18, 2015 at 01:06:13PM +0300, Jani Nikula wrote:
>> The hotplug work function has two loops iterating over connectors, the
>> first for handling hotplug disabling due to irq storms and the second
>> for actually handling the hotplug events. Move the debug printing into
>> the second one, so we can abstract the storm handling better. This may
>> change the output ordering slightly when there are multiple simultaneous
>> hotplug events.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_irq.c | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
>> index 56db9e747464..d64d6895a2e5 100644
>> --- a/drivers/gpu/drm/i915/i915_irq.c
>> +++ b/drivers/gpu/drm/i915/i915_irq.c
>> @@ -917,10 +917,6 @@ static void i915_hotplug_work_func(struct work_struct *work)
>> | DRM_CONNECTOR_POLL_DISCONNECT;
>> hpd_disabled = true;
>> }
>> - if (hpd_event_bits & (1 << intel_encoder->hpd_pin)) {
>> - DRM_DEBUG_KMS("Connector %s (pin %i) received hotplug event.\n",
>> - connector->name, intel_encoder->hpd_pin);
>> - }
>> }
>> /* if there were no outputs to poll, poll was disabled,
>> * therefore make sure it's enabled when disabling HPD on
>> @@ -939,6 +935,8 @@ static void i915_hotplug_work_func(struct work_struct *work)
>> continue;
>> intel_encoder = intel_connector->encoder;
>> if (hpd_event_bits & (1 << intel_encoder->hpd_pin)) {
>> + DRM_DEBUG_KMS("Connector %s (pin %i) received hotplug event.\n",
>> + connector->name, intel_encoder->hpd_pin);
>
> In light of other conversations, is reporting an irq (even a hotplug
> one) directly related to KMS? I think DRIVER is more specific in this
> case.
Perhaps; this patch was just about moving the call around. A more
thorough cleanup of the debugging could be a follow-up.
BR,
Jani.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-18 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 10:06 [PATCH 0/5] drm/i915: hotplug cleanup saga continues Jani Nikula
2015-06-18 10:06 ` [PATCH 1/5] drm/i915/irq: move hotplug even debug print to second connector loop Jani Nikula
2015-06-18 10:21 ` Chris Wilson
2015-06-18 10:43 ` Jani Nikula [this message]
2015-06-18 10:52 ` Chris Wilson
2015-06-18 10:06 ` [PATCH 2/5] drm/i915/irq: abstract irq storm hotplug disabling Jani Nikula
2015-06-22 13:02 ` [Intel-gfx] " Daniel Vetter
2015-06-23 0:29 ` Dave Airlie
2015-06-23 6:36 ` Daniel Vetter
2015-06-18 10:06 ` [PATCH 3/5] drm/i915/irq: clarify irq storm related function naming Jani Nikula
2015-06-18 10:06 ` [PATCH 4/5] drm/i915: move generic hotplug code into new intel_hotplug.c file Jani Nikula
2015-06-18 10:06 ` [PATCH 5/5] drm/i915: reduce line width in {pch, i9xx}_get_hpd_pins() Jani Nikula
2015-06-22 13:05 ` Daniel Vetter
2015-06-22 13:06 ` [PATCH 0/5] drm/i915: hotplug cleanup saga continues Daniel Vetter
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=87d20ti9f1.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--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