drm/tilcdc: Add bridge support and sync-lost flood recovery
Subsystems (6)
v4 cover drm/tilcdc: Add bridge support and sync-lost flood recovery
Changes since v3:
- "drm/tilcdc: Enable sync lost error and recovery handling for rev 1 LCDC"
- Fix broken irq enable/disble code for LCDC rev 1
- Add: "dt-bindings: Move "ti,tfp410.txt" from display/ti to display/bridge"
- "drm/bridge: Add ti-tfp410 DVI transmitter driver"
- Don't fail if either i2c or platform driver register succeeds
- ftp410 -> tfp410
- Merge the old display/ti,tfp410.txt document with my addition
Changes since v2:
- "drm/tilcdc: Recover from sync lost error flood by resetting the LCDC"
- no change
- "drm/bridge: Add ti-tfp410 DVI transmitter driver"
- Fix deveice-tree document
- "driver node" -> "device node"
- remove "(the current implementation does not yet support this)"
- Add dummy i2c support. The driver probe works also if placed under i2c controller node, but there is no actual i2c probing.
- "drm/tilcdc: Add drm bridge support for attaching drm bridge drivers"
- no change
Changes since first version of the series:
- "drm/tilcdc: Recover from sync lost error flood by resetting the LCDC"
- no change
- "drm/bridge: Add ti-tfp410 DVI transmitter driver"
- HDMI -> DVI
- DT Binding document
- Prepare for tfp410 connected trough i2c by optional reg property
- Require two port nodes
- Implementation
- Implement connector node functionality with in tfp410 bridge drive, but follow generic connector binding by pulling the ddc-i2c-bus property from the connector node.
- "drm/tilcdc: Add drm bridge support for attaching drm bridge drivers"
- Remove earlier change in TD binding document. There is no need to mention DRM implementation details, like bridge support, in DT binding.
The first patch is an independent on and I've been testing it for quite a while now.
The tfp410 bridge driver and the tilcdc bridge support are tested with BeagleBone DVI-D Cape Rev A3. The tfp410 bridge driver is missing a lot of features, because the DVI-D cape does not have too many wires connected. The missing features can be added later when they are needed.
Jyri Sarha (4):
drm/tilcdc: Recover from sync lost error flood by resetting the LCDC
dt-bindings: Move "ti,tfp410.txt" from display/ti to display/bridge drm/bridge: Add ti-tfp410 DVI transmitter driver drm/tilcdc: Add drm bridge support for attaching drm bridge drivers
.../bindings/display/bridge/ti,tfp410.txt | 46 +++ .../devicetree/bindings/display/ti/ti,tfp410.txt | 41 --- drivers/gpu/drm/bridge/Kconfig | 7 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 311 +++++++++++++++++++++ drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 26 +- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 7 +- drivers/gpu/drm/tilcdc/tilcdc_drv.h | 2 + drivers/gpu/drm/tilcdc/tilcdc_external.c | 140 ++++++++-- drivers/gpu/drm/tilcdc/tilcdc_external.h | 1 + 10 files changed, 521 insertions(+), 61 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt delete mode 100644 Documentation/devicetree/bindings/display/ti/ti,tfp410.txt create mode 100644 drivers/gpu/drm/bridge/ti-tfp410.c
Signature · 6 lines
1.9.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v4 1/4 drm/tilcdc: Recover from sync lost error flood by resetting the LCDC
Recover from sync lost error flood by resetting the LCDC instead of turning off the SYNC_LOST error IRQ. When LCDC starves on limited memory bandwidth it may sometimes result an error situation when the picture may have shifted couple of pixels to right and SYNC_LOST interrupt is generated on every frame. LCDC main reset recovers from this situation and causes a brief blanking on the screen.
--- drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-)
drivers/gpu/drm/tilcdc/tilcdc_crtc.c +25 -1
@@ -55,6 +55,7 @@ struct tilcdc_crtc {int sync_lost_count;bool frame_intact; +struct work_struct recover_work; };#define to_tilcdc_crtc (x) container_of(x, struct tilcdc_crtc, base)
@@ -252,6 +253,25 @@ static bool tilcdc_crtc_is_on(struct drm_crtc *crtc)return crtc->state && crtc->state->enable && crtc->state->active; } +static void tilcdc_crtc_recover_work (struct work_struct *work) +{ +struct tilcdc_crtc *tilcdc_crtc = + container_of(work, struct tilcdc_crtc, recover_work); +struct drm_crtc *crtc = &tilcdc_crtc->base; + +dev_info (crtc->dev->dev,"%s: Reset CRTC" , __func__); + +drm_modeset_lock_crtc (crtc,NULL ); + +if (!tilcdc_crtc_is_on (crtc)) + goto out; + +tilcdc_crtc_disable (crtc); +tilcdc_crtc_enable (crtc); +out: +drm_modeset_unlock_crtc (crtc); +} +static void tilcdc_crtc_destroy (struct drm_crtc *crtc) {struct tilcdc_crtc *tilcdc_crtc =to_tilcdc_crtc (crtc);
@@ -838,9 +858,12 @@ irqreturn_t tilcdc_crtc_irq(struct drm_crtc *crtc) tilcdc_crtc->frame_intact = false;if (tilcdc_crtc->sync_lost_count++ >SYNC_LOST_COUNT_LIMIT ) { -dev_err (dev->dev,"%s(0x%08x): Sync lost flood detected, disabling the interrupt" , __func__, stat); +dev_err (dev->dev,"%s(0x%08x): Sync lost flood detected, recovering" , __func__, stat); +queue_work (system_wq, + &tilcdc_crtc->recover_work);tilcdc_write (dev,LCDC_INT_ENABLE_CLR_REG ,LCDC_SYNC_LOST ); + tilcdc_crtc->sync_lost_count =0 ; } }
@@ -880,6 +903,7 @@ struct drm_crtc *tilcdc_crtc_create(struct drm_device *dev) "unref", unref_worker);spin_lock_init (&tilcdc_crtc->irq_lock); +INIT_WORK (&tilcdc_crtc->recover_work, tilcdc_crtc_recover_work); ret = drm_crtc_init_with_planes(dev, crtc, &tilcdc_crtc->primary,
Signature · 6 lines
1.9.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v4 3/4 drm/bridge: Add ti-tfp410 DVI transmitter driver
In reply to a message not in the archiveAdd very basic ti-tfp410 DVI transmitter driver. The only feature separating this from a completely dummy bridge is the EDID read support trough DDC I2C. Even that functionality should be in a separate generic connector driver. However, because of missing DRM infrastructure support the connector is implemented within the bridge driver. Some tfp410 HW specific features may be added later if needed, because there is a set of registers behind i2c if it is connected.
This implementation is tested against my new tilcdc bridge support and it works with BeagleBone DVI-D Cape Rev A3. A DT binding document is also updated.
--- .../bindings/display/bridge/ti,tfp410.txt | 9 +- drivers/gpu/drm/bridge/Kconfig | 7 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 311 +++++++++++++++++++++ 4 files changed, 326 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/bridge/ti-tfp410.c
Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt +7 -2
@@ -6,10 +6,15 @@ Required properties: Optional properties: - powerdown-gpios: power-down gpio +- reg: I2C address. If and only if present the device node + should be placed into the i2c controller node where the + tfp410 i2c is connected to. Required nodes: -- Video port 0 for DPI input -- Video port 1 for DVI output +- Video port 0 for DPI input [1]. +- Video port 1 for DVI output [1]. + +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt Example -------
drivers/gpu/drm/bridge/Kconfig +7 -0
@@ -81,6 +81,13 @@ config DRM_TOSHIBA_TC358767 ---help--- Toshiba TC358767 eDP bridge chip driver. +config DRM_TI_TFP410 + tristate "TI TFP410 DVI/HDMI bridge" + depends on OF + select DRM_KMS_HELPER + ---help--- + Texas Instruments TFP410 DVI/HDMI Transmitter driver + source "drivers/gpu/drm/bridge/analogix/Kconfig" source "drivers/gpu/drm/bridge/adv7511/Kconfig"
drivers/gpu/drm/bridge/Makefile +1 -0
@@ -11,3 +11,4 @@ obj-$(CONFIG_DRM_SII902X) += sii902x.o obj-$(CONFIG_DRM_TOSHIBA_TC358767) += tc358767.o obj-$(CONFIG_DRM_ANALOGIX_DP) += analogix/ obj-$(CONFIG_DRM_I2C_ADV7511) += adv7511/ +obj-$(CONFIG_DRM_TI_TFP410) += ti-tfp410.o
drivers/gpu/drm/bridge/ti-tfp410.c new file +311 -0
311 lines not on this page · raw message
Signature · 6 lines
1.9.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver
Quoted 282 lines · Jyri Sarha
Add very basic ti-tfp410 DVI transmitter driver. The only feature separating this from a completely dummy bridge is the EDID read support trough DDC I2C. Even that functionality should be in a separate generic connector driver. However, because of missing DRM infrastructure support the connector is implemented within the bridge driver. Some tfp410 HW specific features may be added later if needed, because there is a set of registers behind i2c if it is connected.
This implementation is tested against my new tilcdc bridge support and it works with BeagleBone DVI-D Cape Rev A3. A DT binding document is also updated.
Signed-off-by Jyri Sarha <[email protected]>--- .../bindings/display/bridge/ti,tfp410.txt | 9 +- drivers/gpu/drm/bridge/Kconfig | 7 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 311 +++++++++++++++++++++ 4 files changed, 326 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/bridge/ti-tfp410.cDocumentation/devicetree/bindings/display/bridge/ti,tfp410.txt +7
-2@@ -6,10 +6,15 @@ Required properties: Optional properties: - powerdown-gpios: power-down gpio +- reg: I2C address. If and only if present the device node + should be placed into the i2c controller node where the + tfp410 i2c is connected to. Required nodes: -- Video port 0 for DPI input -- Video port 1 for DVI output +- Video port 0 for DPI input [1]. +- Video port 1 for DVI output [1]. + +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt Example -------drivers/gpu/drm/bridge/Kconfig +7
-0@@ -81,6 +81,13 @@ config DRM_TOSHIBA_TC358767 ---help--- Toshiba TC358767 eDP bridge chip driver. +config DRM_TI_TFP410 + tristate "TI TFP410 DVI/HDMI bridge" + depends on OF + select DRM_KMS_HELPER + ---help--- + Texas Instruments TFP410 DVI/HDMI Transmitter driver + source "drivers/gpu/drm/bridge/analogix/Kconfig" source "drivers/gpu/drm/bridge/adv7511/Kconfig"drivers/gpu/drm/bridge/Makefile +1
-0@@ -11,3 +11,4 @@ obj-$(CONFIG_DRM_SII902X) += sii902x.o obj-$(CONFIG_DRM_TOSHIBA_TC358767) += tc358767.o obj-$(CONFIG_DRM_ANALOGIX_DP) += analogix/ obj-$(CONFIG_DRM_I2C_ADV7511) += adv7511/ +obj-$(CONFIG_DRM_TI_TFP410) += ti-tfp410.odrivers/gpu/drm/bridge/ti-tfp410.c new file +206
-0@@ -0,0 +1,311 @@ +/* +* Copyright (C) 2016 Texas Instruments +* Author: Jyri Sarha <[email protected]> +* +* This program is free software; you can redistribute it and/or modify it +* under the terms of the GNU General Public License version 2 as published by +* the Free Software Foundation. +* +*/ + +#include <linux/module.h> +#include <linux/of_graph.h> +#include <linux/platform_device.h> +#include <linux/i2c.h> + +#include <drm/drmP.h> +#include <drm/drm_atomic_helper.h> +#include <drm/drm_crtc.h> +#include <drm/drm_crtc_helper.h> + +struct tfp410 { +struct drm_bridge bridge; +struct drm_connector connector; + +struct i2c_adapter *ddc; + +struct device *dev; +}; + +static inline struct tfp410 * +drm_bridge_to_tfp410 (struct drm_bridge *bridge) +{ + return container_of(bridge, struct tfp410, bridge); +} + +static inline struct tfp410 * +drm_connector_to_tfp410 (struct drm_connector *connector) +{ + return container_of(connector, struct tfp410, connector); +} + +static int tfp410_get_modes (struct drm_connector *connector) +{ +struct tfp410 *dvi =drm_connector_to_tfp410 (connector); +struct edid *edid; +int ret; + +if (!dvi->ddc) + goto fallback; + + edid =drm_get_edid (connector, dvi->ddc); +if (!edid) { +DRM_INFO ("EDID read failed. Fallback to standard modes\n" ); + goto fallback; + } + +drm_mode_connector_update_edid_property (connector, edid); + +return drm_add_edid_modes (connector, edid); +fallback: +/* No EDID, fallback on the XGA standard modes */ + ret =drm_add_modes_noedid (connector,1920 ,1200 ); + +/* And prefer a mode pretty much anything can handle */ +drm_set_preferred_mode (connector,1024 ,768 ); + +return ret; +} + +static const struct drm_connector_helper_funcs tfp410_con_helper_funcs = { + .get_modes = tfp410_get_modes, +}; + +static enum drm_connector_status +tfp410_connector_detect (struct drm_connector *connector,bool force) +{ +struct tfp410 *dvi =drm_connector_to_tfp410 (connector); + +if (dvi->ddc) { +if (drm_probe_ddc (dvi->ddc)) +return connector_status_connected; +else +return connector_status_disconnected; + } + +return connector_status_unknown; +} + +static const struct drm_connector_funcs tfp410_con_funcs = { + .dpms = drm_atomic_helper_connector_dpms, + .detect = tfp410_connector_detect, + .fill_modes = drm_helper_probe_single_connector_modes, + .destroy = drm_connector_cleanup, + .reset = drm_atomic_helper_connector_reset, + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state, + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, +}; + +static int tfp410_attach (struct drm_bridge *bridge) +{ +struct tfp410 *dvi =drm_bridge_to_tfp410 (bridge); +int ret; + +if (!bridge->encoder) { +dev_err (dvi->dev,"Missing encoder\n" ); +return -ENODEV ; + } + +drm_connector_helper_add (&dvi->connector, + &tfp410_con_helper_funcs); + ret =drm_connector_init (bridge->dev, &dvi->connector, + &tfp410_con_funcs,DRM_MODE_CONNECTOR_HDMIA ); +if (ret) { +dev_err (dvi->dev,"drm_connector_init() failed: %d\n" , ret); +return ret; + } + +drm_mode_connector_attach_encoder (&dvi->connector, + bridge->encoder); + +return 0 ; +} + +static const struct drm_bridge_funcs tfp410_bridge_funcs = { + .attach = tfp410_attach, +}; + +static int tfp410_get_connector_ddc (struct tfp410 *dvi) +{ +struct device_node *ep =NULL , *connector_node =NULL ; +struct device_node *ddc_phandle =NULL ; +int ret =0 ; + +/* port@1 is the connector node */ + ep =of_graph_get_endpoint_by_regs (dvi->dev->of_node,1 ,-1 ); +if (!ep) + goto fail; + + connector_node =of_graph_get_remote_port_parent (ep); +if (!connector_node) + goto fail; + + ddc_phandle =of_parse_phandle (connector_node,"ddc-i2c-bus" ,0 ); +if (!ddc_phandle) + goto fail; + + dvi->ddc =of_get_i2c_adapter_by_node (ddc_phandle); +if (dvi->ddc) +dev_info (dvi->dev,"Connector's ddc i2c bus found\n" ); +else + ret = -EPROBE_DEFER ; + +fail: +of_node_put (ep); +of_node_put (connector_node); +of_node_put (ddc_phandle); +return ret; +} + +static int tfp410_init (struct device *dev) +{ +struct tfp410 *dvi; +int ret; + +if (!dev->of_node) { +dev_err (dev,"device-tree data is missing\n" ); +return -ENXIO ; + } + + dvi =devm_kzalloc (dev,sizeof (*dvi),GFP_KERNEL ); +if (!dvi) +return -ENOMEM ; +dev_set_drvdata (dev, dvi); + + dvi->bridge.funcs = &tfp410_bridge_funcs; + dvi->bridge.of_node = dev->of_node; + dvi->dev = dev; + + ret =tfp410_get_connector_ddc (dvi); +if (ret) + goto fail; + + ret =drm_bridge_add (&dvi->bridge); +if (ret) { +dev_err (dev,"drm_bridge_add() failed: %d\n" , ret); + goto fail; + } + +return 0 ; +fail: +i2c_put_adapter (dvi->ddc); +return ret; +} + +static int tfp410_fini (struct device *dev) +{ +struct tfp410 *dvi =dev_get_drvdata (dev); + +drm_bridge_remove (&dvi->bridge); + +if (dvi->ddc) +i2c_put_adapter (dvi->ddc); + +return 0 ; +} +
drivers/gpu/drm/bridge/ti-tfp410.c line 216
Quoted 10 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +10
-0+static int tfp410_probe (struct platform_device *pdev) +{ +return tfp410_init (&pdev->dev); +} + +static int tfp410_remove (struct platform_device *pdev) +{ +return tfp410_fini (&pdev->dev); +} +
Argh... I think I should still put all i2c code between #if defined(CONFIG_I2C) || defined(CONFIG_I2C_MODULE)
#endif
Otherwise I think this is now finally ready.
Quoted 86 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +85
-0+/* There is currently no i2c functionality. */ +static int tfp410_i2c_probe (struct i2c_client *client, +const struct i2c_device_id *id) +{ +int reg; + +if (!client->dev.of_node || +of_property_read_u32 (client->dev.of_node,"reg" , ®)) { +dev_err (&client->dev, +"Can't get i2c reg property from device-tree\n" ); +return -ENXIO ; + } + +return tfp410_init (&client->dev); +} + +static int tfp410_i2c_remove (struct i2c_client *client) +{ +return tfp410_fini (&client->dev); +} + +static const struct of_device_id tfp410_match[] = { + { .compatible ="ti,tfp410" }, + {}, +}; +MODULE_DEVICE_TABLE (of, tfp410_match); + +struct platform_driver tfp410_platform_driver = { + .probe = tfp410_probe, + .remove = tfp410_remove, + .driver = { + .name ="tfp410-bridge" , + .of_match_table = tfp410_match, + }, +}; + +static const struct i2c_device_id tfp410_i2c_ids[] = { + {"tfp410" ,0 }, + { } +}; +MODULE_DEVICE_TABLE (i2c, tfp410_i2c_ids); + +static struct i2c_driver tfp410_i2c_driver = { + .driver = { + .name ="tfp410" , + .of_match_table =of_match_ptr (tfp410_match), + }, + .id_table = tfp410_i2c_ids, + .probe = tfp410_i2c_probe, + .remove = tfp410_i2c_remove, +}; + +static struct { +uint i2c:1 ; +uint platform:1 ; +} tfp410_registered_driver; + +static int __init tfp410_module_init (void ) +{ +int ret; + + ret =i2c_add_driver (&tfp410_i2c_driver); +if (ret) +pr_err ("%s: registering i2c driver failed: %d" , + __func__, ret); +else + tfp410_registered_driver.i2c =1 ; + + ret =platform_driver_register (&tfp410_platform_driver); +if (ret) +pr_err ("%s: registering platform driver failed: %d" , + __func__, ret); +else + tfp410_registered_driver.platform =1 ; + +if (tfp410_registered_driver.i2c || + tfp410_registered_driver.platform) +return 0 ; + +return ret; +} +module_init (tfp410_module_init); + +static void __exit tfp410_module_exit(void) +{
drivers/gpu/drm/bridge/ti-tfp410.c line 311
Quoted 10 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +10
-0+if (tfp410_registered_driver.i2c) +i2c_del_driver (&tfp410_i2c_driver); +if (tfp410_registered_driver.platform) +platform_driver_unregister (&tfp410_platform_driver); +} +module_exit (tfp410_module_exit); + +MODULE_AUTHOR ("Jyri Sarha <[email protected]>" ); +MODULE_DESCRIPTION ("TI TFP410 DVI bridge driver" ); +MODULE_LICENSE ("GPL" );
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver
Quoted 288 lines · Jyri Sarha
Quoted 287 lines · Jyri Sarha
Add very basic ti-tfp410 DVI transmitter driver. The only feature separating this from a completely dummy bridge is the EDID read support trough DDC I2C. Even that functionality should be in a separate generic connector driver. However, because of missing DRM infrastructure support the connector is implemented within the bridge driver. Some tfp410 HW specific features may be added later if needed, because there is a set of registers behind i2c if it is connected.
This implementation is tested against my new tilcdc bridge support and it works with BeagleBone DVI-D Cape Rev A3. A DT binding document is also updated.
Signed-off-by Jyri Sarha <[email protected]>--- .../bindings/display/bridge/ti,tfp410.txt | 9 +- drivers/gpu/drm/bridge/Kconfig | 7 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 311 +++++++++++++++++++++ 4 files changed, 326 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/bridge/ti-tfp410.cDocumentation/devicetree/bindings/display/bridge/ti,tfp410.txt +7
-2@@ -6,10 +6,15 @@ Required properties: Optional properties: - powerdown-gpios: power-down gpio +- reg: I2C address. If and only if present the device node + should be placed into the i2c controller node where the + tfp410 i2c is connected to. Required nodes: -- Video port 0 for DPI input -- Video port 1 for DVI output +- Video port 0 for DPI input [1]. +- Video port 1 for DVI output [1]. + +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt Example -------drivers/gpu/drm/bridge/Kconfig +7
-0@@ -81,6 +81,13 @@ config DRM_TOSHIBA_TC358767 ---help--- Toshiba TC358767 eDP bridge chip driver. +config DRM_TI_TFP410 + tristate "TI TFP410 DVI/HDMI bridge" + depends on OF + select DRM_KMS_HELPER + ---help--- + Texas Instruments TFP410 DVI/HDMI Transmitter driver + source "drivers/gpu/drm/bridge/analogix/Kconfig" source "drivers/gpu/drm/bridge/adv7511/Kconfig"drivers/gpu/drm/bridge/Makefile +1
-0@@ -11,3 +11,4 @@ obj-$(CONFIG_DRM_SII902X) += sii902x.o obj-$(CONFIG_DRM_TOSHIBA_TC358767) += tc358767.o obj-$(CONFIG_DRM_ANALOGIX_DP) += analogix/ obj-$(CONFIG_DRM_I2C_ADV7511) += adv7511/ +obj-$(CONFIG_DRM_TI_TFP410) += ti-tfp410.odrivers/gpu/drm/bridge/ti-tfp410.c new file +211
-0@@ -0,0 +1,311 @@ +/* +* Copyright (C) 2016 Texas Instruments +* Author: Jyri Sarha <[email protected]> +* +* This program is free software; you can redistribute it and/or modify it +* under the terms of the GNU General Public License version 2 as published by +* the Free Software Foundation. +* +*/ + +#include <linux/module.h> +#include <linux/of_graph.h> +#include <linux/platform_device.h> +#include <linux/i2c.h> + +#include <drm/drmP.h> +#include <drm/drm_atomic_helper.h> +#include <drm/drm_crtc.h> +#include <drm/drm_crtc_helper.h> + +struct tfp410 { +struct drm_bridge bridge; +struct drm_connector connector; + +struct i2c_adapter *ddc; + +struct device *dev; +}; + +static inline struct tfp410 * +drm_bridge_to_tfp410 (struct drm_bridge *bridge) +{ + return container_of(bridge, struct tfp410, bridge); +} + +static inline struct tfp410 * +drm_connector_to_tfp410 (struct drm_connector *connector) +{ + return container_of(connector, struct tfp410, connector); +} + +static int tfp410_get_modes (struct drm_connector *connector) +{ +struct tfp410 *dvi =drm_connector_to_tfp410 (connector); +struct edid *edid; +int ret; + +if (!dvi->ddc) + goto fallback; + + edid =drm_get_edid (connector, dvi->ddc); +if (!edid) { +DRM_INFO ("EDID read failed. Fallback to standard modes\n" ); + goto fallback; + } + +drm_mode_connector_update_edid_property (connector, edid); + +return drm_add_edid_modes (connector, edid); +fallback: +/* No EDID, fallback on the XGA standard modes */ + ret =drm_add_modes_noedid (connector,1920 ,1200 ); + +/* And prefer a mode pretty much anything can handle */ +drm_set_preferred_mode (connector,1024 ,768 ); + +return ret; +} + +static const struct drm_connector_helper_funcs tfp410_con_helper_funcs = { + .get_modes = tfp410_get_modes, +}; + +static enum drm_connector_status +tfp410_connector_detect (struct drm_connector *connector,bool force) +{ +struct tfp410 *dvi =drm_connector_to_tfp410 (connector); + +if (dvi->ddc) { +if (drm_probe_ddc (dvi->ddc)) +return connector_status_connected; +else +return connector_status_disconnected; + } + +return connector_status_unknown; +} + +static const struct drm_connector_funcs tfp410_con_funcs = { + .dpms = drm_atomic_helper_connector_dpms, + .detect = tfp410_connector_detect, + .fill_modes = drm_helper_probe_single_connector_modes, + .destroy = drm_connector_cleanup, + .reset = drm_atomic_helper_connector_reset, + .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state, + .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, +}; + +static int tfp410_attach (struct drm_bridge *bridge) +{ +struct tfp410 *dvi =drm_bridge_to_tfp410 (bridge); +int ret; + +if (!bridge->encoder) { +dev_err (dvi->dev,"Missing encoder\n" ); +return -ENODEV ; + } + +drm_connector_helper_add (&dvi->connector, + &tfp410_con_helper_funcs); + ret =drm_connector_init (bridge->dev, &dvi->connector, + &tfp410_con_funcs,DRM_MODE_CONNECTOR_HDMIA ); +if (ret) { +dev_err (dvi->dev,"drm_connector_init() failed: %d\n" , ret); +return ret; + } + +drm_mode_connector_attach_encoder (&dvi->connector, + bridge->encoder); + +return 0 ; +} + +static const struct drm_bridge_funcs tfp410_bridge_funcs = { + .attach = tfp410_attach, +}; + +static int tfp410_get_connector_ddc (struct tfp410 *dvi) +{ +struct device_node *ep =NULL , *connector_node =NULL ; +struct device_node *ddc_phandle =NULL ; +int ret =0 ; + +/* port@1 is the connector node */ + ep =of_graph_get_endpoint_by_regs (dvi->dev->of_node,1 ,-1 ); +if (!ep) + goto fail; + + connector_node =of_graph_get_remote_port_parent (ep); +if (!connector_node) + goto fail; + + ddc_phandle =of_parse_phandle (connector_node,"ddc-i2c-bus" ,0 ); +if (!ddc_phandle) + goto fail; + + dvi->ddc =of_get_i2c_adapter_by_node (ddc_phandle); +if (dvi->ddc) +dev_info (dvi->dev,"Connector's ddc i2c bus found\n" ); +else + ret = -EPROBE_DEFER ; + +fail: +of_node_put (ep); +of_node_put (connector_node); +of_node_put (ddc_phandle); +return ret; +} + +static int tfp410_init (struct device *dev) +{ +struct tfp410 *dvi; +int ret; + +if (!dev->of_node) { +dev_err (dev,"device-tree data is missing\n" ); +return -ENXIO ; + } + + dvi =devm_kzalloc (dev,sizeof (*dvi),GFP_KERNEL ); +if (!dvi) +return -ENOMEM ; +dev_set_drvdata (dev, dvi); + + dvi->bridge.funcs = &tfp410_bridge_funcs; + dvi->bridge.of_node = dev->of_node; + dvi->dev = dev; + + ret =tfp410_get_connector_ddc (dvi); +if (ret) + goto fail; + + ret =drm_bridge_add (&dvi->bridge); +if (ret) { +dev_err (dev,"drm_bridge_add() failed: %d\n" , ret); + goto fail; + } + +return 0 ; +fail: +i2c_put_adapter (dvi->ddc); +return ret; +} + +static int tfp410_fini (struct device *dev) +{ +struct tfp410 *dvi =dev_get_drvdata (dev); + +drm_bridge_remove (&dvi->bridge); + +if (dvi->ddc) +i2c_put_adapter (dvi->ddc); + +return 0 ; +} + +static int tfp410_probe (struct platform_device *pdev) +{ +return tfp410_init (&pdev->dev); +} +
Quoted 8 lines
drivers/gpu/drm/bridge/ti-tfp410.c line 216
Quoted 5 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +5
-0+static int tfp410_remove (struct platform_device *pdev) +{ +return tfp410_fini (&pdev->dev); +} +Argh... I think I should still put all i2c code between #if
defined(CONFIG_I2C)||defined(CONFIG_I2C_MODULE)
ITYM
#if IS_ENABLED(CONFIG_I2C)
BR,
Jani.
Quoted 106 lines
#endif
Otherwise I think this is now finally ready.
Quoted 86 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +85
-0+/* There is currently no i2c functionality. */ +static int tfp410_i2c_probe (struct i2c_client *client, +const struct i2c_device_id *id) +{ +int reg; + +if (!client->dev.of_node || +of_property_read_u32 (client->dev.of_node,"reg" , ®)) { +dev_err (&client->dev, +"Can't get i2c reg property from device-tree\n" ); +return -ENXIO ; + } + +return tfp410_init (&client->dev); +} + +static int tfp410_i2c_remove (struct i2c_client *client) +{ +return tfp410_fini (&client->dev); +} + +static const struct of_device_id tfp410_match[] = { + { .compatible ="ti,tfp410" }, + {}, +}; +MODULE_DEVICE_TABLE (of, tfp410_match); + +struct platform_driver tfp410_platform_driver = { + .probe = tfp410_probe, + .remove = tfp410_remove, + .driver = { + .name ="tfp410-bridge" , + .of_match_table = tfp410_match, + }, +}; + +static const struct i2c_device_id tfp410_i2c_ids[] = { + {"tfp410" ,0 }, + { } +}; +MODULE_DEVICE_TABLE (i2c, tfp410_i2c_ids); + +static struct i2c_driver tfp410_i2c_driver = { + .driver = { + .name ="tfp410" , + .of_match_table =of_match_ptr (tfp410_match), + }, + .id_table = tfp410_i2c_ids, + .probe = tfp410_i2c_probe, + .remove = tfp410_i2c_remove, +}; + +static struct { +uint i2c:1 ; +uint platform:1 ; +} tfp410_registered_driver; + +static int __init tfp410_module_init (void ) +{ +int ret; + + ret =i2c_add_driver (&tfp410_i2c_driver); +if (ret) +pr_err ("%s: registering i2c driver failed: %d" , + __func__, ret); +else + tfp410_registered_driver.i2c =1 ; + + ret =platform_driver_register (&tfp410_platform_driver); +if (ret) +pr_err ("%s: registering platform driver failed: %d" , + __func__, ret); +else + tfp410_registered_driver.platform =1 ; + +if (tfp410_registered_driver.i2c || + tfp410_registered_driver.platform) +return 0 ; + +return ret; +} +module_init (tfp410_module_init); + +static void __exit tfp410_module_exit(void) +{drivers/gpu/drm/bridge/ti-tfp410.c line 311
Quoted 10 lines
drivers/gpu/drm/bridge/ti-tfp410.c new file +10
-0+if (tfp410_registered_driver.i2c) +i2c_del_driver (&tfp410_i2c_driver); +if (tfp410_registered_driver.platform) +platform_driver_unregister (&tfp410_platform_driver); +} +module_exit (tfp410_module_exit); + +MODULE_AUTHOR ("Jyri Sarha <[email protected]>" ); +MODULE_DESCRIPTION ("TI TFP410 DVI bridge driver" ); +MODULE_LICENSE ("GPL" );_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 5 lines
Jani Nikula, Intel Open Source Technology Center _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
A message that is not in the archive (sent off-list or not yet received): 2943f3cb3ea913686bc63e8496df63c82ce0f334.1479825908.git.jsarha-l0cyMroinI0@public.gmane.org
Rob Herring
Acked-byRe: [PATCH v4 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver
Quoted 8 lines · Jyri Sarha
Add very basic ti-tfp410 DVI transmitter driver. The only feature separating this from a completely dummy bridge is the EDID read support trough DDC I2C. Even that functionality should be in a separate generic connector driver. However, because of missing DRM infrastructure support the connector is implemented within the bridge driver. Some tfp410 HW specific features may be added later if needed, because there is a set of registers behind i2c if it is connected.
Quoted 7 lines
This implementation is tested against my new tilcdc bridge support and it works with BeagleBone DVI-D Cape Rev A3. A DT binding document is also updated.
Signed-off-by Jyri Sarha <[email protected]>--- .../bindings/display/bridge/ti,tfp410.txt | 9 +-
Quoted 5 lines
drivers/gpu/drm/bridge/Kconfig | 7 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/ti-tfp410.c | 311 +++++++++++++++++++++ 4 files changed, 326 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/bridge/ti-tfp410.c
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v4 4/4 drm/tilcdc: Add drm bridge support for attaching drm bridge drivers
In reply to a message not in the archiveAdds drm bride support for attaching drm bridge drivers to tilcdc. The decision whether a video port leads to an external encoder or bridge is made simply based on remote device's compatible string. The code has been tested with BeagleBone-Black with and without BeagleBone DVI-D Cape Rev A3 using ti-tfp410 driver.
--- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 7 +- drivers/gpu/drm/tilcdc/tilcdc_drv.h | 2 + drivers/gpu/drm/tilcdc/tilcdc_external.c | 140 +++++++++++++++++++++++++++---- drivers/gpu/drm/tilcdc/tilcdc_external.h | 1 + 4 files changed, 131 insertions(+), 19 deletions(-)
drivers/gpu/drm/tilcdc/tilcdc_drv.c +6 -1
@@ -384,9 +384,14 @@ static int tilcdc_init(struct drm_driver *ddrv, struct device *dev) ret =tilcdc_add_external_encoders (ddev);if (ret <0 ) goto init_failed; + }else { + ret =tilcdc_attach_remote_device (ddev); +if (ret) + goto init_failed; } -if ((priv->num_encoders ==0 ) || (priv->num_connectors ==0 )) { +if (!priv->remote_encoder && + ((priv->num_encoders ==0 ) || (priv->num_connectors ==0 ))) {dev_err (dev,"no encoders/connectors found\n" ); ret = -ENXIO ; goto init_failed;
drivers/gpu/drm/tilcdc/tilcdc_drv.h +2 -0
@@ -90,6 +90,8 @@ struct tilcdc_drm_private {struct drm_connector *connectors[8 ];const struct drm_connector_helper_funcs *connector_funcs[8 ]; +struct drm_encoder *remote_encoder; +bool is_registered;bool is_componentized; };
drivers/gpu/drm/tilcdc/tilcdc_external.c +122 -18
167 lines not on this page · raw message
drivers/gpu/drm/tilcdc/tilcdc_external.h +1 -0
@@ -22,4 +22,5 @@void tilcdc_remove_external_encoders (struct drm_device *dev);int tilcdc_get_external_components (struct device *dev,struct component_match **match); +int tilcdc_attach_remote_device (struct drm_device *ddev);#endif /* __TILCDC_SLAVE_H__ */
Signature · 6 lines
1.9.1 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH v4 2/4 dt-bindings: Move "ti, tfp410.txt" from display/ti to display/bridge
In reply to Jyri SarhaMove "ti,tfp410.txt" from display/ti to display/bridge before adding generic (non omapdrm/dss specific) implementation and new features.
--- .../bindings/display/bridge/ti,tfp410.txt | 41 ++++++++++++++++++++++ .../devicetree/bindings/display/ti/ti,tfp410.txt | 41 ---------------------- 2 files changed, 41 insertions(+), 41 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt delete mode 100644 Documentation/devicetree/bindings/display/ti/ti,tfp410.txt
Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt new file +41 -0
@@ -0,0 +1,41 @@ +TFP410 DPI to DVI encoder +========================= + +Required properties: +- compatible: "ti,tfp410" + +Optional properties: +- powerdown-gpios: power-down gpio + +Required nodes: +- Video port 0 for DPI input +- Video port 1 for DVI output + +Example +------- + +tfp410: encoder@0 { + compatible = "ti,tfp410"; + powerdown-gpios = <&twl_gpio 2 GPIO_ACTIVE_LOW>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + + tfp410_in: endpoint@0 { + remote-endpoint = <&dpi_out>; + }; + }; + + port@1 { + reg = <1>; + + tfp410_out: endpoint@0 { + remote-endpoint = <&dvi_connector_in>; + }; + }; + }; +};
Documentation/devicetree/bindings/display/ti/ti,tfp410.txt deleted +0 -41
41 lines not on this page · raw message
Signature · 6 lines
1.9.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v4 2/4] dt-bindings: Move "ti, tfp410.txt" from display/ti to display/bridge
Quoted 10 lines · Jyri Sarha
Move "ti,tfp410.txt" from display/ti to display/bridge before adding generic (non omapdrm/dss specific) implementation and new features.
Signed-off-by Jyri Sarha <[email protected]>--- .../bindings/display/bridge/ti,tfp410.txt | 41 ++++++++++++++++++++++ .../devicetree/bindings/display/ti/ti,tfp410.txt | 41 ---------------------- 2 files changed, 41 insertions(+), 41 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt delete mode 100644 Documentation/devicetree/bindings/display/ti/ti,tfp410.txt
Next time, use git format-patch -M option.
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel