From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH 0/6] accel/ivpu: Fixes for linux-6.6-rc4
Date: Wed, 27 Sep 2023 08:05:37 +0200 [thread overview]
Message-ID: <20230927060537.GE846747@linux.intel.com> (raw)
In-Reply-To: <20230925121137.872158-1-stanislaw.gruszka@linux.intel.com>
On Mon, Sep 25, 2023 at 02:11:31PM +0200, Stanislaw Gruszka wrote:
> - dmesg flood fix
> - HW power-on and interrupt handling fixes for VPU4
> - FW loading/mapping fix
Pushed to drm-misc-fixes.
I had to resolve conflict when rebuilding tip, hope everything is ok there.
Thanks
Stanislaw
> Jacek Lawrynowicz (1):
> accel/ivpu: Don't flood dmesg with VPU ready message
>
> Karol Wachowski (4):
> accel/ivpu/40xx: Ensure clock resource ownership Ack before Power-Up
> accel/ivpu/40xx: Disable frequency change interrupt
> accel/ivpu/40xx: Fix missing VPUIP interrupts
> accel/ivpu: Use cached buffers for FW loading
>
> Stanislaw Gruszka (1):
> accel/ivpu: Do not use wait event interruptible
>
> drivers/accel/ivpu/ivpu_drv.c | 2 +-
> drivers/accel/ivpu/ivpu_fw.c | 8 +++++---
> drivers/accel/ivpu/ivpu_gem.h | 5 +++++
> drivers/accel/ivpu/ivpu_hw_40xx.c | 28 +++++++++++++++++++--------
> drivers/accel/ivpu/ivpu_hw_40xx_reg.h | 2 ++
> drivers/accel/ivpu/ivpu_ipc.c | 11 ++++-------
> 6 files changed, 37 insertions(+), 19 deletions(-)
>
> --
> 2.25.1
>
prev parent reply other threads:[~2023-09-27 6:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 12:11 [PATCH 0/6] accel/ivpu: Fixes for linux-6.6-rc4 Stanislaw Gruszka
2023-09-25 12:11 ` [PATCH 1/6] accel/ivpu: Do not use wait event interruptible Stanislaw Gruszka
2023-09-26 15:51 ` Jeffrey Hugo
2023-09-25 12:11 ` [PATCH 2/6] accel/ivpu: Don't flood dmesg with VPU ready message Stanislaw Gruszka
2023-09-26 15:52 ` Jeffrey Hugo
2023-09-25 12:11 ` [PATCH 3/6] accel/ivpu/40xx: Ensure clock resource ownership Ack before Power-Up Stanislaw Gruszka
2023-09-26 15:53 ` Jeffrey Hugo
2023-09-25 12:11 ` [PATCH 4/6] accel/ivpu/40xx: Disable frequency change interrupt Stanislaw Gruszka
2023-09-26 15:54 ` Jeffrey Hugo
2023-09-25 12:11 ` [PATCH 5/6] accel/ivpu/40xx: Fix missing VPUIP interrupts Stanislaw Gruszka
2023-09-26 15:55 ` Jeffrey Hugo
2023-09-25 12:11 ` [PATCH 6/6] accel/ivpu: Use cached buffers for FW loading Stanislaw Gruszka
2023-09-26 12:09 ` [PATCH v2 " Stanislaw Gruszka
2023-09-26 15:56 ` Jeffrey Hugo
2023-09-27 6:05 ` Stanislaw Gruszka [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=20230927060537.GE846747@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jani.nikula@intel.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.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