From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915/uc: Add explicit DISABLED state for firmware
Date: Fri, 16 Aug 2019 23:43:28 +0100 [thread overview]
Message-ID: <156599540849.22053.11817372973045022419@skylake-alporthouse-com> (raw)
In-Reply-To: <20190816205658.15020-1-michal.wajdeczko@intel.com>
Quoting Michal Wajdeczko (2019-08-16 21:56:58)
> We really need to have separate NOT_SUPPORTED state (for
> lack of hardware support) and DISABLED state (to indicate
> user decision) as we will have to take special steps even
> if GuC firmware is now disabled but hardware exists and
> could have been previously used.
>
> v2: fix logic (Chris/CI)
> v3: use proper check to avoid probe failure (CI)
> v4: explain status transitions (Chris)
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-16 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 20:56 [PATCH v4] drm/i915/uc: Add explicit DISABLED state for firmware Michal Wajdeczko
2019-08-16 22:42 ` ✓ Fi.CI.BAT: success for drm/i915/uc: Add explicit DISABLED state for firmware (rev4) Patchwork
2019-08-16 22:43 ` Chris Wilson [this message]
2019-08-17 17:38 ` ✗ 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=156599540849.22053.11817372973045022419@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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.