-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
Area: cpuArea: CPU/MCU portsArea: CPU/MCU portsArea: driversArea: Device driversArea: Device driversDiscussion: RFCThe issue/PR is used as a discussion starting point about the item of the issue/PRThe issue/PR is used as a discussion starting point about the item of the issue/PRProcess: API changeIntegration Process: PR contains or issue proposes an API change. Should be handled with care.Integration Process: PR contains or issue proposes an API change. Should be handled with care.State: staleState: The issue / PR has no activity for >185 daysState: The issue / PR has no activity for >185 daysType: new featureThe issue requests / The PR implemements a new feature for RIOTThe issue requests / The PR implemements a new feature for RIOT
Description
Many times, internal peripherals in a MCU are enough to handle basic operations, like GPIOs, ADCs, DACs, etc. However, for complex applications, extensions for such peripherals are needed, and actually widely used in industry.
Since RIOT aim is to keep the periph interfaces as slim and portable as possible, making extensions to them is indeed a complicated task. The aim of this issue is to explore the possible solutions to this, and to work together towards a common definition on how to write APIs and driver extensions for this use-case.
I'll summarize here the interfaces that need changes, and the PRs if there's one.
GPIO
- periph/gpio: support for extension API #9860 (partially replaces drivers/gpio_exp: map GPIO expanders onto gpio_t #9190) (PR)
- periph/gpio: support for extension API (part 2) #9958 (partially replaces drivers/gpio_exp: map GPIO expanders onto gpio_t #9190) (PR)
ADC
DAC
PWM
Metadata
Metadata
Assignees
Labels
Area: cpuArea: CPU/MCU portsArea: CPU/MCU portsArea: driversArea: Device driversArea: Device driversDiscussion: RFCThe issue/PR is used as a discussion starting point about the item of the issue/PRThe issue/PR is used as a discussion starting point about the item of the issue/PRProcess: API changeIntegration Process: PR contains or issue proposes an API change. Should be handled with care.Integration Process: PR contains or issue proposes an API change. Should be handled with care.State: staleState: The issue / PR has no activity for >185 daysState: The issue / PR has no activity for >185 daysType: new featureThe issue requests / The PR implemements a new feature for RIOTThe issue requests / The PR implemements a new feature for RIOT