slimbus: Add messaging APIs to slimbus framework

Browse source

SLIMbus devices use value-element, and information elements to
control device parameters (e.g. value element is used to represent
gain for codec, information element is used to represent interrupt
status for codec when codec interrupt fires).
Messaging APIs are used to set/get these value and information
elements. SLIMbus specification uses 8-bit "transaction IDs" for
messages where a read-value is anticipated. Framework uses a table
of pointers to store those TIDs and responds back to the caller in
O(1).
Caller can do synchronous and asynchronous reads/writes.

Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Reviwed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

...

This commit is contained in:

Sagar Dharia 2017-12-11 23:43:00 +00:00 • committed by Greg Kroah-Hartman

parent 7588a511bd

commit afbdcc7c38

4 changed files with 405 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

drivers/slimbus/Makefile

View file

297

drivers/slimbus/messaging.c

View file

67

drivers/slimbus/slimbus.h

View file

40

include/linux/slimbus.h

View file