From: Daniel Vetter <daniel@ffwll.ch>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
Paolo Bonzini <pbonzini@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Chen, Tiejun" <tiejun.chen@intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [Intel-gfx] [RFC][PATCH] gpu:drm:i915:intel_detect_pch: back to check devfn instead of check class type
Date: Fri, 11 Jul 2014 08:29:56 +0200 [thread overview]
Message-ID: <20140711062956.GP17271@phenom.ffwll.local> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D125FCA7FF@SHSMSX101.ccr.corp.intel.com>
On Thu, Jul 10, 2014 at 09:08:24PM +0000, Tian, Kevin wrote:
> actually I'm curious whether it's still necessary to __detect__ PCH. Could
> we assume a 1:1 mapping between GPU and PCH, e.g. BDW already hard
> code the knowledge:
>
> } else if (IS_BROADWELL(dev)) {
> dev_priv->pch_type = PCH_LPT;
> dev_priv->pch_id =
> INTEL_PCH_LPT_LP_DEVICE_ID_TYPE;
> DRM_DEBUG_KMS("This is Broadwell, assuming "
> "LynxPoint LP PCH\n");
>
> Or if there is real usage on non-fixed mapping (not majority), could it be a
> better option to have fixed mapping as a fallback instead of leaving as
> PCH_NONE? Then even when Qemu doesn't provide a special tweaked PCH,
> the majority case just works.
I guess we can do it, at least I haven't seen any strange combinations in
the wild outside of Intel ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Daniel Vetter <daniel@ffwll.ch>,
"Chen, Tiejun" <tiejun.chen@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Intel-gfx] [RFC][PATCH] gpu:drm:i915:intel_detect_pch: back to check devfn instead of check class type
Date: Fri, 11 Jul 2014 08:29:56 +0200 [thread overview]
Message-ID: <20140711062956.GP17271@phenom.ffwll.local> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D125FCA7FF@SHSMSX101.ccr.corp.intel.com>
On Thu, Jul 10, 2014 at 09:08:24PM +0000, Tian, Kevin wrote:
> actually I'm curious whether it's still necessary to __detect__ PCH. Could
> we assume a 1:1 mapping between GPU and PCH, e.g. BDW already hard
> code the knowledge:
>
> } else if (IS_BROADWELL(dev)) {
> dev_priv->pch_type = PCH_LPT;
> dev_priv->pch_id =
> INTEL_PCH_LPT_LP_DEVICE_ID_TYPE;
> DRM_DEBUG_KMS("This is Broadwell, assuming "
> "LynxPoint LP PCH\n");
>
> Or if there is real usage on non-fixed mapping (not majority), could it be a
> better option to have fixed mapping as a fallback instead of leaving as
> PCH_NONE? Then even when Qemu doesn't provide a special tweaked PCH,
> the majority case just works.
I guess we can do it, at least I haven't seen any strange combinations in
the wild outside of Intel ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Kay, Allen M" <allen.m.kay@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Chen, Tiejun" <tiejun.chen@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Intel-gfx] [RFC][PATCH] gpu:drm:i915:intel_detect_pch: back to check devfn instead of check class type
Date: Fri, 11 Jul 2014 08:29:56 +0200 [thread overview]
Message-ID: <20140711062956.GP17271@phenom.ffwll.local> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D125FCA7FF@SHSMSX101.ccr.corp.intel.com>
On Thu, Jul 10, 2014 at 09:08:24PM +0000, Tian, Kevin wrote:
> actually I'm curious whether it's still necessary to __detect__ PCH. Could
> we assume a 1:1 mapping between GPU and PCH, e.g. BDW already hard
> code the knowledge:
>
> } else if (IS_BROADWELL(dev)) {
> dev_priv->pch_type = PCH_LPT;
> dev_priv->pch_id =
> INTEL_PCH_LPT_LP_DEVICE_ID_TYPE;
> DRM_DEBUG_KMS("This is Broadwell, assuming "
> "LynxPoint LP PCH\n");
>
> Or if there is real usage on non-fixed mapping (not majority), could it be a
> better option to have fixed mapping as a fallback instead of leaving as
> PCH_NONE? Then even when Qemu doesn't provide a special tweaked PCH,
> the majority case just works.
I guess we can do it, at least I haven't seen any strange combinations in
the wild outside of Intel ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-11 6:29 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 9:53 [RFC][PATCH] gpu:drm:i915:intel_detect_pch: back to check devfn instead of check class type Tiejun Chen
2014-06-19 9:53 ` Tiejun Chen
2014-06-19 9:53 ` [Qemu-devel] " Tiejun Chen
2014-06-20 9:40 ` Chen, Tiejun
2014-06-20 9:40 ` Chen, Tiejun
2014-06-20 9:40 ` [Qemu-devel] " Chen, Tiejun
2014-06-20 12:32 ` Daniel Vetter
2014-06-20 12:32 ` Daniel Vetter
2014-06-20 12:32 ` [Qemu-devel] " Daniel Vetter
2014-06-22 8:00 ` Chen, Tiejun
2014-06-22 8:00 ` Chen, Tiejun
2014-06-22 8:00 ` [Qemu-devel] " Chen, Tiejun
2014-06-20 12:48 ` Paolo Bonzini
2014-06-20 12:48 ` [Qemu-devel] " Paolo Bonzini
2014-06-22 8:25 ` Chen, Tiejun
2014-06-22 8:25 ` [Qemu-devel] " Chen, Tiejun
2014-06-25 6:48 ` Paolo Bonzini
2014-06-25 6:48 ` [Qemu-devel] " Paolo Bonzini
2014-06-25 7:34 ` Chen, Tiejun
2014-06-25 7:34 ` [Qemu-devel] " Chen, Tiejun
2014-06-25 7:55 ` Paolo Bonzini
2014-06-25 7:55 ` [Qemu-devel] " Paolo Bonzini
2014-06-30 3:13 ` Chen, Tiejun
2014-06-30 3:13 ` [Qemu-devel] " Chen, Tiejun
2014-06-30 10:56 ` Paolo Bonzini
2014-06-30 10:56 ` [Qemu-devel] " Paolo Bonzini
2014-07-07 14:49 ` Daniel Vetter
2014-07-07 14:49 ` Daniel Vetter
2014-07-07 14:49 ` [Qemu-devel] " Daniel Vetter
2014-07-07 14:57 ` Paolo Bonzini
2014-07-07 14:57 ` [Qemu-devel] " Paolo Bonzini
2014-07-07 17:54 ` [Intel-gfx] " Daniel Vetter
2014-07-07 17:54 ` Daniel Vetter
2014-07-07 17:54 ` [Qemu-devel] " Daniel Vetter
2014-07-07 17:58 ` Paolo Bonzini
2014-07-07 17:58 ` [Qemu-devel] " Paolo Bonzini
2014-07-07 18:40 ` Daniel Vetter
2014-07-07 18:40 ` Daniel Vetter
2014-07-07 18:40 ` [Qemu-devel] [Intel-gfx] " Daniel Vetter
2014-07-10 21:08 ` Tian, Kevin
2014-07-10 21:08 ` Tian, Kevin
2014-07-10 21:08 ` [Qemu-devel] [Intel-gfx] " Tian, Kevin
2014-07-11 6:29 ` Daniel Vetter [this message]
2014-07-11 6:29 ` Daniel Vetter
2014-07-11 6:29 ` [Qemu-devel] " Daniel Vetter
2014-07-11 19:42 ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-07-11 19:42 ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-07-11 19:42 ` [Qemu-devel] [Xen-devel] [Intel-gfx] " Konrad Rzeszutek Wilk
2014-07-11 20:30 ` Tian, Kevin
2014-07-11 20:30 ` [Xen-devel] " Tian, Kevin
2014-07-11 20:30 ` [Qemu-devel] [Xen-devel] [Intel-gfx] " Tian, Kevin
2014-07-12 10:13 ` [Intel-gfx] [Xen-devel] " Daniel Vetter
2014-07-12 10:13 ` Daniel Vetter
2014-07-12 10:13 ` [Qemu-devel] [Intel-gfx] " Daniel Vetter
2014-06-24 2:59 ` [Intel-gfx] " Zhenyu Wang
2014-06-24 2:59 ` Zhenyu Wang
2014-06-24 2:59 ` [Qemu-devel] [Intel-gfx] " Zhenyu Wang
2014-06-25 2:28 ` Chen, Tiejun
2014-06-25 2:28 ` Chen, Tiejun
2014-06-25 2:28 ` [Qemu-devel] [Intel-gfx] " Chen, Tiejun
2014-07-07 14:51 ` Daniel Vetter
2014-07-07 14:51 ` Daniel Vetter
2014-07-07 14:51 ` [Qemu-devel] " Daniel Vetter
2014-06-30 11:18 ` Michael S. Tsirkin
2014-06-30 11:18 ` Michael S. Tsirkin
2014-06-30 11:18 ` [Qemu-devel] " Michael S. Tsirkin
2014-07-01 1:52 ` Chen, Tiejun
2014-07-01 1:52 ` Chen, Tiejun
2014-07-01 1:52 ` [Qemu-devel] " Chen, Tiejun
2014-07-02 6:21 ` Michael S. Tsirkin
2014-07-02 6:21 ` Michael S. Tsirkin
2014-07-02 6:21 ` [Qemu-devel] " Michael S. Tsirkin
2014-07-02 8:27 ` Chen, Tiejun
2014-07-02 8:27 ` Chen, Tiejun
2014-07-02 8:27 ` [Qemu-devel] " Chen, Tiejun
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=20140711062956.GP17271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=allen.m.kay@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tiejun.chen@intel.com \
--cc=xen-devel@lists.xensource.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.