public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <ogabbay@kernel.org>
To: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Cc: SW_Drivers@habana.ai
Subject: [PATCH 0/4] Enable support of GAUDI NIC QMANs
Date: Tue,  3 Nov 2020 08:06:57 +0200	[thread overview]
Message-ID: <20201103060701.25852-1-ogabbay@kernel.org> (raw)

This patch-set initializes the GAUDI compute queues which are connected
to the NIC ports. It also configures the security properties of those
queues.

This is the pretty much the same code as the one that configures the
rest of the queues in GAUDI.

I want to emphasize that there is no networking/ethernet/RDMA code in
this patch-set. Those features will be supported in later patch-sets
according to the feedback that was received from the community.

This patch-set is pre-requisite for those later patch-sets and also for
additional features we want to upstream to the driver, such as collective
wait mechanism.

Thanks,
Oded

Oded Gabbay (4):
  habanalabs/gaudi: add NIC QMAN H/W and registers definitions
  habanalabs/gaudi: add NIC firmware-related definitions
  habanalabs/gaudi: add NIC security configuration
  habanalabs/gaudi: add support for NIC QMANs

 drivers/misc/habanalabs/common/habanalabs.h   |    3 +-
 drivers/misc/habanalabs/gaudi/gaudi.c         |  741 ++-
 drivers/misc/habanalabs/gaudi/gaudiP.h        |   32 +
 .../misc/habanalabs/gaudi/gaudi_security.c    | 3973 +++++++++++++++++
 .../misc/habanalabs/include/common/cpucp_if.h |   34 +-
 .../include/gaudi/asic_reg/gaudi_regs.h       |   14 +-
 .../include/gaudi/asic_reg/nic0_qm0_masks.h   |  800 ++++
 .../include/gaudi/asic_reg/nic0_qm0_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic0_qm1_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic1_qm0_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic1_qm1_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic2_qm0_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic2_qm1_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic3_qm0_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic3_qm1_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic4_qm0_regs.h    |  834 ++++
 .../include/gaudi/asic_reg/nic4_qm1_regs.h    |  834 ++++
 .../habanalabs/include/gaudi/gaudi_fw_if.h    |   24 +
 .../habanalabs/include/gaudi/gaudi_masks.h    |   15 +
 19 files changed, 13926 insertions(+), 50 deletions(-)
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic0_qm0_masks.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic0_qm0_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic0_qm1_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic1_qm0_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic1_qm1_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic2_qm0_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic2_qm1_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic3_qm0_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic3_qm1_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic4_qm0_regs.h
 create mode 100644 drivers/misc/habanalabs/include/gaudi/asic_reg/nic4_qm1_regs.h

--
2.17.1


             reply	other threads:[~2020-11-03  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  6:06 Oded Gabbay [this message]
2020-11-03  6:06 ` [PATCH 1/4] habanalabs/gaudi: add NIC QMAN H/W and registers definitions Oded Gabbay
2020-11-03  6:06 ` [PATCH 2/4] habanalabs/gaudi: add NIC firmware-related definitions Oded Gabbay
2020-11-03  6:07 ` [PATCH 3/4] habanalabs/gaudi: add NIC security configuration Oded Gabbay
2020-11-03  6:07 ` [PATCH 4/4] habanalabs/gaudi: add support for NIC QMANs Oded Gabbay

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=20201103060701.25852-1-ogabbay@kernel.org \
    --to=ogabbay@kernel.org \
    --cc=SW_Drivers@habana.ai \
    --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