drivers/iio/imu/inv_mpu6050

InvenSense MPU-6050 family and ICM-206xx motion-tracking IMUs

A widely deployed family of 6-axis and 9-axis motion sensors (gyroscope, accelerometer, and on some parts a magnetometer) from InvenSense, now owned by TDK. Parts like the MPU-6050, MPU-6500, MPU-9150, MPU-9250 and the newer ICM-206xx series are found in countless hobbyist boards, drones, robotics projects, fitness wearables, and embedded products from the early 2010s onward.

keep-annotate conf=0.83 deploy=medium replacement=none subsystem=iio category=sensor-iio
83%

recommendation

Worth keeping but flagging as legacy-heavy because the original MPU-6050 silicon is now end-of-life at TDK (which steers new designs toward the ICM-42670-P), yet modules based on these chips are still stocked at distributors like DigiKey and remain ubiquitous in the maker and embedded world. Upstream activity backs that up: the driver was still getting probe and error-path fixes in early 2026 and patches were being backported to stable kernels, so it is actively maintained for a real installed base.

repository signals

13 files
4,558 source lines
52 commits, 5y
+1,006 / −397 lines added / removed, 5y
22 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 52 total · active in 33/61 months
2021 2022 2023 2024 2025 2026 2021-04: 1 commit · +1 −1 2021-05: 2 commits · +9 −19 2021-06: 2 commits · +38 −22 2021-07: 0 commits · +0 −0 2021-08: 1 commit · +21 −15 2021-09: 1 commit · +1 −1 2021-10: 0 commits · +0 −0 2021-11: 1 commit · +2 −2 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 3 commits · +11 −14 2022-03: 1 commit · +24 −2 2022-04: 0 commits · +0 −0 2022-05: 1 commit · +1 −1 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 2 commits · +3 −5 2022-09: 1 commit · +12 −11 2022-10: 0 commits · +0 −0 2022-11: 1 commit · +3 −4 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 2 commits · +26 −3 2023-06: 2 commits · +63 −101 2023-07: 0 commits · +0 −0 2023-08: 1 commit · +0 −1 2023-09: 1 commit · +17 −0 2023-10: 2 commits · +5 −8 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 2 commits · +7 −0 2024-03: 4 commits · +600 −88 2024-04: 2 commits · +2 −2 2024-05: 1 commit · +3 −2 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 1 commit · +11 −2 2024-09: 3 commits · +49 −10 2024-10: 4 commits · +4 −11 2024-11: 1 commit · +38 −0 2024-12: 1 commit · +4 −4 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 1 commit · +6 −8 2025-04: 2 commits · +6 −6 2025-05: 1 commit · +20 −36 2025-06: 1 commit · +3 −7 2025-07: 1 commit · +2 −3 2025-08: 1 commit · +0 −7 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 1 commit · +14 −1 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The driver is still receiving non-trivial upstream fixes in 2026, including probe/regulator error-path work.

  2. lore.kernel.org

    Fixes for this driver family are being backported to stable, indicating ongoing supported deployments.

  3. invensense.tdk.com

    TDK marks MPU-6050 as EOL and names ICM-42670-P as the recommended replacement for that specific part.

  4. digikey.com

    Even though the MPU-6050 IC is obsolete, MPU-6050-based boards/modules and accessories are still sold through mainstream distribution channels.

codex reasoning notes (technical)

Local source inspection (shell `rg`/`sed`) shows a real multi-chip IMU driver covering MPU6050/9150/6500/9250 and ICM206xx parts. lore_file_timeline on `inv_mpu_core.c` produced the cited 2026 linux-iio and stable URLs, showing active fixes/backports rather than retirement. Web search produced the cited TDK and DigiKey URLs: TDK shows the base MPU-6050 is EOL with a newer silicon recommendation, while DigiKey still lists MPU-6050 ecosystem hardware for sale. Net: legacy silicon in an active installed base with continuing maintenance; annotate as legacy-heavy, but do not deprecate/remove.