From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@redhat.com>,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 0/2] mei: add timeout to send
Date: Wed, 30 Nov 2022 09:20:28 -0500 [thread overview]
Message-ID: <Y4dmrP9RzXi7wrwJ@intel.com> (raw)
In-Reply-To: <20221116124735.2493847-1-alexander.usyskin@intel.com>
On Wed, Nov 16, 2022 at 02:47:33PM +0200, Alexander Usyskin wrote:
> When driver wakes up the firmware from the low power state,
> it is sending a memory ready message.
> The send is done via synchronous/blocking function to ensure
> that firmware is in ready state. However, in case of firmware
> undergoing reset send might be block forever.
> To address this issue a timeout is added to blocking
> write command on the internal bus.
>
> Introduce the __mei_cl_send_timeout function to use instead of
> __mei_cl_send in cases where timeout is required.
> The mei_cl_write has only two callers and there is no need to split
> it into two functions.
>
> V2: address review comments:
> - split __mei_cl_send and __mei_cl_send_timeout
> - add units to timeout KDoc
> - use MAX_SCHEDULE_TIMEOUT to squash wait to one macro
>
> V3: - split the state fix into separate patch
> - document define unit
> - expand timeout KDoc
These 2 patches looks good to me now.
Greg, whenever you review it, please let me know if it is
okay to me to push these through the drm-fixes, or if you
prefer these to the mei branches.
Btw, Alexander, would we have a good "Fixes:" tag for these
patches?
Thanks,
Rodrigo.
>
> Alexander Usyskin (2):
> mei: add timeout to send
> mei: bus-fixup: change pxp mode only if message was sent
>
> drivers/misc/mei/bus-fixup.c | 14 +++++++++-----
> drivers/misc/mei/bus.c | 22 +++++++++++++++++++++-
> drivers/misc/mei/client.c | 20 ++++++++++++++++----
> drivers/misc/mei/client.h | 2 +-
> drivers/misc/mei/main.c | 2 +-
> drivers/misc/mei/mei_dev.h | 2 ++
> 6 files changed, 50 insertions(+), 12 deletions(-)
>
> --
> 2.34.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alexander Usyskin <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@redhat.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v3 0/2] mei: add timeout to send
Date: Wed, 30 Nov 2022 09:20:28 -0500 [thread overview]
Message-ID: <Y4dmrP9RzXi7wrwJ@intel.com> (raw)
In-Reply-To: <20221116124735.2493847-1-alexander.usyskin@intel.com>
On Wed, Nov 16, 2022 at 02:47:33PM +0200, Alexander Usyskin wrote:
> When driver wakes up the firmware from the low power state,
> it is sending a memory ready message.
> The send is done via synchronous/blocking function to ensure
> that firmware is in ready state. However, in case of firmware
> undergoing reset send might be block forever.
> To address this issue a timeout is added to blocking
> write command on the internal bus.
>
> Introduce the __mei_cl_send_timeout function to use instead of
> __mei_cl_send in cases where timeout is required.
> The mei_cl_write has only two callers and there is no need to split
> it into two functions.
>
> V2: address review comments:
> - split __mei_cl_send and __mei_cl_send_timeout
> - add units to timeout KDoc
> - use MAX_SCHEDULE_TIMEOUT to squash wait to one macro
>
> V3: - split the state fix into separate patch
> - document define unit
> - expand timeout KDoc
These 2 patches looks good to me now.
Greg, whenever you review it, please let me know if it is
okay to me to push these through the drm-fixes, or if you
prefer these to the mei branches.
Btw, Alexander, would we have a good "Fixes:" tag for these
patches?
Thanks,
Rodrigo.
>
> Alexander Usyskin (2):
> mei: add timeout to send
> mei: bus-fixup: change pxp mode only if message was sent
>
> drivers/misc/mei/bus-fixup.c | 14 +++++++++-----
> drivers/misc/mei/bus.c | 22 +++++++++++++++++++++-
> drivers/misc/mei/client.c | 20 ++++++++++++++++----
> drivers/misc/mei/client.h | 2 +-
> drivers/misc/mei/main.c | 2 +-
> drivers/misc/mei/mei_dev.h | 2 ++
> 6 files changed, 50 insertions(+), 12 deletions(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-11-30 14:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:47 [Intel-gfx] [PATCH v3 0/2] mei: add timeout to send Alexander Usyskin
2022-11-16 12:47 ` Alexander Usyskin
2022-11-16 12:47 ` [Intel-gfx] [PATCH v3 1/2] " Alexander Usyskin
2022-11-16 12:47 ` Alexander Usyskin
2022-11-16 12:47 ` [Intel-gfx] [PATCH v3 2/2] mei: bus-fixup: change pxp mode only if message was sent Alexander Usyskin
2022-11-16 12:47 ` Alexander Usyskin
2022-11-16 21:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success for mei: add timeout to send (rev3) Patchwork
2022-11-17 0:46 ` Matt Roper
2022-11-17 7:24 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-11-30 14:20 ` Rodrigo Vivi [this message]
2022-11-30 14:20 ` [Intel-gfx] [PATCH v3 0/2] mei: add timeout to send Rodrigo Vivi
2022-11-30 17:43 ` Greg Kroah-Hartman
2022-11-30 17:43 ` Greg Kroah-Hartman
2022-11-30 17:48 ` Vivi, Rodrigo
2022-11-30 17:48 ` Vivi, Rodrigo
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=Y4dmrP9RzXi7wrwJ@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@redhat.com \
--cc=alexander.usyskin@intel.com \
--cc=daniel@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@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.