--- title: A new kselftest for verifying driver probe of... description: A new Linux kernel self-test (kselftest) has been upstreamed to verify that drivers correctly probe devices on Devicetree-based platforms. Unlike the existing... canonical: https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: A new kselftest for verifying driver probe of Devicetree-based platforms | daily.dev og:description: A new Linux kernel self-test (kselftest) has been upstreamed to verify that drivers correctly probe devices on Devicetree-based platforms. Unlike the existing... og:url: https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl og:image: https://api.daily.dev/og/posts/l6Rli8mVl.png og:image:alt: A new kselftest for verifying driver probe of Devicetree-based platforms og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # A new kselftest for verifying driver probe of Devicetree-based platforms **[Collabora Blog](https://daily.dev/sources/collabora)** · 4 min read · 0 upvotes · 0 comments ## Summary A new Linux kernel self-test (kselftest) has been upstreamed to verify that drivers correctly probe devices on Devicetree-based platforms. Unlike the existing bootrr tool, which relies on unstable kernel ABIs and requires per-platform device lists, the new DT kselftest leverages the already-maintained Devicetree to automatically enumerate expected devices and checks via sysfs whether each has a bound driver. On the MT8195-based Tomato Chromebook running Linux-next, results show 181 passing, 34 skipped, and 11 failing tests — all failures correctly indicating missing upstream support. Similar kselftests for ACPI-based platforms and discoverable buses like USB and PCI are in progress on the mailing list. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the main problems with bootrr for testing driver probe on Linux platforms? Bootrr relies on unstable kernel ABIs — specifically device and driver names — that can change between kernel versions, causing false regression reports and requiring updates per kernel version. It also requires a manually crafted list of all devices for each new platform, making it costly to enable and maintain. The new DT kselftest avoids both issues by using the already-maintained Devicetree. _Kernel developers tracking driver probe regressions across platforms follow upstream testing developments on daily.dev._ ### How does the new Linux DT kselftest determine which devices to check for driver binding? The test iterates over nodes in the currently loaded Devicetree and checks via sysfs whether a corresponding device and driver are bound. Nodes not expected to register a device are skipped based on a list of Devicetree compatibles extracted from all drivers in the kernel source, so no per-platform device list needs to be maintained separately. _Embedded Linux engineers keeping up with kernel testing improvements find relevant upstream discussions on daily.dev._ ## Similar posts on daily.dev - [Linux 7.4 To Introduce Initial Device Trees For Apple M4, A18 Pro For MacBook Neo](https://daily.dev/posts/linux-7-4-to-introduce-initial-device-trees-for-apple-m4-a18-pro-for-macbook-neo-gwvp2quis) · Phoronix · 0 upvotes · 0 comments - [Linux 7.1 Lands Workaround For Arm C1-Pro Erratum](https://daily.dev/posts/linux-7-1-lands-workaround-for-arm-c1-pro-erratum-p9wxa3qmk) · Phoronix · 0 upvotes · 0 comments - [Linux Kernel Introducing New Taint Due To Fuzzing Bots Yielding Impractical Bug Reports](https://daily.dev/posts/linux-kernel-introducing-new-taint-due-to-fuzzing-bots-yielding-impractical-bug-reports-xgx8vvj7q) · Phoronix · 0 upvotes · 0 comments - [Linux DT Patches Provide Very Basic Support For Apple M3 Pro / Max / Ultra](https://daily.dev/posts/linux-dt-patches-provide-very-basic-support-for-apple-m3-pro-max-ultra-1pfcyj2wn) · Phoronix · 0 upvotes · 0 comments - [Linux Kernel API Specification Framework Advances Past RFC Stage](https://daily.dev/posts/linux-kernel-api-specification-framework-advances-past-rfc-stage-rzo4apdfa) · Phoronix · 0 upvotes · 0 comments --- Tags: [#linux](https://daily.dev/tags/linux) [View this post on daily.dev](https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"A new kselftest for verifying driver probe of Devicetree-based platforms","url":"https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl"},"datePublished":"2026-08-11T08:53:32.716Z","dateModified":"2026-08-11T09:14:56.267Z","description":"A new Linux kernel self-test (kselftest) has been upstreamed to verify that drivers correctly probe devices on Devicetree-based platforms. Unlike the existing...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3c216717421ba66cca81a3c9835f99bc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3c216717421ba66cca81a3c9835f99bc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collabora Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collabora Blog","logo":"https://media.daily.dev/image/upload/s--ZGZ0FjqS--/f_auto,q_auto/v1786438306/logos/collabora?_a=BAMAMicg0","url":"https://daily.dev/sources/collabora"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collabora Blog","item":"https://daily.dev/sources/collabora"},{"@type":"ListItem","position":3,"name":"A new kselftest for verifying driver probe of Devicetree-based platforms"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-new-kselftest-for-verifying-driver-probe-of-devicetree-based-platforms-l6rli8mvl#faq","mainEntity":[{"@type":"Question","name":"What are the main problems with bootrr for testing driver probe on Linux platforms?","acceptedAnswer":{"@type":"Answer","text":"Bootrr relies on unstable kernel ABIs — specifically device and driver names — that can change between kernel versions, causing false regression reports and requiring updates per kernel version. It also requires a manually crafted list of all devices for each new platform, making it costly to enable and maintain. The new DT kselftest avoids both issues by using the already-maintained Devicetree. Kernel developers tracking driver probe regressions across platforms follow upstream testing developments on daily.dev."}},{"@type":"Question","name":"How does the new Linux DT kselftest determine which devices to check for driver binding?","acceptedAnswer":{"@type":"Answer","text":"The test iterates over nodes in the currently loaded Devicetree and checks via sysfs whether a corresponding device and driver are bound. Nodes not expected to register a device are skipped based on a list of Devicetree compatibles extracted from all drivers in the kernel source, so no per-platform device list needs to be maintained separately. Embedded Linux engineers keeping up with kernel testing improvements find relevant upstream discussions on daily.dev."}}]} ```