From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt 3/3] tools: Remove punit and nc reg read/write tools
Date: Fri, 12 Sep 2014 18:02:34 +0300 [thread overview]
Message-ID: <20140912150234.GB12416@intel.com> (raw)
In-Reply-To: <878ulodh1v.fsf@intel.com>
On Fri, Sep 12, 2014 at 05:55:40PM +0300, Jani Nikula wrote:
> On Fri, 12 Sep 2014, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > intel_iosf_sb_{read,write} provide the same functionality.
> >
> > intel_dpio_{read,write} are still left in place since they use a
> > different opcode to do the register access. Need to verify if
> > both opcodes work.
>
> And if they don't, can you add a param or special case for that in the
> iosf sb tool?
Yeah that can be done if needed.
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2014-09-12 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 14:30 [PATCH igt 1/3] tools: Allow iosf-sb utils to work on chv ville.syrjala
2014-09-12 14:30 ` [PATCH igt 2/3] toos/intel_iosf_sb: Add symbolic unit names ville.syrjala
2014-09-12 14:30 ` [PATCH igt 3/3] tools: Remove punit and nc reg read/write tools ville.syrjala
2014-09-12 14:55 ` Jani Nikula
2014-09-12 15:02 ` Ville Syrjälä [this message]
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=20140912150234.GB12416@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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