From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
linux@roeck-us.net, stewart@linux.vnet.ibm.com
Cc: jdelvare@suse.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, svaidy@linux.vnet.ibm.com,
ego@linux.vnet.ibm.com, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH V2 1/2] hwmon: (ibmpowernv) introduce a legacy_compatibles array
Date: Tue, 20 Jun 2017 12:45:00 +0530 [thread overview]
Message-ID: <5cc575c8-246c-9559-e990-348b13e9ddd3@linux.vnet.ibm.com> (raw)
In-Reply-To: <3b82267d-c647-d523-12d8-496378ab240b@kaod.org>
On 06/20/2017 11:36 AM, Cédric Le Goater wrote:
> On 06/20/2017 07:08 AM, Shilpasri G Bhat wrote:
>> From: Cédric Le Goater <clg@kaod.org>
>>
>> Today, the type of a PowerNV sensor system is determined with the
>> "compatible" property for legacy Firmwares and with the "sensor-type"
>> for newer ones. The same array of strings is used for both to do the
>> matching and this raises some issue to introduce new sensor types.
>>
>> Let's introduce two different arrays (legacy and current) to make
>> things easier for new sensor types.
>>
>> Signed-off-by: Cédric Le Goater <clg@kaod.org>
>> Tested-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
>
> Did you test on a Tuleta (IBM Power) system ?
I have tested this patch on P9 FSP and Firestone.
>
> Thanks,
>
> C.
>
>> ---
>> drivers/hwmon/ibmpowernv.c | 26 ++++++++++++++++++--------
>> 1 file changed, 18 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/hwmon/ibmpowernv.c b/drivers/hwmon/ibmpowernv.c
>> index 862b832..6d8909c 100644
>> --- a/drivers/hwmon/ibmpowernv.c
>> +++ b/drivers/hwmon/ibmpowernv.c
>> @@ -55,17 +55,27 @@ enum sensors {
>>
>> #define INVALID_INDEX (-1U)
>>
>> +/*
>> + * 'compatible' string properties for sensor types as defined in old
>> + * PowerNV firmware (skiboot). These are ordered as 'enum sensors'.
>> + */
>> +static const char * const legacy_compatibles[] = {
>> + "ibm,opal-sensor-cooling-fan",
>> + "ibm,opal-sensor-amb-temp",
>> + "ibm,opal-sensor-power-supply",
>> + "ibm,opal-sensor-power"
>> +};
>> +
>> static struct sensor_group {
>> - const char *name;
>> - const char *compatible;
>> + const char *name; /* matches property 'sensor-type' */
>> struct attribute_group group;
>> u32 attr_count;
>> u32 hwmon_index;
>> } sensor_groups[] = {
>> - {"fan", "ibm,opal-sensor-cooling-fan"},
>> - {"temp", "ibm,opal-sensor-amb-temp"},
>> - {"in", "ibm,opal-sensor-power-supply"},
>> - {"power", "ibm,opal-sensor-power"}
>> + { "fan" },
>> + { "temp" },
>> + { "in" },
>> + { "power" }
>> };
>>
>> struct sensor_data {
>> @@ -239,8 +249,8 @@ static int get_sensor_type(struct device_node *np)
>> enum sensors type;
>> const char *str;
>>
>> - for (type = 0; type < MAX_SENSOR_TYPE; type++) {
>> - if (of_device_is_compatible(np, sensor_groups[type].compatible))
>> + for (type = 0; type < ARRAY_SIZE(legacy_compatibles); type++) {
>> + if (of_device_is_compatible(np, legacy_compatibles[type]))
>> return type;
>> }
>>
>>
>
next prev parent reply other threads:[~2017-06-20 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 5:08 [PATCH V2 0/2] hwmon: (ibmpowernv) Add support for current(A) sensors Shilpasri G Bhat
2017-06-20 5:08 ` [PATCH V2 1/2] hwmon: (ibmpowernv) introduce a legacy_compatibles array Shilpasri G Bhat
2017-06-20 6:06 ` Cédric Le Goater
2017-06-20 7:15 ` Shilpasri G Bhat [this message]
2017-06-20 7:55 ` Cédric Le Goater
2017-06-20 5:08 ` [PATCH V2 2/2] hwmon: (ibmpowernv) Add current(A) sensor Shilpasri G Bhat
2017-06-20 6:05 ` Cédric Le Goater
2017-06-20 20:53 ` [PATCH V2 0/2] hwmon: (ibmpowernv) Add support for current(A) sensors Guenter Roeck
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=5cc575c8-246c-9559-e990-348b13e9ddd3@linux.vnet.ibm.com \
--to=shilpa.bhat@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=clg@kaod.org \
--cc=ego@linux.vnet.ibm.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=stewart@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome