Note: This is a resend, my email client decided to
Change my paragraph format with 70 char lines.
Apologies.
Greetings Guenter,
> > +static bool fan_installed(struct device *dev, int fan) {
> > + struct gxp_fan_ctrl_drvdata *drvdata = dev_get_drvdata(dev);
> > + u32 trans_offset;
> > + u32 trans_shift;
> > + u32 val;
> > +
> > + address_translation(drvdata->data->fan[fan].inst,
> > + &trans_offset,
> > + &trans_shift);
> > +
> > + regmap_read(drvdata->plreg_map, trans_offset, &val);
> > + val = (val >> trans_shift) & drvdata->data->fan[fan].bit;
> > + if (val == drvdata->data->fan[fan].bit)
> > + return 1;
> > + else
> > + return 0;
> return val == drvdata->data->fan[fan].bit;
> Those calculations look quite complex. Is there a public datasheet that would enable me to understand how registers are actually assigned ?
There is no public datasheet as of yet but there is work ongoing to
create one. I will however document exactly how it is setup in hwmon.
There is so much I/O on our board that most of the inputs and outputs
go through an external CPLD we are interfaced with to save pins. A
memory area in our SoC reflects some of the I/O from CPLD in bytes
ranging from 0 to 0xff. Each byte represents information such as byte
0x27, which on this particular platform represents the fan installation
status of fans 0 to 7 respectively with bit 0 to 7. The byte 0x28 represents
something else. Regmap_read/write does a word instead of a single byte
which we are interested in so we use address_translation to keep offsets
easier to read.
> > + } else {
> > + /* Power Off */
> > + val = 0;
> > + }
> What determines power to a fan ? Should the power state be reported with fanX_enable ? Or possibly the installed state ?
This actually is the power state of the system, not the fan. When the
system is off we will see a PWM value of 0xFF on the fan. The idea
here was to report a value of 0 if the system was off.
Would you like me to use fanX_enable (read only) to show it as
disabled while the system is off ?
>From a hardware standpoint that would be accurate.
> > +static const struct fan_ctrl_data g10_data = {
> > + .fan[0] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x01 },
> > + .fan[1] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x02 },
> > + .fan[2] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x04 },
> > + .fan[3] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x08 },
> > + .fan[4] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x10 },
> > + .fan[5] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x20 },
> > + .fan[6] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x40 },
> > + .fan[7] = { .inst = 0x00, .fail = 0x02, .id = 0x04, .bit = 0x80 },
> > + .fan[8] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x01 },
> > + .fan[9] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x02 },
> > + .fan[10] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x04 },
> > + .fan[11] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x08 },
> > + .fan[12] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x10 },
> > + .fan[13] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x20 },
> > + .fan[14] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x40 },
> > + .fan[15] = { .inst = 0x01, .fail = 0x03, .id = 0x05, .bit = 0x80 },
> > + .power_bit = 24,
> > +};
> > +
> > +static const struct of_device_id gxp_fan_ctrl_of_match[] = {
> > + { .compatible = "hpe,gxp-fan-ctrl", .data = &g10_data },
> I don't understand the point of attaching g10_data here.
> Why not just access it directly ? There is just one table.
The reason for having this data with the of_device_id binding is that
each platform has different byte offsets as mentioned above. We
would like to be able to reuse the driver if possible for this. We will
soon need g11_data that will be added here. Would a description in
Documentation, comments and commit message allow us to keep
this ?
Thank you for your assistance and feedback with this code,
-Nick Hawkins
