rust-embedded / rust-embedded/linux-embedded-hal

Switch to gpiocdev-rs for GPIO uAPI v2 support?

Open
#92 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
319
Forks
60
Avg merge
12h 31m
Merged PRs (30d)
1

Description

Context:
Our gpio-cdev crate only supports GPIO uAPI v1, which has been deprecated in the kernel. There is a new crate gpiocdev which does support it in newer kernels.

Preliminary analysis of switching to the newer gpiocdev in no particular order:

  • Pro:
    • Supports GPIO uAPI v2 as well as v1 which is deprecated.
    • More active project.
    • Author is the author of the API in the Linux kernel.
    • gpiosim support.
  • Cons:
    • Porting effort.
    • Adds many dependencies.
    • Breaking change.
    • Outside of the rust-embedded org.

See https://github.com/rust-embedded/gpio-cdev/issues/68

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the current gpio-cdev dependency context and rust-embedded/gpio-cdev#68, then compare the migration implications of gpiocdev-rs. The issue names no files or tests; the work is complete only when the project has settled the migration decision and its breaking-change and porting scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
embedded-iot, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.