Driver API review/cleanup/rework

[galak]

This issue will be used to track all driver subsystem rework/cleanups:

• spi: Issue SPI subsystem API & features updates #5797, SPI API improvements proposals #5839, PR SPI API cleanup and update #5921

• adc: PR Introduce reworked API for ADC drivers #7691 Remove QMSI sensor subsystem ADC driver and use Designware driver for ARC. #8857

• counter/rtc: Issue drivers: counter API update  #5895, Unify counter.h and rtc.h interfaces #8331. PR see issue. API complete

• display PR: Display api #7833

• watchdog: Issues Convert Atmel SAM Watchdog driver to new API #10913, Convert Atmel SAM0 Watchdog driver to new API #10914, Convert CMSDK APB Watchdog driver to new API #10916, Convert iwdg_stm32 STM32 Watchdog driver to new API #10917 DONE: Issue Watchdog API update #3994, PR drivers: watchdog: Watchdog API redesign [RFC] #1260, drivers: wdt: Watchdog API redesign and shim for nrfx wdt driver #7007

• i2c Issue: Collection of various issues related to I2C API #4040 PR: Add support for I2C Slave Drivers #5224 (merged)

• gpio Issue gpio: Cleanup flags #10339 Add GPIO_ACCESS_BY_PORT_MASK mode #10741 gpio/pinctrl: GPIO and introduce PINCTRL API to support gpio, pinctrl DTS nodes #15611

• pinctrl: PR drivers: pinctrl device interface (Linux-like) and STM32F0 driver #5799

• pinmux

• Advanced sensor API lack of a performant sensor API #1387, RFC: Improvements to drivers/sensors for light sensors #13455 ZIO: Beginnings of a Sampled Input/Output API #14008

• General inconsistencies and common guidelines for APIs

• serial Issue: Provide more generic UART APIs for read and write #1682 RFC: UART API Enhancements #8243 serial: uart_irq_tx_ready() needs better documentation or correction of the test #11535 PRs: driver: uart-stm32: add line_ctrl_set/get support #8306 uart: expanded common line controls command #8307 (@jarz-nordic). PR api: uart: Add new asynchronous UART API (Transfer sub-API) #10820

• dma RFC: DMA API: API to reload/refresh DMA buffer(s) #8974 RFC: DMA API: use client data in dma_callback function instead of dma dev #8928

• pwm: Issues pwm: Update PWM API for dynamic prescaler computation #6958 and pwm: No clear semantics to stop a PWM leads to diverse implementations #9507

• battery: Issue battery: Add standard APIs for Battery Charging and Fuel Gauge Handling (Energy Management) #2542

• led Issue: led: Add color setting and fading to LED API #8946

• clock_control Issues: clock_control: API should support asynchronous and synchronous variants of turning on clocks #11107 clock_control: API should allow callback to be specified #12039 ZIO: Beginnings of a Sampled Input/Output API #14008

• console (console.h? clarify with @pfalcon)

• usb

• aio

• bluetooth: internal to bt subsystem

• crypto

• entropy

• ethernet: internal to net subsystem

• flash

• i2s

• ieee802154: internal to net subsystem

• ipm

• pci

• system timer: interface to kernel, no exported header file

• sensor

• interrupt_controller

  • shared_irq

Notes from API meeting:

https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit?usp=sharing

[b0661]

@galak can pinctrl PR #5799 also be added here?

[carlescufi]

@b0661 done

[Mani-Sadhasivam]

@galak @carlescufi Can we add LED API to this issue?

[carlescufi]

@Mani-Sadhasivam done, is that what you meant?

[Mani-Sadhasivam]

@carlescufi No, I mean to add LED entry to the list of API's here. I will work on extending the API further.

[Mani-Sadhasivam]

@carlescufi Moreover, issue #8946 belongs to LED API and not LED Strip.

[vaussard]

Issues related to the PWM API: #6958 and #9507

[galak]

@mbolivar to move this issue into a project.

[nvlsianpu]

@galah @carlescufi flash driver documentation issue: flash: should write_protection be emulated?

[mbolivar]

@mbolivar to move this issue into a project.

Finally got around to this: https://github.com/zephyrproject-rtos/zephyr/projects/18

Is that pretty much what people are expecting? Should we close this if so?

[andrewboie]

I think we need clarity on what is going on with the new async serial API, and the old CONFIG_UART_INTERRUPT_DRIVEN API, as seen here: #14854

[henrikbrixandersen]

@galak Does this issue still provide value or can it be closed?

[galak]

@galak Does this issue still provide value or can it be closed?

going to close it. We can re-open if needed.