From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [PATCH igt 3/3] tools: Remove punit and nc reg read/write tools Date: Fri, 12 Sep 2014 18:02:34 +0300 Message-ID: <20140912150234.GB12416@intel.com> References: <1410532239-20807-1-git-send-email-ville.syrjala@linux.intel.com> <1410532239-20807-3-git-send-email-ville.syrjala@linux.intel.com> <878ulodh1v.fsf@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id D87C46E626 for ; Fri, 12 Sep 2014 08:03:05 -0700 (PDT) Content-Disposition: inline In-Reply-To: <878ulodh1v.fsf@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Jani Nikula Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org 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=E4l=E4 > > > > 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=E4l=E4 Intel OTC