From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH intel-gpu-tools] tools: Added intel_dpio_read and intel_dpio_write
Date: Mon, 06 Aug 2012 14:21:17 -0700 [thread overview]
Message-ID: <95ccd39fcb0204058c18f497b88781ee@bwidawsk.net> (raw)
In-Reply-To: <20120806071652.GE5502@phenom.ffwll.local>
On 2012-08-06 00:16, Daniel Vetter wrote:
> On Thu, Aug 02, 2012 at 09:06:48AM -0700, Ben Widawsky wrote:
>> On 2012-08-02 05:07, Vijay Purushothaman wrote:
>> >In Valleyview the DPLL and lane control registers are accessible
>> only
>> >through side band fabric called DPIO. Added two tools to read and
>> >write
>> >registers residing in this space.
>>
>> Could I convince you to use the centralized read/write mmio
>> functions?
>> Otherwise, everything seems fine to me here.
>
> I wonder whether we need some kernel interface for this, after all if
> the
> kernel touches this, too, things will blow up. Otoh the kernel only
> uses
> the dpio sideband regs at modeset time, so I guess the risk is
> minimal.
> -Daniel
It's the same as any register. As long as it's root only, bullets, gun,
and
target for foot are provided for free. Though I would like to converge
on
central API for register read and right.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-08-06 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 12:07 [PATCH intel-gpu-tools] tools: Added intel_dpio_read and intel_dpio_write Vijay Purushothaman
2012-08-02 16:06 ` Ben Widawsky
2012-08-03 7:05 ` Jani Nikula
2012-08-06 7:45 ` Vijay Purushothaman
2012-08-06 7:16 ` Daniel Vetter
2012-08-06 21:21 ` Ben Widawsky [this message]
2012-08-06 7:40 ` Vijay Purushothaman
2012-08-06 21:26 ` Ben Widawsky
2012-08-17 12:36 Vijay Purushothaman
2012-08-21 7:31 ` 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=95ccd39fcb0204058c18f497b88781ee@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel@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.