drivers: sensors: add ST lis2dux12 accelerometer support

[kdunn926]

The driver was based off the existing lis2dw12 implementation.

This was physically tested via SPI at 1MHz using a nrf52840 development kit. Both the Zephyr sensor and direct spi_write APIs were successfully used. Interrupts and runtime configuration changes (e.g. ODR, range) were not tested.

sensor API sample:

    struct sensor_value accel[3];
    int rc = sensor_sample_fetch_chan(accelerometer_dev, SENSOR_CHAN_ALL);
    [...]
    rc = sensor_channel_get(accelerometer_dev, SENSOR_CHAN_ACCEL_XYZ,  accel);

spi_write API sample:

int lis2dux12_print_device_id()
{

    static uint8_t tx_buffer[2] = { LIS2DUX12_WHO_AM_I, 0x0 };
    static uint8_t rx_buffer[2] = { 0x0, 0x0 };

    const struct spi_buf tx_buf = {
            .buf = tx_buffer,
            .len = sizeof(tx_buffer)
    };
    const struct spi_buf_set tx =  {
            .buffers = &tx_buf,
            .count = 1
    };

    const struct spi_buf rx_buf = {
            .buf = rx_buffer,
            .len = sizeof(rx_buffer)
    };
    const struct spi_buf_set rx =  {
            .buffers = &rx_buf,
            .count = 1
    };

    int ret = spi_transceive(spi3_dev, &spi3_cfg, &tx, &rx);
    if (ret != 0) {
        LOG_ERR("SPI write error: %s [%d]\n", strerror(ret), ret);
    } else {
        // ignore first byte
        LOG_WRN("Device ID: %x", rx_buffer[1]);
    }

    return ret;
}

[github-actions]

Hello @kdunn926, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[ycsin]

consider using year 2023, and probably just use .clang-format to format all these new files

[avisconti]

It's been a long way but we are finally there...

[MaureenHelm]

Please rebase

[kdunn926]

Please rebase

Ok I just did. Sorry for the delay.

[kdunn926]

consider using year 2023, and probably just use .clang-format to format all these new files

@ycsin - Have all the changes you requested been addressed?

[avisconti]

@fabiobaltieri if/when you have time, can you possibly take a look at this PR? Thanks

[fabiobaltieri]

drop the initializer, not needed

[kdunn926]

Alright

[fabiobaltieri]

invert the logic here:

if (err) {
        return err;
}

and just return 0; at the end of the function, keep the normal execution flow inline, easier to follow the code intended path

[kdunn926]

That makes sense. I made the change.

[fabiobaltieri]

sure you don't want to error out here? silently falling back to default does not strike me as a great idea, maybe add a LOG_ERR and return -EINVAL?

[kdunn926]

Good point, I changed it to be like this:

	default:
		LOG_ERR("range [%d] not supported.", range);
		return -EINVAL;

[fabiobaltieri]

nit: you can probably pull those \ a bit behind, no need to make lines unnecessarily wide

[kdunn926]

Alright, I shifted these over quite a bit in the latest commit.

stale

[avisconti]

Very good

[github-actions]

Hi @kdunn926!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁