All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	jdelvare@suse.com, arnd@arndb.de, linux-doc@vger.kernel.org,
	andrew@aj.id.au, gregkh@linuxfoundation.org,
	openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	joel@jms.id.au, linux-arm-kernel@lists.infradead.org
Subject: Re: [linux, dev-4.10, 6/6] drivers/hwmon: Add a driver for a generic PECI hwmon
Date: Thu, 11 Jan 2018 16:26:05 -0800	[thread overview]
Message-ID: <4bf64613-890f-c800-a065-bb070bcc5a37@linux.intel.com> (raw)
In-Reply-To: <20180111235346.GA13443@lunn.ch>

On 1/11/2018 3:53 PM, Andrew Lunn wrote:
> On Thu, Jan 11, 2018 at 03:14:37PM -0800, Jae Hyun Yoo wrote:
>> 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.
> 
> Hi Jae
> 
> You need to be careful with the name then. You should not claim the
> name 'peci' in case somebody actually implements a PECI driver which
> is compatible with Intel PECI.
> 
> However, looking at other comments, it seems like this part is going
> away, if you turn your code into a bus driver.
> 
>        Andrew
> 

Hi Andrew,

I see. I'll keep that in mind and will keep finding if there is any 
better way. Thanks for sharing your thought.

Jae

WARNING: multiple messages have this Message-ID (diff)
From: jae.hyun.yoo@linux.intel.com (Jae Hyun Yoo)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux, dev-4.10, 6/6] drivers/hwmon: Add a driver for a generic PECI hwmon
Date: Thu, 11 Jan 2018 16:26:05 -0800	[thread overview]
Message-ID: <4bf64613-890f-c800-a065-bb070bcc5a37@linux.intel.com> (raw)
In-Reply-To: <20180111235346.GA13443@lunn.ch>

On 1/11/2018 3:53 PM, Andrew Lunn wrote:
> On Thu, Jan 11, 2018 at 03:14:37PM -0800, Jae Hyun Yoo wrote:
>> 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.
> 
> Hi Jae
> 
> You need to be careful with the name then. You should not claim the
> name 'peci' in case somebody actually implements a PECI driver which
> is compatible with Intel PECI.
> 
> However, looking at other comments, it seems like this part is going
> away, if you turn your code into a bus driver.
> 
>        Andrew
> 

Hi Andrew,

I see. I'll keep that in mind and will keep finding if there is any 
better way. Thanks for sharing your thought.

Jae

  reply	other threads:[~2018-01-12  0:26 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:31 [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Jae Hyun Yoo
2018-01-09 22:31 ` Jae Hyun Yoo
2018-01-09 22:31 ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 1/6] Documentation: dt-bindings: Add Aspeed PECI Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 2/6] ARM: dts: aspeed: peci: " Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 3/6] drivers/misc: Add driver for Aspeed PECI and generic PECI headers Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-10 10:18   ` Greg KH
2018-01-10 10:18     ` Greg KH
2018-01-10 10:18     ` Greg KH
2018-01-10 19:32     ` Jae Hyun Yoo
2018-01-10 19:32       ` Jae Hyun Yoo
2018-01-11  9:02     ` Benjamin Herrenschmidt
2018-01-11  9:02       ` Benjamin Herrenschmidt
2018-01-11  9:02       ` Benjamin Herrenschmidt
2018-01-11 20:33       ` Jae Hyun Yoo
2018-01-11 20:33         ` Jae Hyun Yoo
2018-01-10 10:20   ` Greg KH
2018-01-10 10:20     ` Greg KH
2018-01-10 10:20     ` Greg KH
2018-01-10 19:34     ` Jae Hyun Yoo
2018-01-10 19:34       ` Jae Hyun Yoo
2018-01-10 11:55   ` Arnd Bergmann
2018-01-10 11:55     ` Arnd Bergmann
2018-01-10 11:55     ` Arnd Bergmann
2018-01-10 23:11     ` Jae Hyun Yoo
2018-01-10 23:11       ` Jae Hyun Yoo
2018-01-11  9:06   ` Benjamin Herrenschmidt
2018-01-11  9:06     ` Benjamin Herrenschmidt
2018-01-11  9:06     ` Benjamin Herrenschmidt
2018-01-11 20:42     ` Jae Hyun Yoo
2018-01-11 20:42       ` Jae Hyun Yoo
2018-01-11 20:42       ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 4/6] Documentation: dt-bindings: Add a generic PECI hwmon Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-10 12:20   ` Arnd Bergmann
2018-01-10 12:20     ` Arnd Bergmann
2018-01-10 12:20     ` Arnd Bergmann
2018-01-10 23:20     ` Jae Hyun Yoo
2018-01-10 23:20       ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 5/6] Documentation: hwmon: " Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-09 22:31 ` [PATCH linux dev-4.10 6/6] drivers/hwmon: Add a driver for " Jae Hyun Yoo
2018-01-09 22:31   ` Jae Hyun Yoo
2018-01-10 12:29   ` Arnd Bergmann
2018-01-10 12:29     ` Arnd Bergmann
2018-01-10 12:29     ` Arnd Bergmann
2018-01-10 23:45     ` Jae Hyun Yoo
2018-01-10 23:45       ` Jae Hyun Yoo
2018-01-11 13:22       ` Arnd Bergmann
2018-01-11 13:22         ` Arnd Bergmann
2018-01-11 13:22         ` Arnd Bergmann
2018-01-11 20:49         ` Jae Hyun Yoo
2018-01-11 20:49           ` Jae Hyun Yoo
2018-01-10 21:47   ` [linux, dev-4.10, " Guenter Roeck
2018-01-10 21:47     ` Guenter Roeck
2018-01-11 19:47     ` Jae Hyun Yoo
2018-01-11 19:47       ` Jae Hyun Yoo
2018-01-11 19:47       ` Jae Hyun Yoo
2018-01-11 21:40       ` Guenter Roeck
2018-01-11 21:40         ` Guenter Roeck
2018-01-11 22:18         ` Andrew Lunn
2018-01-11 22:18           ` Andrew Lunn
2018-01-11 22:18           ` Andrew Lunn
2018-01-11 23:14           ` Jae Hyun Yoo
2018-01-11 23:14             ` Jae Hyun Yoo
2018-01-11 23:53             ` Andrew Lunn
2018-01-11 23:53               ` Andrew Lunn
2018-01-12  0:26               ` Jae Hyun Yoo [this message]
2018-01-12  0:26                 ` Jae Hyun Yoo
2018-01-11 23:03         ` Jae Hyun Yoo
2018-01-11 23:03           ` Jae Hyun Yoo
2018-01-11 23:03           ` Jae Hyun Yoo
2018-01-10 10:17 ` [PATCH linux dev-4.10 0/6] Add support PECI and PECI hwmon drivers Greg KH
2018-01-10 10:17   ` Greg KH
2018-01-10 10:17   ` Greg KH
2018-01-10 19:14   ` Jae Hyun Yoo
2018-01-10 19:14     ` Jae Hyun Yoo
2018-01-10 19:17     ` Greg KH
2018-01-10 19:17       ` Greg KH
2018-01-10 19:17       ` Greg KH
2018-01-10 19:30       ` Jae Hyun Yoo
2018-01-10 19:30         ` Jae Hyun Yoo
2018-01-10 20:27         ` Greg KH
2018-01-10 20:27           ` Greg KH
2018-01-10 20:27           ` Greg KH
2018-01-10 21:46           ` Jae Hyun Yoo
2018-01-10 21:46             ` Jae Hyun Yoo
2018-01-10 21:46             ` Jae Hyun Yoo
2018-01-11  7:30             ` Greg KH
2018-01-11  7:30               ` Greg KH
2018-01-11  8:28               ` Joel Stanley
2018-01-11  8:28                 ` Joel Stanley
2018-01-11  8:28                 ` Joel Stanley
2018-01-11  8:41                 ` Greg KH
2018-01-11  8:41                   ` Greg KH
2018-01-11  8:41                   ` Greg KH
2018-01-11  9:17                   ` Arnd Bergmann
2018-01-11  9:17                     ` Arnd Bergmann
2018-01-11  9:17                     ` Arnd Bergmann
2018-01-11  9:17                     ` Arnd Bergmann
2018-01-11  9:21                   ` Benjamin Herrenschmidt
2018-01-11  9:21                     ` Benjamin Herrenschmidt
2018-01-11  9:21                     ` Benjamin Herrenschmidt
2018-01-11  8:56               ` Benjamin Herrenschmidt
2018-01-11  8:56                 ` Benjamin Herrenschmidt
2018-01-11  9:59                 ` Greg KH
2018-01-11  9:59                   ` Greg KH
2018-01-11  9:59                   ` Greg KH
2018-01-11 20:49                   ` Benjamin Herrenschmidt
2018-01-11 20:49                     ` Benjamin Herrenschmidt
2018-01-11 20:49                     ` Benjamin Herrenschmidt
2018-01-11 19:54                 ` Jae Hyun Yoo
2018-01-11 19:54                   ` Jae Hyun Yoo

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=4bf64613-890f-c800-a065-bb070bcc5a37@linux.intel.com \
    --to=jae.hyun.yoo@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdelvare@suse.com \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=openbmc@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.