From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 3/3] drm/i915: use the gmbus irq for waits
Date: Wed, 05 Sep 2012 22:34:54 +0100 [thread overview]
Message-ID: <6c3329$5sb84q@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1346873081-1305-3-git-send-email-daniel.vetter@ffwll.ch>
On Wed, 5 Sep 2012 21:24:41 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> We need two special things to properly wire this up:
> - Add another argument to gmbus_wait_hw_status to pass in the
> correct interrupt bit in gmbus4.
> - Since we can only get an irq for one of the two events we want,
> hand-roll the wait_event_timeout code so that we wake up every
> jiffie and can check for NAKs. This way we also subsume gmbus
> support for platforms without interrupts (or where those are not
> yet enabled).
>
> The important bit really is to only enable one gmbus interrupt source
> at the same time - with that piece of lore figured out, this seems to
> work flawlessly.
Outline looks good. Did have a worry over the conversion to schedule(1),
but then realised that is equivalent to the current msleep. So there is
a potential that we need to do better for gen2/3.
Need to dig a little more, so just a-b for now.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-05 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 19:24 [PATCH 1/3] drm/i915: extract gmbus_wait_hw_status Daniel Vetter
2012-09-05 19:24 ` [PATCH 2/3] drm/i915: wire up gmbus irq handler Daniel Vetter
2012-09-05 21:29 ` Chris Wilson
2012-09-05 21:36 ` Daniel Vetter
2012-09-05 21:52 ` Chris Wilson
2012-09-05 19:24 ` [PATCH 3/3] drm/i915: use the gmbus irq for waits Daniel Vetter
2012-09-05 21:34 ` Chris Wilson [this message]
2012-09-05 21:25 ` [PATCH 1/3] drm/i915: extract gmbus_wait_hw_status Chris Wilson
2012-09-05 21:30 ` Daniel Vetter
2012-09-05 22:12 ` Chris Wilson
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='6c3329$5sb84q@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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 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.