Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karolina Stolarek <karolina.stolarek@intel.com>
To: <sai.gowtham.ch@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] lib/intel_reg: Add copy commands in the lib
Date: Fri, 18 Aug 2023 15:40:28 +0200	[thread overview]
Message-ID: <c8d42fd3-4f5b-cfbb-c61f-623e6384851c@intel.com> (raw)
In-Reply-To: <20230818051916.28272-2-sai.gowtham.ch@intel.com>

Hi Sai,

On 18.08.2023 07:19, sai.gowtham.ch@intel.com wrote:
> From: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
> 
> Add memory copy and set commands to the lib.
> 
> Signed-off-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
> ---
>   lib/intel_mocs.h | 2 ++
>   lib/intel_reg.h  | 4 ++++
>   2 files changed, 6 insertions(+)
> 
> diff --git a/lib/intel_mocs.h b/lib/intel_mocs.h
> index 255eac0ff..4f4cf53e0 100644
> --- a/lib/intel_mocs.h
> +++ b/lib/intel_mocs.h
> @@ -6,6 +6,8 @@
>   #ifndef _INTEL_MOCS_H
>   #define _INTEL_MOCS_H
>   
> +#define MEM_COPY_MOCS_SHIFT                     25
> +

 From what I can see, this flag is only used in the xe_copy_basic test. 
Would it be possible to keep it local for the time being?

Many thanks,
Karolina

>   uint8_t intel_get_wb_mocs(int fd);
>   uint8_t intel_get_uc_mocs(int fd);
>   
> diff --git a/lib/intel_reg.h b/lib/intel_reg.h
> index 3bf3676dc..322aec9fd 100644
> --- a/lib/intel_reg.h
> +++ b/lib/intel_reg.h
> @@ -2564,6 +2564,10 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
>   
>   #define XY_FAST_COLOR_BLT		((0x2<<29)|(0x44<<22)|0xe)
>   
> +/* RAW memory commands */
> +#define MEM_COPY_CMD                    ((0x2 << 29)|(0x5a << 22)|0x8)
> +#define MEM_SET_CMD                     ((0x2 << 29)|(0x5b << 22)|0x5)
> +
>   #define XY_FAST_COPY_BLT				((2<<29)|(0x42<<22)|0x8)
>   /* dword 0 */
>   #define   XY_FAST_COPY_SRC_TILING_LINEAR		(0 << 20)

  reply	other threads:[~2023-08-18 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  5:19 [igt-dev] [PATCH i-g-t 0/2] Add copy basic test to exercise blt commands sai.gowtham.ch
2023-08-18  5:19 ` [igt-dev] [PATCH i-g-t 1/2] lib/intel_reg: Add copy commands in the lib sai.gowtham.ch
2023-08-18 13:40   ` Karolina Stolarek [this message]
2023-08-18  5:19 ` [igt-dev] [PATCH i-g-t 2/2] tests/xe/xe_copy_basic: Add copy basic test to exercise blt commands sai.gowtham.ch
2023-08-18 13:40   ` Karolina Stolarek
2023-08-21  9:51     ` Kamil Konieczny
2023-08-21 13:29     ` Ch, Sai Gowtham
2023-08-22  8:14       ` Karolina Stolarek
2023-08-18  6:24 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2023-08-18  6:41 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-18  6:55 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-19  8:56 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork

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=c8d42fd3-4f5b-cfbb-c61f-623e6384851c@intel.com \
    --to=karolina.stolarek@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=sai.gowtham.ch@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