Hi Randy,

On 7/23/2018 3:21 PM, Randy Dunlap wrote:

On 07/23/2018 02:47 PM, Jae Hyun Yoo wrote:

quoted

This commit adds PECI client MFD driver.

Signed-off-by: Jae Hyun Yoo <redacted>
Cc: Lee Jones <redacted>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Andrew Jeffery <redacted>
Cc: James Feist <redacted>
Cc: Jason M Biils <redacted>
Cc: Joel Stanley <joel@jms.id.au>
Cc: Vernon Mauery <redacted>
---
  drivers/mfd/Kconfig                   |  14 ++
  drivers/mfd/Makefile                  |   1 +
  drivers/mfd/intel-peci-client.c       | 182 ++++++++++++++++++++++++++
  include/linux/mfd/intel-peci-client.h |  81 ++++++++++++
  4 files changed, 278 insertions(+)
  create mode 100644 drivers/mfd/intel-peci-client.c
  create mode 100644 include/linux/mfd/intel-peci-client.h

diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index f3fa516011ec..e38b591479d4 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig

@@ -595,6 +595,20 @@ config MFD_INTEL_MSIC
  	  Passage) chip. This chip embeds audio, battery, GPIO, etc.
  	  devices used in Intel Medfield platforms.
  
+config MFD_INTEL_PECI_CLIENT
+	bool "Intel PECI client"
+	depends on (PECI || COMPILE_TEST)
+	select MFD_CORE
+	help
+	  If you say yes to this option, support will be included for the
+	  multi-funtional Intel PECI (Platform Environment Control Interface)

	  multi-functional

Thanks for your pointing it out. Will fix it.

Thanks,

Jae

quoted

+	  client. PECI is a one-wire bus interface that provides a communication
+	  channel from PECI clients in Intel processors and chipset components
+	  to external monitoring or control devices.
+
+	  Additional drivers must be enabled in order to use the functionality
+	  of the device.
+
  config MFD_IPAQ_MICRO
  	bool "Atmel Micro ASIC (iPAQ h3100/h3600/h3700) Support"
  	depends on SA1100_H3100 || SA1100_H3600