On 3/21/19 4:59 AM, Charles Keepax wrote:
On Wed, Mar 20, 2019 at 09:40:10AM -0700, Guenter Roeck wrote:
On Wed, Mar 20, 2019 at 02:58:18PM +0000, Charles Keepax wrote:
From: Lucas Tanure <tanureal@xxxxxxxxxxxxxxxxxxxxx>
Lochnagar is an evaluation and development board for Cirrus
Logic Smart CODEC and Amp devices. It allows the connection of
most Cirrus Logic devices on mini-cards, as well as allowing
connection of various application processor systems to provide a
full evaluation platform.
This driver adds support for the hardware monitoring features of
the Lochnagar 2 to the hwmon API. Monitoring is provided for
the board voltages, currents and temperature supported by the
board controller chip.
Signed-off-by: Lucas Tanure <tanureal@xxxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxx>
---
+#include <linux/of_device.h>
+#include <linux/i2c.h>
+#include <asm/div64.h>
+
Alphabetic order, please. Also, please include linux/math64.h
instead of asm/div64.h.
+struct lochnagar_hwmon {
+ struct lochnagar *lochnagar;
The only use of this structure is to dereference regmap from it.
Please replace it with a pointer to struct regmap.
+
+ /* Lock to ensure only a single sensor is read at a time */
+ struct mutex sensor_lock;
+ struct device *hwmon_dev;
Not used anywhere.
+static u64 float_to_int(u32 data, u32 precision)
A return type of 'long' would make more sense. Also see below.
Yup will get those all fixed up.
+{
+ s64 man = data & 0x007FFFFF;
+ s32 exp = ((data & 0x7F800000) >> 23) - 127 - 23;
+ bool negative = data & 0x80000000;
+
+ man = (man + (1 << 23)) * precision;
+
+ if (exp > 0)
+ man <<= exp;
+ else if (exp < 0)
+ man >>= -exp;
+
Is this an ieee754 floating point format ? Please add a comment stating it.
Also, if the format supports it, please check for NaN. If the HW guarantees
to never return NaN, please add a respective comment.
How likely is it that the values overflow ? A precision multipler of
1,000,000,000 means that numbers will overflow quite easily. And does
the the hardware really report voltages and currents in pico-units,
and are temperatures really reported in micro-degrees C ?
I believe the hardware can't return NaN. But will check that,
what ranges are possible and add some overflow checking.
How about the units ? Maybe add a note explaining what the HW actually returns.
Overall it might make sense to reconfigure the hardware into continuous
measurement mode and get rid of the delays (if that can be configured -
the user guide isn't detailed enough to be able to determine for sure).
After all, it is quite unlikely that the board will be used in an
environment where the power savings would be worth the inconvenience
of having to wait more than two seconds for a set of measurement values
(adding all the current and temperature delays up).
Yeah the hardware is quite slow and regrettably doesn't have a
continuous measurement mode. We could potentially add a thread to
poll them but mostly the usage for this data is just taking power
measurements of various audio use-cases so the large delay isn't
a huge problem and not sure it warrents the additional
complexity.
+ msleep(nsamples);
+
This needs some explanation how nsamples translates into millisecond waits,
especially since that wait can add up significantly (reading the temperature
will take forever, as will reading all currents).
+ ret = regmap_read_poll_timeout(regmap, LOCHNAGAR2_IMON_CTRL3, val,
+ val & LOCHNAGAR2_IMON_DONE_MASK,
+ 5000, 2000000);
Can that indeed take another two seconds on top of the sleep above ?
It does about about 1.5-2 seconds I think last time I checked.
Essentially the hardware will average a number of readings and
return that. The number of readings given in the driver is what
the hardware guys recommended for each, that said we could
potentially make it configurable if that helps at all? Also
I could get the msleep a bit closer to the actual runtime,
just need to check how linear the time is with the number of
samples take (I assume very).
Brr. Just add a note explaining that the long times are indeed intentional,
and that the HW takes that long.
Thanks,
Guenter
+static int lochnagar_hwmon_probe(struct platform_device *pdev)
+{
+ struct device *dev = &pdev->dev;
+ struct lochnagar *lochnagar = dev_get_drvdata(dev->parent);
+ struct lochnagar_hwmon *priv;
+
It might make sense to add a check to ensure that lochnagar is not NULL.
Can do.
Thanks,
Charles
