All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Don't force IOSF_MBI
Date: Mon, 20 Jul 2020 17:29:00 +0800	[thread overview]
Message-ID: <20200720170950.75c989d4@xhacker.debian> (raw)
In-Reply-To: <159501436493.15672.10863611355648667796@build.alporthouse.com>

On Fri, 17 Jul 2020 20:32:44 +0100 Chris Wilson  wrote:

> 
> 
> Quoting Jisheng Zhang (2020-07-17 07:11:38)
> > The i915 doesn't depend on IOSF_MBI, asm/iosf_mbi.h already defines
> > isof_mbi_* APIs when ISOF_MBI is disabled.
> >
> > Don't force IOSF_MBI to allow disabling IOSF_MBI for non SoC platforms.  
> 
> But it is required for Valleyview/Cherryview and we want to support
> those by default. Tricky.

If linux kernel is built for Valleyview/Cherryview, ISOF_MBI has to be
enabled. The dependency is met there.

Thanks


WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Don't force IOSF_MBI
Date: Mon, 20 Jul 2020 17:29:00 +0800	[thread overview]
Message-ID: <20200720170950.75c989d4@xhacker.debian> (raw)
In-Reply-To: <159501436493.15672.10863611355648667796@build.alporthouse.com>

On Fri, 17 Jul 2020 20:32:44 +0100 Chris Wilson  wrote:

> 
> 
> Quoting Jisheng Zhang (2020-07-17 07:11:38)
> > The i915 doesn't depend on IOSF_MBI, asm/iosf_mbi.h already defines
> > isof_mbi_* APIs when ISOF_MBI is disabled.
> >
> > Don't force IOSF_MBI to allow disabling IOSF_MBI for non SoC platforms.  
> 
> But it is required for Valleyview/Cherryview and we want to support
> those by default. Tricky.

If linux kernel is built for Valleyview/Cherryview, ISOF_MBI has to be
enabled. The dependency is met there.

Thanks

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Don't force IOSF_MBI
Date: Mon, 20 Jul 2020 17:29:00 +0800	[thread overview]
Message-ID: <20200720170950.75c989d4@xhacker.debian> (raw)
In-Reply-To: <159501436493.15672.10863611355648667796@build.alporthouse.com>

On Fri, 17 Jul 2020 20:32:44 +0100 Chris Wilson  wrote:

> 
> 
> Quoting Jisheng Zhang (2020-07-17 07:11:38)
> > The i915 doesn't depend on IOSF_MBI, asm/iosf_mbi.h already defines
> > isof_mbi_* APIs when ISOF_MBI is disabled.
> >
> > Don't force IOSF_MBI to allow disabling IOSF_MBI for non SoC platforms.  
> 
> But it is required for Valleyview/Cherryview and we want to support
> those by default. Tricky.

If linux kernel is built for Valleyview/Cherryview, ISOF_MBI has to be
enabled. The dependency is met there.

Thanks

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-07-20  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17  6:11 [PATCH] drm/i915: Don't force IOSF_MBI Jisheng Zhang
2020-07-17  6:11 ` [Intel-gfx] " Jisheng Zhang
2020-07-17  6:11 ` Jisheng Zhang
2020-07-17 17:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-07-17 19:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-07-17 19:32 ` [PATCH] " Chris Wilson
2020-07-17 19:32   ` [Intel-gfx] " Chris Wilson
2020-07-17 19:32   ` Chris Wilson
2020-07-20  9:29   ` Jisheng Zhang [this message]
2020-07-20  9:29     ` [Intel-gfx] " Jisheng Zhang
2020-07-20  9:29     ` Jisheng Zhang

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=20200720170950.75c989d4@xhacker.debian \
    --to=jisheng.zhang@synaptics.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@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 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.