linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	David Airlie <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	"Lubart, Vitaly" <vitaly.lubart@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Subject: RE: [PATCH v5 02/14] drm/i915/gsc: add slow_fw flag to the mei auxiliary device
Date: Mon, 18 Jul 2022 13:47:35 +0000	[thread overview]
Message-ID: <c5cae0f43af84182b9539085012088d8@intel.com> (raw)
In-Reply-To: <Ysb5464dRPxPrp0d@intel.com>


> 
> On Wed, Jul 06, 2022 at 02:43:33PM +0300, Alexander Usyskin wrote:
> > Add slow_fw flag to the mei auxiliary device info to inform the mei
> > driver about slow underlying firmware.
> > Such firmware will require to use larger operation timeouts.
> >
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> > ---
> >  include/linux/mei_aux.h | 1 +
> 
> This patch has a wrong subject since it doesn't touch i915.

This is in a shared file between drm and mei, but I can resend.

> 
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/include/linux/mei_aux.h b/include/linux/mei_aux.h index
> > 587f25128848..a29f4064b9c0 100644
> > --- a/include/linux/mei_aux.h
> > +++ b/include/linux/mei_aux.h
> > @@ -11,6 +11,7 @@ struct mei_aux_device {
> >  	struct auxiliary_device aux_dev;
> >  	int irq;
> >  	struct resource bar;
> > +	bool slow_fw;
> >  };
> >
> >  #define auxiliary_dev_to_mei_aux_dev(auxiliary_dev) \
> > --
> > 2.34.1
> >

  reply	other threads:[~2022-07-18 13:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 11:43 [PATCH v5 00/14] GSC support for XeHP SDV and DG2 platforms Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 01/14] drm/i915/gsc: skip irq initialization if using polling Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 02/14] drm/i915/gsc: add slow_fw flag to the mei auxiliary device Alexander Usyskin
2022-07-07 15:21   ` Rodrigo Vivi
2022-07-18 13:47     ` Winkler, Tomas [this message]
2022-07-06 11:43 ` [PATCH v5 03/14] drm/i915/gsc: add slow_fw flag to the gsc device definition Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 04/14] drm/i915/gsc: add GSC XeHP SDV platform definition Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 05/14] mei: gsc: use polling instead of interrupts Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 06/14] mei: gsc: wait for reset thread on stop Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 07/14] mei: extend timeouts on slow devices Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 08/14] mei: bus: export common mkhi definitions into a separate header Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 09/14] mei: mkhi: add memory ready command Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 10/14] mei: gsc: setup gsc extended operational memory Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 11/14] mei: gsc: add transition to PXP mode in resume flow Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 12/14] mei: debugfs: add pxp mode to devstate in debugfs Alexander Usyskin
2022-07-06 11:43 ` [PATCH v5 13/14] drm/i915/gsc: allocate extended operational memory in LMEM Alexander Usyskin
2022-08-02 17:29   ` [v5,13/14] " Teres Alexis, Alan Previn
2022-08-02 18:49     ` Winkler, Tomas
2022-07-06 11:43 ` [PATCH v5 14/14] HAX: drm/i915: force INTEL_MEI_GSC on for CI Alexander Usyskin
2022-07-08 13:34 ` [PATCH v5 00/14] GSC support for XeHP SDV and DG2 platforms Greg Kroah-Hartman
2022-07-08 13:57   ` Rodrigo Vivi

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=c5cae0f43af84182b9539085012088d8@intel.com \
    --to=tomas.winkler@intel.com \
    --cc=airlied@linux.ie \
    --cc=alexander.usyskin@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=daniele.ceraolospurio@intel.com \
    --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=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).