Good morning Andy,
thank you again for the comprehensive feedback! Below I removed
everything but possible open points. I'll send v4 soon.
Best regards
Christian
On Thursday, 30 July 2020, 13:31:31 CEST, Andy Shevchenko wrote:
> On Thu, Jul 30, 2020 at 1:52 PM Christian Eggers <ceggers@xxxxxxx> wrote:
> > +/**
> > + * struct as73211_data - Instance data for one AS73211
> > + * @client: I2C client.
> > + * @osr: Cached Operational State Register.
> > + * @creg1: Cached Configuration Register 1.
> > + * @creg2: Cached Configuration Register 2.
> > + * @creg3: Cached Configuration Register 3.
> > + * @buffer: Buffer for triggered measurements.
> > + * @mutex: Keeps cached registers in synch with the device.
> > + * @completion: Completion to wait for interrupt.
> > + */
> > +struct as73211_data {
> > + struct i2c_client *client;
> > + u8 osr;
> > + u8 creg1;
> > + u8 creg2;
> > + u8 creg3;
> > + struct mutex mutex;
> > + struct completion completion;
> > +};
>
> Actually Jonathan is correct -- the above has kernel doc issues.
That's correct (the description for @buffer has to be removed). I didn't figure
out how to automatically check for this. When building with V=1 C=1, I only get
the message "as73211.c:76: info: Scanning doc for struct as73211_data".
> > +static unsigned int as73211_integration_time_us(struct as73211_data
> > *data)
> > +{
> > + /* Integration time has 15 steps, the step size depends on the
> > clock. */ + unsigned int mul = BIT(3 - (data->creg3 & GENMASK(1,
> > 0)));
> Shouldn't be rather
>
> #define FOO GENMASK(1, 0)
> mul = BIT(FOO - (creg & FOO));
>
> with a descriptive name of FOO?
>
> Or if both 3:s have different meaning, two definitions?
In my opinion, both 3:s have different meaning. The first is from an arbitrary
choosen mathematic transformation (like the 125). I've added appropriate
documentation for this.
> > +static unsigned int as73211_gain(struct as73211_data *data)
> > +{
> >
> > + return BIT(0xb - FIELD_GET(AS73211_CREG1_GAIN_MASK, data->creg1));
>
> Magic!
Similarly it's difficult to find an eligible alias for the 0xb as the
whole expression is constructed from viewing tables on the data sheet. I added
some comment.
> > + if (data->client->irq) {
> > + dev_dbg(dev, "Waiting for completion...\n");
> > + ret = wait_for_completion_timeout(&data->completion,
> >
> > + 2 + usecs_to_jiffies(time_us));
>
> Magic!
It turned out the the "2" can be removed, as the timeout is already rounded up.
> > + usleep_range(time_us, time_us + 100000);
> If time_us appears to be, let's say, 100. The above margin is way too high.
range changed to (time_us, 2 * time_us).
> > + if (osr_status & AS73211_OSR_SS) {
> > + dev_warn(dev, "%s() Measurement has not
> > stopped\n", __func__); + return -ETIME;
> > + }
> > + if (osr_status & AS73211_OSR_STATUS_NOTREADY) {
> > + dev_warn(dev, "%s() Data is not ready\n",
> > __func__); + return -ENODATA;
> > + }
> > + if (!(osr_status & AS73211_OSR_STATUS_NDATA)) {
> > + dev_warn(dev, "%s() New new data available\n",
> > __func__); + return -ENODATA;
> > + }
> > + if (osr_status & AS73211_OSR_STATUS_LDATA) {
> > + dev_warn(dev, "%s() Result buffer overrun\n",
> > __func__); + return -ENOBUFS;
> > + }
> > + if (osr_status & AS73211_OSR_STATUS_ADCOF) {
> > + dev_warn(dev, "%s() ADC overflow\n", __func__);
> > + return -EOVERFLOW;
> > + }
> > + if (osr_status & AS73211_OSR_STATUS_MRESOF) {
> > + dev_warn(dev, "%s() Measurement result
> > overflow\n", __func__); + return -EOVERFLOW;
> > + }
> > + if (osr_status & AS73211_OSR_STATUS_OUTCONVOF) {
> > + dev_warn(dev, "%s() Timer overflow\n", __func__);
> > + return -EOVERFLOW;
> > + }
> > + dev_warn(dev, "%s() Unexpected status value\n", __func__);
> > + return -EIO;
> > + }
>
> All above dev_warn() are wrong. Should be dev_err(). Otherwise all
> return -ERRNO are wrong.
I have changed everything to "dev_err".
> > + *val = BIT(data->creg3 & GENMASK(1, 0)) * 1024 * 1000;
>
> 1000 is magic and 1024 either.
Changed to 1024000 and added a comment.
> 1000 is frequency multiplier? If it's not defined do it like
> #define HZ_PER_KHZ
> #define KHZ_PER_MHZ
> or what is that?
>
> ...
>
> > + *val = time_us / 1000000;
> > + *val2 = time_us % 1000000;
>
> Ditto.
>
> NSEC_PER_SEC or what?
>
> ...
>
> > + int reg_bits, freq_kHz = val / 1000; /* 1024, 2048, ...
> > */
>
> HZ_PER_KHZ?
>
> ...
>
> > + if (val < 0 || (freq_kHz * 1000) != val || val2)
>
> Ditto.
I switched to existing defined where possible. But I wouldn't like to introduce
this for every possible physical unit. Please check again in v4.
> > + return i2c_smbus_write_byte_data(data->client,
> > AS73211_REG_CREG3, data->creg3);
> Can it suddenly return positive number?
The i2c_smbus_write_xxx() return 0 on success, but i2c_smbus_read_xxx return
the value read from the register...
> > + struct iio_dev *indio_dev = pf->indio_dev;
>
> Ditto. Do you use indio_dev below (except one case)? I haven't noticed.
indio_dev is used multiple times
> > + }
> > + /* Optimization for reading only color channels */
> > + else {
>
> Should be one line. Had you run checkpatch?
checkpatch didn't complain here (probably due to the comment). Changed anyway.
> > +static ssize_t as73211_show_samp_freq_available(struct device *dev
> > __always_unused, + struct
> > device_attribute *attr __always_unused, +
> > char *buf)
> > +{
> > +}
> > +
> > +static ssize_t as73211_show_int_time_available(struct device *dev,
> > + struct device_attribute
> > *attr __always_unused, +
> > char *buf)
> > +{
> > +}
> > +
> > +static ssize_t as73211_show_hardwaregain_available(struct device *dev
> > __always_unused, +
> > struct device_attribute *attr __always_unused, +
> > char *buf)
> > +{
> > +}
>
> I guess above is an overkill. See example here
>
> commit 6085102c494b8afc62bc093f8f32d6248f6d33e5
> Author: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
> Date: Mon Mar 23 12:41:26 2020 +0200
>
> iio: pressure: bmp280: Convert to use ->read_avail()
>
> ...
>
Converted to read_avail(). Please also review read_raw() for
IIO_CHAN_INFO_OFFSET and IIO_CHAN_INFO_SCALE.
> > + ret = i2c_smbus_read_byte_data(data->client, AS73211_REG_OSR);
> > + if (ret < 0)
> > + return ret;
>
> Yeah, be consistent. Either all such call should be checked against
> negative error code, or drop ' < 0' everywhere it applies.
I decided to check for < 0 everywhere.
> > + if (client->irq) {
> > + ret = request_threaded_irq(client->irq,
> > + NULL,
> > + as73211_ready_handler,
> > + IRQF_TRIGGER_RISING | IRQF_ONESHOT,
>
> Should not be IRQ trigger type here. (Do you have broken firmware table?)
Of course you are right! This is already in the device tree:
interrupts = <19 IRQ_TYPE_EDGE_RISING>;
