1976f33e87
One limitation of the current IPM API is that it is assuming that the hardware is only exporting one single channel through which the data can be sent or signalling can happen. If the hardware supports multiple channels, the IPM device must be instantiated (possibly in the DT) several times, one for each channel to be able to send data through multiple channels using the same hw peripheral. Also in the current IPM API only one callback can be registered, that means that only one driver is controlling all the signalling happening on all the channels. This patch is introducing a new MBOX API that is supporting multi-channel signalling and data exachange leveraging and extending the previous (and outdated) IPM API. Signed-off-by: Carlo Caione <ccaione@baylibre.com> |
||
|---|---|---|
| .. | ||
| vnd,adc-temp-sensor.yaml | ||
| vnd,adc.yaml | ||
| vnd,array-holder.yaml | ||
| vnd,busy-sim.yaml | ||
| vnd,child-bindings.yaml | ||
| vnd,clock.yaml | ||
| vnd,disabled-compat.yaml | ||
| vnd,dma.yaml | ||
| vnd,enum-holder.yaml | ||
| vnd,enum-int-required-false-holder.yaml | ||
| vnd,enum-required-false-holder.yaml | ||
| vnd,gpio-expander-common.yaml | ||
| vnd,gpio-expander-i2c.yaml | ||
| vnd,gpio-expander-spi.yaml | ||
| vnd,gpio-one-cell.yaml | ||
| vnd,gpio.yaml | ||
| vnd,great-grandchild-bindings.yaml | ||
| vnd,i2c-device.yaml | ||
| vnd,i2c-mux.yaml | ||
| vnd,i2c.yaml | ||
| vnd,intc.yaml | ||
| vnd,interrupt-holder.yaml | ||
| vnd,mbox-zero-cell.yaml | ||
| vnd,mbox.yaml | ||
| vnd,phandle-holder.yaml | ||
| vnd,pinctrl-device.yaml | ||
| vnd,pinctrl-test.yaml | ||
| vnd,pinctrl.yaml | ||
| vnd,pwm.yaml | ||
| vnd,reg-holder.yaml | ||
| vnd,serial.yaml | ||
| vnd,spi-device-2.yaml | ||
| vnd,spi-device.yaml | ||
| vnd,spi.yaml | ||