From: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 07/14] mei: gsc: wait for reset thread on stop
Date: Sun, 19 Jun 2022 16:37:14 +0300 [thread overview]
Message-ID: <20220619133721.523546-8-alexander.usyskin@intel.com> (raw)
In-Reply-To: <20220619133721.523546-1-alexander.usyskin@intel.com>
Wait for reset work to complete before initiating
stop reset flow sequence.
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---
drivers/misc/mei/init.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/mei/init.c b/drivers/misc/mei/init.c
index eb052005ca86..5bb6ba662cc0 100644
--- a/drivers/misc/mei/init.c
+++ b/drivers/misc/mei/init.c
@@ -320,6 +320,8 @@ void mei_stop(struct mei_device *dev)
mei_clear_interrupts(dev);
mei_synchronize_irq(dev);
+ /* to catch HW-initiated reset */
+ mei_cancel_work(dev);
mutex_lock(&dev->device_lock);
--
2.32.0
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Usyskin <alexander.usyskin@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 07/14] mei: gsc: wait for reset thread on stop
Date: Sun, 19 Jun 2022 16:37:14 +0300 [thread overview]
Message-ID: <20220619133721.523546-8-alexander.usyskin@intel.com> (raw)
In-Reply-To: <20220619133721.523546-1-alexander.usyskin@intel.com>
Wait for reset work to complete before initiating
stop reset flow sequence.
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---
drivers/misc/mei/init.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/misc/mei/init.c b/drivers/misc/mei/init.c
index eb052005ca86..5bb6ba662cc0 100644
--- a/drivers/misc/mei/init.c
+++ b/drivers/misc/mei/init.c
@@ -320,6 +320,8 @@ void mei_stop(struct mei_device *dev)
mei_clear_interrupts(dev);
mei_synchronize_irq(dev);
+ /* to catch HW-initiated reset */
+ mei_cancel_work(dev);
mutex_lock(&dev->device_lock);
--
2.32.0
next prev parent reply other threads:[~2022-06-19 13:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 13:37 [PATCH v3 00/14] GSC support for XeHP SDV and DG2 platforms Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 01/14] HAX: drm/i915: force INTEL_MEI_GSC on for CI Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 02/14] drm/i915/gsc: skip irq initialization if using polling Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 03/14] drm/i915/gsc: add slow_fw flag to the mei auxiliary device Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] [PATCH v3 04/14] drm/i915/gsc: add slow_fw flag to the gsc device definition Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] [PATCH v3 05/14] drm/i915/gsc: add GSC XeHP SDV platform definition Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] [PATCH v3 06/14] mei: gsc: use polling instead of interrupts Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin [this message]
2022-06-19 13:37 ` [PATCH v3 07/14] mei: gsc: wait for reset thread on stop Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] [PATCH v3 08/14] mei: extend timeouts on slow devices Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] [PATCH v3 09/14] mei: bus: export common mkhi definitions into a separate header Alexander Usyskin
2022-06-19 13:37 ` Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 10/14] mei: mkhi: add memory ready command Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 11/14] mei: gsc: setup gsc extended operational memory Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 12/14] mei: gsc: add transition to PXP mode in resume flow Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:37 ` [PATCH v3 13/14] mei: debugfs: add pxp mode to devstate in debugfs Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-27 14:02 ` Greg Kroah-Hartman
2022-06-27 14:02 ` [Intel-gfx] " Greg Kroah-Hartman
2022-06-29 8:37 ` Winkler, Tomas
2022-06-29 8:37 ` [Intel-gfx] " Winkler, Tomas
2022-06-19 13:37 ` [PATCH v3 14/14] drm/i915/gsc: allocate extended operational memory in LMEM Alexander Usyskin
2022-06-19 13:37 ` [Intel-gfx] " Alexander Usyskin
2022-06-19 13:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for GSC support for XeHP SDV and DG2 platforms (rev3) Patchwork
2022-06-19 13:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-19 14:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-19 16:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-27 14:02 ` [Intel-gfx] [PATCH v3 00/14] GSC support for XeHP SDV and DG2 platforms Greg Kroah-Hartman
2022-06-27 14:02 ` Greg Kroah-Hartman
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=20220619133721.523546-8-alexander.usyskin@intel.com \
--to=alexander.usyskin@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=gregkh@linuxfoundation.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 \
--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 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.