From: Daniel Vetter <daniel@ffwll.ch>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 7/9] drm/i915: Rename the forcewake get/put functions
Date: Tue, 20 Jan 2015 11:02:36 +0100 [thread overview]
Message-ID: <20150120100236.GQ10113@phenom.ffwll.local> (raw)
In-Reply-To: <1421400882-3176-7-git-send-email-mika.kuoppala@intel.com>
On Fri, Jan 16, 2015 at 11:34:40AM +0200, Mika Kuoppala wrote:
> @@ -356,14 +356,21 @@ void intel_uncore_sanitize(struct drm_device *dev)
> intel_disable_gt_powersave(dev);
> }
>
> -/*
> - * Generally this is called implicitly by the register read function. However,
> - * if some sequence requires the GT to not power down then this function should
> - * be called at the beginning of the sequence followed by a call to
> - * gen6_gt_force_wake_put() at the end of the sequence.
> +/**
> + * intel_uncore_forcewake_get - grab forcewake domain references
> + * @dev_priv: i915 device instance
> + * @fw_domains: forcewake domains to get reference on
> + *
> + * This function can be used get GT's forcewake domain references.
> + * Normal register access will handle the forcewake domains automatically.
> + * However if some sequence requires the GT to not power down a particular
> + * forcewake domains this function should be called at the beginning of the
> + * sequence. And subsequently the reference should be dropped by symmetric
> + * call to intel_unforce_forcewake_put(). Usually caller wants all the domains
> + * to be kept awake so the @fw_domains would be then FORCEWAKE_ALL.
> */
intel_uncore.c isn't pulled into the drm.tmpl docbook file, which means
your shiny new kerneldoc here won't be used. Can you please supply a
follow-up patch to remedy this?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-20 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:34 [PATCH 1/9] drm/i915: Rebalance runtime pm vs forcewake Mika Kuoppala
2015-01-16 9:34 ` [PATCH 2/9] drm/i915: Assert that runtime pm is active on user fw access Mika Kuoppala
2015-01-16 9:34 ` [PATCH 3/9] drm/i915: Skip uncore lock on earlier gens Mika Kuoppala
2015-01-16 9:34 ` [PATCH 4/9] drm/i915: Reduce duplicated forcewake logic Mika Kuoppala
2015-01-16 9:34 ` [PATCH 5/9] drm/i915: Consolidate forcewake code Mika Kuoppala
2015-01-19 14:20 ` Mika Kuoppala
2015-01-16 9:34 ` [PATCH 6/9] drm/i915: Make vlv and chv forcewake put generic Mika Kuoppala
2015-01-16 9:34 ` [PATCH 7/9] drm/i915: Rename the forcewake get/put functions Mika Kuoppala
2015-01-20 10:02 ` Daniel Vetter [this message]
2015-01-28 15:47 ` [PATCH] drm/i915/documentation: Add intel_uncore.c to drm.tmpl Mika Kuoppala
2015-01-29 16:05 ` Daniel Vetter
2015-02-02 15:30 ` shuang.he
2015-01-16 9:34 ` [PATCH 8/9] drm/i915: Enum forcewake domains and domain identifiers Mika Kuoppala
2015-01-16 9:34 ` [PATCH 9/9] drm/i915: Rename i915_gen6_forcewake_count_info Mika Kuoppala
2015-01-16 19:16 ` shuang.he
2015-01-20 10:09 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-12-16 15:20 [PATCH 1/9] drm/i915: Rebalance runtime pm vs forcewake Mika Kuoppala
2014-12-16 15:20 ` [PATCH 7/9] drm/i915: Rename the forcewake get/put functions Mika Kuoppala
2014-12-17 13:17 ` Mika Kuoppala
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=20150120100236.GQ10113@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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