[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <463412a8-ad34-264d-0f44-bd383f100b44@linux.intel.com>
Date: Thu, 11 Jan 2018 15:14:37 -0800
From: Jae Hyun Yoo <jae.hyun.yoo@...ux.intel.com>
To: Andrew Lunn <andrew@...n.ch>, Guenter Roeck <linux@...ck-us.net>
Cc: linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
jdelvare@...e.com, arnd@...db.de, linux-doc@...r.kernel.org,
andrew@...id.au, gregkh@...uxfoundation.org,
openbmc@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
joel@....id.au, linux-arm-kernel@...ts.infradead.org
Subject: Re: [linux, dev-4.10, 6/6] drivers/hwmon: Add a driver for a generic
PECI hwmon
On 1/11/2018 2:18 PM, Andrew Lunn wrote:
>>>>> +static const struct of_device_id peci_of_table[] = {
>>>>> + { .compatible = "peci-hwmon", },
>>>>
>>>> This does not look like a reference to some piece of hardware.
>>>>
>>>
>>> This driver provides generic PECI hwmon function to which controller has
>>> PECI HW such as Aspeed or Nuvoton BMC chip so it's not dependant on a
>>> specific hardware. Should I remove this or any suggestion?
>
> PECI seems to be an Intel thing. So at least it should be
>
> { .compatible = "intel,peci-hwmon", }
>
> assuming it is actually compatible with the Intel specification.
>
> Andrew
>
Yes, PECI is an Intel thing but this driver is running on an ARM kernel
on Aspeed or Nuvoton chipsets for now. This driver will be monitoring a
host server's Intel CPU and DIMM which is running on a separated OS.
Thanks,
Jae
Powered by blists - more mailing lists