zephyr/samples/application_development/out_of_tree_driver
Tomasz Bursztyka 98d9b01322 device: Apply driver_api/data attributes rename everywhere
Via coccinelle:

@r_device_driver_api_and_data_1@
struct device *D;
@@
(
D->
-	driver_api
+	api
|
D->
-	driver_data
+	data
)

@r_device_driver_api_and_data_2@
expression E;
@@
(
net_if_get_device(E)->
-	driver_api
+	api
|
net_if_get_device(E)->
-	driver_data
+	data
)

And grep/sed rules for macros:

git grep -rlz 'dev)->driver_data' |
	xargs -0 sed -i 's/dev)->driver_data/dev)->data/g'

git grep -rlz 'dev->driver_data' |
	xargs -0 sed -i 's/dev->driver_data/dev->data/g'

git grep -rlz 'device->driver_data' |
	xargs -0 sed -i 's/device->driver_data/device->data/g'

Fixes #27397

Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2020-08-11 19:30:53 +02:00
..
hello_world_module/zephyr device: Apply driver_api/data attributes rename everywhere 2020-08-11 19:30:53 +02:00
src samples: application_development: Fix for userspace 2020-06-13 16:37:58 -04:00
CMakeLists.txt samples: application_development: Fix for userspace 2020-06-13 16:37:58 -04:00
prj.conf samples: application_development: Fix for userspace 2020-06-13 16:37:58 -04:00
README.rst samples: out_of_tree_driver: Add readme to out of tree sample 2020-05-15 17:18:56 +02:00
sample.yaml samples: clean test identifiers 2020-05-11 17:00:26 +02:00

.. _out_of_tree_driver:

Out Of Tree Driver
##################

Overview
********
A simple example that demonstrates custom zephyr drivers using the zephyr driver
API that are maintained outside of Zephyr.