drivers: sensor: mb7040: add support for MaxBotix MB7040 ultrasonic sensor

[ww3ak]

Adds a new Zephyr sensor driver for the MaxBotix MB7040 ultrasonic rangefinder.

The driver uses I2C communication to read range data from the sensor and exposes it via the Zephyr sensor API.

Functionality was tested on an esp32-s3.

[github-actions]

Hello @ww3ak, 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. 😊

[jilaypandya]

Hey @ww3ak, Thanks for creating this PR, If i am not completely mistaken, i think a couple of files are missing here. Taking reference from a recent sensor driver contribution #89908, you would need to add bindings, also add the sensor to i2c.dtsi.

[Copilot]

Pull Request Overview

Adds support for the MaxBotix MB7040 ultrasonic sensor via I2C and optional status GPIO, exposing distance measurements through the Zephyr sensor API.

• Implements sample fetch, channel get, and initialization routines with semaphore and GPIO callback
• Provides Kconfig options for driver enablement and measurement timing
• Registers the driver in CMakeLists for build integration

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
drivers/sensor/mb7040/mb7040.c	New sensor driver with I2C read/write, status GPIO interrupt, and Zephyr sensor API hooks
drivers/sensor/mb7040/Kconfig	Configuration entries for enabling the driver, delay timing, and status GPIO support
drivers/sensor/mb7040/CMakeLists.txt	Build file including the new driver source in the Zephyr library

Comments suppressed due to low confidence (2)

drivers/sensor/mb7040/Kconfig:19

• Update help text to reflect that MB7040_DELAY_MS is applied unconditionally (used even when status GPIO is enabled).

Default delay if status-gpio is not defined

drivers/sensor/mb7040/mb7040.c:1

• [nitpick] Consider adding unit or integration tests for the new driver to verify I2C read/write behavior and status GPIO handling.

/*

[ww3ak]

I believe I fixed/added necessary things!

[jilaypandya]

could you run check_compliance.py locally, it will help you solve some of the compliance issues.
https://docs.zephyrproject.org/latest/contribute/style/code.html

comment addressed

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarQube Cloud

[ww3ak]

@jilaypandya thanks for the approval! What do I have to wait for now for this to be merged?

[jilaypandya]

You need an approval from the assignee of the PR :). Other requested changes need to be addressed if any, after that the PR is merge ready.