[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <87609nxfym.fsf@linux.vnet.ibm.com>
Date: Mon, 04 Dec 2017 15:41:21 +1100
From: Stewart Smith <stewart@...ux.vnet.ibm.com>
To: Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
linuxppc-dev@...ts.ozlabs.org
Cc: linux-kernel@...r.kernel.org, ego@...ux.vnet.ibm.com,
akshay.adiga@...ux.vnet.ibm.com, svaidy@...ux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/powernv : Add support to enable sensor groups
Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com> writes:
> On 11/28/2017 05:07 PM, Michael Ellerman wrote:
>> Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com> writes:
>>
>>> Adds support to enable/disable a sensor group. This can be used to
>>> select the sensor groups that needs to be copied to main memory by
>>> OCC. Sensor groups like power, temperature, current, voltage,
>>> frequency, utilization can be enabled/disabled at runtime.
>>>
>>> Signed-off-by: Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>
>>> ---
>>> The skiboot patch for the opal call is posted below:
>>> https://lists.ozlabs.org/pipermail/skiboot/2017-November/009713.html
>>
>> Can you remind me why we're doing this with a completely bespoke sysfs
>> API, rather than using some generic sensors API?
>>
>
> Disabling/Enabling sensor groups is not supported in the current generic sensors
> API. And also we dont export all type of sensors in HWMON as not all of them are
> environment sensors (like performance).
Are there barriers to adding such concepts to the generic sensors API?
--
Stewart Smith
OPAL Architect, IBM.
Powered by blists - more mailing lists