Request for comments: the driver library

[bettio]

I'm planning to create a new repo for collecting all pure Erlang drivers.

The plan is the following:

• I will create a repo called atomvm_drivers
• Instead of creating a package, everything will be split in the smallest possible units
• Each package will have a common naming schema (no yet sure between: avm_driver_foo123 or avm_foo123_driver)
• Each driver module will have a common naming schema (e.g. foo123_driver)

CI will take care of publishing everything in a automated way on hex.pm, so we don't have to worry about this task.

In order to use packages from git instead of hex.pm:
mix: use sparse option, e.g.: sparse: “apps/sx126x_driver”
rebar3: use git_subdir

Some good candidates for inclusion:

• https://github.com/bettio/pocketOS/blob/main/src/bq25896_driver.erl
• https://github.com/bettio/pocketOS/blob/main/src/lora_sx126x.erl (rename needed -> sx126x_driver)
• https://github.com/bettio/pocketOS/blob/main/src/rotary_driver.erl (rename likely needed -> generic_rotary_driver)
• https://github.com/bettio/pocketOS/blob/main/src/tca8418_driver.erl
• https://github.com/bettio/pocketOS/blob/main/src/xl9555_driver.erl

C components are out of scope now.

Why splitting everything into small packages?

We want to save flash space, so we avoid unnecessary bundling. If a hardware project has a sx126x chip, it doesn't make sense having stored in the flash also the driver for sx1728 chip. If anyone needs both, adding both to project deps must work.