From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Alexander Usyskin <alexander.usyskin@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>
Subject: Re: [PATCH v6 00/14] GSC support for XeHP SDV and DG2
Date: Sun, 24 Jul 2022 15:44:05 +0200 [thread overview]
Message-ID: <Yt1Mpc45jcptPEye@kroah.com> (raw)
In-Reply-To: <20220724082428.218628-1-tomas.winkler@intel.com>
On Sun, Jul 24, 2022 at 11:24:14AM +0300, Tomas Winkler wrote:
> Add GSC support for XeHP SDV and DG2 platforms.
>
> The series includes changes for the mei driver:
> - add ability to use polling instead of interrupts
> - add ability to use extended timeouts
> - setup extended operational memory for GSC
>
> The series includes changes for the i915 driver:
> - allocate extended operational memory for GSC
> - GSC on XeHP SDV offsets and definitions
>
> Greg KH, please review and ACK the MEI patches.
> We are pushing these patches through gfx tree as
> the auxiliary device belongs there.
Please wait until after -rc1 is out, my trees are closed for new work at
this point in time, and so should the gfx tree :)
thanks,
greg k-h
prev parent reply other threads:[~2022-07-24 13:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 8:24 [PATCH v6 00/14] GSC support for XeHP SDV and DG2 Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 01/14] drm/i915/gsc: skip irq initialization if using polling Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 02/14] mei: add slow_fw flag to the mei auxiliary device Tomas Winkler
2022-07-24 13:44 ` Greg Kroah-Hartman
2022-07-24 8:24 ` [PATCH v6 03/14] drm/i915/gsc: add slow_fw flag to the gsc device definition Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 04/14] drm/i915/gsc: add GSC XeHP SDV platform definition Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 05/14] mei: gsc: use polling instead of interrupts Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 06/14] mei: gsc: wait for reset thread on stop Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 07/14] mei: extend timeouts on slow devices Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 08/14] mei: bus: export common mkhi definitions into a separate header Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 09/14] mei: mkhi: add memory ready command Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 10/14] mei: gsc: setup gsc extended operational memory Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 11/14] mei: gsc: add transition to PXP mode in resume flow Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 12/14] mei: debugfs: add pxp mode to devstate in debugfs Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 13/14] drm/i915/gsc: allocate extended operational memory in LMEM Tomas Winkler
2022-07-24 8:24 ` [PATCH v6 14/14] HAX: drm/i915: force INTEL_MEI_GSC on for CI Tomas Winkler
2022-07-24 13:44 ` Greg Kroah-Hartman [this message]
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=Yt1Mpc45jcptPEye@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=alexander.usyskin@intel.com \
--cc=daniel@ffwll.ch \
--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 \
--cc=tomas.winkler@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=vitaly.lubart@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;
as well as URLs for NNTP newsgroup(s).