From: Oded Gabbay <ogabbay@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] habanalabs second pull request for kernel 5.12
Date: Mon, 8 Feb 2021 18:30:22 +0200 [thread overview]
Message-ID: <20210208163022.GA5745@CORE.localdomain> (raw)
Hi Greg,
This is habanalabs second pull request for the merge window of
kernel 5.12.
It contains important fixes, especially in the firmware-related code.
Details are in the tag.
Thanks,
Oded
The following changes since commit 369aea84595189200a2e6b028f556a7efa0ec489:
mei: implement client dma setup. (2021-02-06 15:48:11 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git tags/misc-habanalabs-next-2021-02-08
for you to fetch changes up to da5dfbb97a82ff698e1dc7b229d4d4f5759dad2b:
habanalabs/gaudi: don't enable clock gating on DMA5 (2021-02-08 18:20:08 +0200)
----------------------------------------------------------------
This tag contains the following changes for 5.12-rc1:
- Improve communication protocol with device CPU CP application.
The change prevents random (rare) out-of-sync errors.
- Notify F/W to start sending events only after initialization of
device is done. This fixes the issue where fatal events were received
but ignored.
- Fix integer handling (static analysis warning).
- Always fetch HBM ECC errors from F/W (if available).
- Minor fix in GAUDI-specific initialization code.
----------------------------------------------------------------
Oded Gabbay (4):
habanalabs: fix integer handling issue
habanalabs: enable F/W events after init done
habanalabs: return block size + block ID
habanalabs/gaudi: don't enable clock gating on DMA5
Ofir Bitton (2):
habanalabs: improve communication protocol with cpucp
habanalabs: support fetching first available user CQ
Ohad Sharabi (2):
habanalabs/gaudi: use HBM_ECC_EN bit for ECC ERR
habanalabs: update security map after init CPU Qs
drivers/misc/habanalabs/common/device.c | 23 ++++++++--
drivers/misc/habanalabs/common/firmware_if.c | 14 ++++++-
drivers/misc/habanalabs/common/habanalabs.h | 15 +++++--
drivers/misc/habanalabs/common/habanalabs_ioctl.c | 3 +-
drivers/misc/habanalabs/common/memory.c | 19 +++++----
drivers/misc/habanalabs/common/mmu/mmu.c | 2 +-
drivers/misc/habanalabs/gaudi/gaudi.c | 49 ++++++++++++++++++----
drivers/misc/habanalabs/goya/goya.c | 27 +++++++++---
.../misc/habanalabs/include/common/hl_boot_if.h | 5 +++
include/uapi/misc/habanalabs.h | 30 ++++++++++---
10 files changed, 148 insertions(+), 39 deletions(-)
next reply other threads:[~2021-02-08 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 16:30 Oded Gabbay [this message]
2021-02-09 8:34 ` Greg KH
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=20210208163022.GA5745@CORE.localdomain \
--to=ogabbay@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®