Skip to content

Question: How best to contribute drivers upstream? #33977

@adamfowleruk

Description

@adamfowleruk

Hello all,

On the Herald Project we've been asked to put together some opensource hardware designs. (To be published soon). These will use some external ICs that may not have drivers in Zephyr RTOS already.

I have a holding place for drivers that we may create for these devices, but really I'd prefer to contribute them back upstream to this project.

Do you have any past best practice for people that create drivers for their own needs/products immediately, and contribute them back upstream to Zephyr for appearance in a later release?

The main issue I see is that of time lag vs. supportability. We need those taking on our opensource hardware and software to grab the latest release of the Nordic SDK, add in our code project, and then build for the target platform. The consumers are Public Health Authorities and so can't really work against the bleeding edge develop branches of Zephyr, or to patch NCS. So we need a way to give them any missing drivers immediately, but then make sure we contribute them back upstream to your project to ensure everyone else can benefit.

Any advice greatly appreciated. Hardware and device drivers not yet uploaded (should be in the next 1-2 weeks), but they will live here:-
https://github.com/theheraldproject/herald-hardware
https://github.com/theheraldproject/zephyr-devices

With our C++ based API that uses the data from these things living here:
https://github.com/theheraldproject/herald-for-cpp

Thanks in advance.

Metadata

Metadata

Assignees

Labels

MetaA collection of features, enhancements or bugs

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions