linux-kernel - [PATCH v3 0/2] add Intel MAX 10 BMC MFD driver & hwmon sub driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1600669071-26235-1-git-send-email-yilun.xu@intel.com>
Date:   Mon, 21 Sep 2020 14:17:49 +0800
From:   Xu Yilun <yilun.xu@...el.com>
To:     lee.jones@...aro.org, linux@...ck-us.net, jdelvare@...e.com,
        linux-hwmon@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     trix@...hat.com, yilun.xu@...el.com,
        matthew.gerlach@...ux.intel.com, russell.h.weight@...el.com,
        lgoncalv@...hat.com, hao.wu@...el.com, mdf@...nel.org
Subject: [PATCH v3 0/2] add Intel MAX 10 BMC MFD driver & hwmon sub driver

I recently realized that maintainers may have trouble to apply patches to
their trees if the patches depend on other being-reviewed patches. So I'm
trying to wrapper the 2 patches into one patchset and let all the
maintainers see the dependencies.

But the patch version is then not aligned between the 2 patches. I'm not
sure how to handle it. I just picked the smaller number on Subject, but
you could still see their own version changes in commit message of each
patch. Sorry if it makes confusing.

Patch #1 implements the basic functions of the BMC chip for some Intel
FPGA PCIe Acceleration Cards (PAC). The BMC is implemented using the
Intel MAX 10 CPLD.

This BMC chip is connected to the FPGA by a SPI bus. To provide direct
register access from the FPGA, the "SPI slave to Avalon Master Bridge"
(spi-avmm) IP is integrated in the chip. It converts encoded streams of
bytes from the host to the internal register read/write on the Avalon
bus. So This driver uses the regmap-spi-avmm for register accessing.

Patch #2 adds support for the hwmon sub device in Intel MAX 10 BMC

Xu Yilun (2):
  mfd: intel-m10-bmc: add Intel MAX 10 BMC chip support for Intel FPGA
    PAC
  hwmon: intel-m10-bmc-hwmon: add hwmon support for Intel MAX 10 BMC

 .../ABI/testing/sysfs-driver-intel-m10-bmc         |  15 +
 Documentation/hwmon/index.rst                      |   1 +
 Documentation/hwmon/intel-m10-bmc-hwmon.rst        |  78 +++++
 drivers/hwmon/Kconfig                              |  11 +
 drivers/hwmon/Makefile                             |   1 +
 drivers/hwmon/intel-m10-bmc-hwmon.c                | 334 +++++++++++++++++++++
 drivers/mfd/Kconfig                                |  13 +
 drivers/mfd/Makefile                               |   2 +
 drivers/mfd/intel-m10-bmc.c                        | 164 ++++++++++
 include/linux/mfd/intel-m10-bmc.h                  |  65 ++++
 10 files changed, 684 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-driver-intel-m10-bmc
 create mode 100644 Documentation/hwmon/intel-m10-bmc-hwmon.rst
 create mode 100644 drivers/hwmon/intel-m10-bmc-hwmon.c
 create mode 100644 drivers/mfd/intel-m10-bmc.c
 create mode 100644 include/linux/mfd/intel-m10-bmc.h

-- 
2.7.4