From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Use a macro to express the range of valid gens for reg_read
Date: Mon, 31 Mar 2014 13:47:12 +0300 [thread overview]
Message-ID: <87ob0mejbj.fsf@intel.com> (raw)
In-Reply-To: <1396261448-30300-1-git-send-email-damien.lespiau@intel.com>
On Mon, 31 Mar 2014, Damien Lespiau <damien.lespiau@intel.com> wrote:
> The reg_read whitelist has a gen bitmask to code the gens we're allowing
> the register to be read on. Until now, it was a litteral, but we can be
> a bit more expressive.
s/litteral/literal/
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> To ease the review, a small test program:
>
> $ cat bit-range.c
> #include <stdio.h>
> #include <stdint.h>
>
> #define U32_C(x) x ## U
> #define GENMASK(h, l) (((U32_C(1) << ((h) - (l) + 1)) - 1) << (l))
> #define GEN_RANGE(l, h) GENMASK(h, l)
>
> int main(int argc, char **argv)
> {
> printf("0x%08x\n", GEN_RANGE(1, 1));
> printf("0x%08x\n", GEN_RANGE(1, 2));
> printf("0x%08x\n", GEN_RANGE(4, 4));
> printf("0x%08x\n", GEN_RANGE(4, 5));
> printf("0x%08x\n", GEN_RANGE(1, 31));
> printf("0x%08x\n", GEN_RANGE(4, 8));
>
> return 0;
> }
> $ ./bit-range
> 0x00000002
> 0x00000006
> 0x00000010
> 0x00000030
> 0xfffffffe
> 0x000001f0
>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
> drivers/gpu/drm/i915/intel_uncore.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
> index 823d699..e2aa964 100644
> --- a/drivers/gpu/drm/i915/intel_uncore.c
> +++ b/drivers/gpu/drm/i915/intel_uncore.c
> @@ -860,12 +860,15 @@ void intel_uncore_fini(struct drm_device *dev)
> intel_uncore_forcewake_reset(dev, false);
> }
>
> +#define GEN_RANGE(l, h) GENMASK(h, l)
> +
> static const struct register_whitelist {
> uint64_t offset;
> uint32_t size;
> - uint32_t gen_bitmask; /* support gens, 0x10 for 4, 0x30 for 4 and 5, etc. */
> + /* supported gens, 0x10 for 4, 0x30 for 4 and 5, etc. */
> + uint32_t gen_bitmask;
> } whitelist[] = {
> - { RING_TIMESTAMP(RENDER_RING_BASE), 8, 0x1F0 },
> + { RING_TIMESTAMP(RENDER_RING_BASE), 8, GEN_RANGE(4, 8) },
> };
>
> int i915_reg_read_ioctl(struct drm_device *dev,
> --
> 1.8.3.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-31 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 10:24 [PATCH] drm/i915: Use a macro to express the range of valid gens for reg_read Damien Lespiau
2014-03-31 10:47 ` Jani Nikula [this message]
2014-03-31 12:08 ` 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=87ob0mejbj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=damien.lespiau@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 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.