netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	petrm@nvidia.com, jiri@nvidia.com, vadimp@nvidia.com,
	mlxsw@nvidia.com, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 0/8] mlxsw: Extend device registers for line cards support
Date: Mon, 11 Apr 2022 17:46:49 +0300	[thread overview]
Message-ID: <20220411144657.2655752-1-idosch@nvidia.com> (raw)

This patch set prepares mlxsw for line cards support by extending device
registers with a slot index, which allows accessing components found on
a line card at a given slot. Currently, only slot index 0 (main board)
is used.

No user visible changes that I am aware of.

The next patchsets will:

1. Extend internal mlxsw interfaces and data structures for line cards
support
2. Add line cards support in devlink and mlxsw_spectrum
3. Add hwmon/thermal support for components found on line cards
4. Extend devlink to expose line card info (e.g., HW revision) and
devices found on line cards (e.g., gearboxes)
5. Extend devlink with the ability to flash devices found on line cards
6. Add line cards support in mlxsw_minimal

Vadim Pasternak (8):
  mlxsw: reg: Extend MTMP register with new slot number field
  mlxsw: reg: Extend MTBR register with new slot number field
  mlxsw: reg: Extend MCIA register with new slot number field
  mlxsw: reg: Extend MCION register with new slot number field
  mlxsw: reg: Extend PMMP register with new slot number field
  mlxsw: reg: Extend MGPIR register with new slot fields
  mlxsw: core_env: Pass slot index during PMAOS register write call
  mlxsw: reg: Add new field to Management General Peripheral Information
    Register

 .../net/ethernet/mellanox/mlxsw/core_env.c    | 33 ++++----
 .../net/ethernet/mellanox/mlxsw/core_hwmon.c  | 24 +++---
 .../ethernet/mellanox/mlxsw/core_thermal.c    | 14 ++--
 drivers/net/ethernet/mellanox/mlxsw/reg.h     | 83 ++++++++++++++++---
 4 files changed, 108 insertions(+), 46 deletions(-)

-- 
2.33.1


             reply	other threads:[~2022-04-11 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 14:46 Ido Schimmel [this message]
2022-04-11 14:46 ` [PATCH net-next 1/8] mlxsw: reg: Extend MTMP register with new slot number field Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 2/8] mlxsw: reg: Extend MTBR " Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 3/8] mlxsw: reg: Extend MCIA " Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 4/8] mlxsw: reg: Extend MCION " Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 5/8] mlxsw: reg: Extend PMMP " Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 6/8] mlxsw: reg: Extend MGPIR register with new slot fields Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 7/8] mlxsw: core_env: Pass slot index during PMAOS register write call Ido Schimmel
2022-04-11 14:46 ` [PATCH net-next 8/8] mlxsw: reg: Add new field to Management General Peripheral Information Register Ido Schimmel
2022-04-12 17:00 ` [PATCH net-next 0/8] mlxsw: Extend device registers for line cards support patchwork-bot+netdevbpf

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=20220411144657.2655752-1-idosch@nvidia.com \
    --to=idosch@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=vadimp@nvidia.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).