linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tianfei Zhang <tianfei.zhang@intel.com>
To: yilun.xu@intel.com, lee.jones@linaro.org
Cc: hao.wu@intel.com, trix@redhat.com, linux-kernel@vger.kernel.org,
	linux-fpga@vger.kernel.org, russell.h.weight@intel.com,
	matthew.gerlach@linux.intel.com,
	Tianfei Zhang <tianfei.zhang@intel.com>
Subject: [PATCH v3 0/3] add PMCI driver support
Date: Fri, 24 Jun 2022 05:22:26 -0400	[thread overview]
Message-ID: <20220624092229.45854-1-tianfei.zhang@intel.com> (raw)

PMCI(Platform Management Control Interface) is a software-visible
interface, connected to card BMC which provided basic register
access functionality from host to Card BMC. This pmci-bmc driver
leverages the regmap APIs to support Intel specific Indirect
Register Interface for register read/write on PMCI driver. 

This patchset adding a driver for the PMCI-base interface of Intel
MAX10 BMC controller.

patch 1: use ddata for local variables which directly interacts with
dev_get_drvdata()/dev_set_drvdata().
patch 2: add a driver for PMCI.
patch 3: introduce a new member in intel_m10bmc for the different
base register address of MAX10 CSRs.

v3:
  - create a new intel-m10-bmc-pmci driver, and discard the bmc-core
    file which adds in v2.
  - create a new file for sysfs-driver-intel-m10-bmc-pmci ABI.
  - remove the regmap_access_table
  - introduce a new member "base" in intel_m10bmc for different base
    register address.
  - rebased on 5.19-rc3
v2:
  - use regmap APIs to support Intel specific Indirect Register Interface
    on PMCI driver.
  - fix compile warning reported by lkp.
  - rebased on 5.19-rc2

Tianfei Zhang (3):
  mfd: intel-m10-bmc: rename the local variables
  mfd: intel-m10-bmc: add PMCI driver
  mfd: intel-m10-bmc: support different BMC base register address

 .../testing/sysfs-driver-intel-m10-bmc-pmci   |  36 +++
 drivers/mfd/Kconfig                           |  10 +
 drivers/mfd/Makefile                          |   1 +
 drivers/mfd/intel-m10-bmc-pmci.c              | 278 ++++++++++++++++++
 drivers/mfd/intel-m10-bmc.c                   |  11 +-
 include/linux/mfd/intel-m10-bmc.h             |  12 +-
 6 files changed, 342 insertions(+), 6 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-pmci
 create mode 100644 drivers/mfd/intel-m10-bmc-pmci.c

-- 
2.26.2


             reply	other threads:[~2022-06-24  9:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  9:22 Tianfei Zhang [this message]
2022-06-24  9:22 ` [PATCH v3 1/3] mfd: intel-m10-bmc: rename the local variables Tianfei Zhang
2022-06-25 13:28   ` Tom Rix
2022-06-27  8:04     ` Lee Jones
2022-06-24  9:22 ` [PATCH v3 2/3] mfd: intel-m10-bmc: add PMCI driver Tianfei Zhang
2022-06-25 13:52   ` Tom Rix
2022-06-27 14:03     ` Zhang, Tianfei
2022-06-27 16:30       ` Xu Yilun
2022-06-28  3:51         ` Zhang, Tianfei
2022-06-24  9:22 ` [PATCH v3 3/3] mfd: intel-m10-bmc: support different BMC base register address Tianfei Zhang

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=20220624092229.45854-1-tianfei.zhang@intel.com \
    --to=tianfei.zhang@intel.com \
    --cc=hao.wu@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=russell.h.weight@intel.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@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 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).