2019-01-03 11:39:48 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
|
|
|
|
|
|
ccflags-y := \
|
2019-03-29 20:32:41 +09:00
|
|
|
-I $(srctree)/$(src)/../include \
|
|
|
|
|
-I $(srctree)/$(src)
|
2019-01-03 11:39:48 +00:00
|
|
|
|
|
|
|
|
komeda-y := \
|
drm/komeda: Build komeda to be a platform module
Implement a simple wrapper for platform module to build komeda to module,
Also add a very simple D71 layer code to show how to discover a product.
Komeda driver direct bind the product ENTRY function xxx_identity to DT
compatible name like:
d71_product = {
.product_id = MALIDP_D71_PRODUCT_ID,
.identify = d71_identify,
},
const struct of_device_id komeda_of_match[] = {
{ .compatible = "arm,mali-d71", .data = &d71_product, },
{},
};
Then when linux found a matched DT node and call driver to probe, we can
easily get the of data, and call into the product to do the identify:
komeda_bind()
{
...
product = of_device_get_match_data(dev);
product->identify();
...
}
Changes in v4:
- Replaced kzalloc with devm_kzalloc
Changes in v3:
- Fixed style problem found by checkpatch.pl --strict.
Signed-off-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
Acked-by: Liviu Dudau <liviu.dudau@arm.com>
Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
2019-01-03 11:40:21 +00:00
|
|
|
komeda_drv.o \
|
2019-01-03 11:39:48 +00:00
|
|
|
komeda_dev.o \
|
2019-01-03 11:40:55 +00:00
|
|
|
komeda_format_caps.o \
|
2019-05-16 07:13:13 +01:00
|
|
|
komeda_color_mgmt.o \
|
2019-01-03 11:41:13 +00:00
|
|
|
komeda_pipeline.o \
|
2019-01-22 11:05:51 +00:00
|
|
|
komeda_pipeline_state.o \
|
2019-01-03 11:41:30 +00:00
|
|
|
komeda_framebuffer.o \
|
|
|
|
|
komeda_kms.o \
|
|
|
|
|
komeda_crtc.o \
|
|
|
|
|
komeda_plane.o \
|
2019-05-23 10:36:38 +01:00
|
|
|
komeda_wb_connector.o \
|
2019-11-07 11:42:32 +00:00
|
|
|
komeda_private_obj.o \
|
|
|
|
|
komeda_event.o
|
drm/komeda: Build komeda to be a platform module
Implement a simple wrapper for platform module to build komeda to module,
Also add a very simple D71 layer code to show how to discover a product.
Komeda driver direct bind the product ENTRY function xxx_identity to DT
compatible name like:
d71_product = {
.product_id = MALIDP_D71_PRODUCT_ID,
.identify = d71_identify,
},
const struct of_device_id komeda_of_match[] = {
{ .compatible = "arm,mali-d71", .data = &d71_product, },
{},
};
Then when linux found a matched DT node and call driver to probe, we can
easily get the of data, and call into the product to do the identify:
komeda_bind()
{
...
product = of_device_get_match_data(dev);
product->identify();
...
}
Changes in v4:
- Replaced kzalloc with devm_kzalloc
Changes in v3:
- Fixed style problem found by checkpatch.pl --strict.
Signed-off-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
Acked-by: Liviu Dudau <liviu.dudau@arm.com>
Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
2019-01-03 11:40:21 +00:00
|
|
|
|
|
|
|
|
komeda-y += \
|
2019-01-22 09:23:40 +00:00
|
|
|
d71/d71_dev.o \
|
|
|
|
|
d71/d71_component.o
|
2019-01-03 11:39:48 +00:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_DRM_KOMEDA) += komeda.o
|
