2018-04-18 22:40:29 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
|
|
|
/*
|
|
|
|
* THC63LVD1024 LVDS to parallel data DRM bridge driver.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2018 Jacopo Mondi <jacopo+renesas@jmondi.org>
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/gpio/consumer.h>
|
2019-05-20 02:36:36 +08:00
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/of.h>
|
2018-04-18 22:40:29 +08:00
|
|
|
#include <linux/of_graph.h>
|
2019-05-20 02:36:36 +08:00
|
|
|
#include <linux/platform_device.h>
|
2018-04-18 22:40:29 +08:00
|
|
|
#include <linux/regulator/consumer.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
|
2019-05-20 02:36:36 +08:00
|
|
|
#include <drm/drm_bridge.h>
|
|
|
|
#include <drm/drm_panel.h>
|
|
|
|
|
2018-04-18 22:40:29 +08:00
|
|
|
enum thc63_ports {
|
|
|
|
THC63_LVDS_IN0,
|
|
|
|
THC63_LVDS_IN1,
|
|
|
|
THC63_RGB_OUT0,
|
|
|
|
THC63_RGB_OUT1,
|
|
|
|
};
|
|
|
|
|
|
|
|
struct thc63_dev {
|
|
|
|
struct device *dev;
|
|
|
|
|
|
|
|
struct regulator *vcc;
|
|
|
|
|
|
|
|
struct gpio_desc *pdwn;
|
|
|
|
struct gpio_desc *oe;
|
|
|
|
|
|
|
|
struct drm_bridge bridge;
|
|
|
|
struct drm_bridge *next;
|
2019-03-05 03:56:07 +08:00
|
|
|
|
|
|
|
struct drm_bridge_timings timings;
|
2018-04-18 22:40:29 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
static inline struct thc63_dev *to_thc63(struct drm_bridge *bridge)
|
|
|
|
{
|
|
|
|
return container_of(bridge, struct thc63_dev, bridge);
|
|
|
|
}
|
|
|
|
|
drm/bridge: Extend bridge API to disable connector creation
Most bridge drivers create a DRM connector to model the connector at the
output of the bridge. This model is historical and has worked pretty
well so far, but causes several issues:
- It prevents supporting more complex display pipelines where DRM
connector operations are split over multiple components. For instance a
pipeline with a bridge connected to the DDC signals to read EDID data,
and another one connected to the HPD signal to detect connection and
disconnection, will not be possible to support through this model.
- It requires every bridge driver to implement similar connector
handling code, resulting in code duplication.
- It assumes that a bridge will either be wired to a connector or to
another bridge, but doesn't support bridges that can be used in both
positions very well (although there is some ad-hoc support for this in
the analogix_dp bridge driver).
In order to solve these issues, ownership of the connector should be
moved to the display controller driver (where it can be implemented
using helpers provided by the core).
Extend the bridge API to allow disabling connector creation in bridge
drivers as a first step towards the new model. The new flags argument to
the bridge .attach() operation allows instructing the bridge driver to
skip creating a connector. Unconditionally set the new flags argument to
0 for now to keep the existing behaviour, and modify all existing bridge
drivers to return an error when connector creation is not requested as
they don't support this feature yet.
The change is based on the following semantic patch, with manual review
and edits.
@ rule1 @
identifier funcs;
identifier fn;
@@
struct drm_bridge_funcs funcs = {
...,
.attach = fn
};
@ depends on rule1 @
identifier rule1.fn;
identifier bridge;
statement S, S1;
@@
int fn(
struct drm_bridge *bridge
+ , enum drm_bridge_attach_flags flags
)
{
... when != S
+ if (flags & DRM_BRIDGE_ATTACH_NO_CONNECTOR) {
+ DRM_ERROR("Fix bridge driver to make connector optional!");
+ return -EINVAL;
+ }
+
S1
...
}
@ depends on rule1 @
identifier rule1.fn;
identifier bridge, flags;
expression E1, E2, E3;
@@
int fn(
struct drm_bridge *bridge,
enum drm_bridge_attach_flags flags
) {
<...
drm_bridge_attach(E1, E2, E3
+ , flags
)
...>
}
@@
expression E1, E2, E3;
@@
drm_bridge_attach(E1, E2, E3
+ , 0
)
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Tested-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200226112514.12455-10-laurent.pinchart@ideasonboard.com
2020-02-26 19:24:29 +08:00
|
|
|
static int thc63_attach(struct drm_bridge *bridge,
|
|
|
|
enum drm_bridge_attach_flags flags)
|
2018-04-18 22:40:29 +08:00
|
|
|
{
|
|
|
|
struct thc63_dev *thc63 = to_thc63(bridge);
|
|
|
|
|
drm/bridge: Extend bridge API to disable connector creation
Most bridge drivers create a DRM connector to model the connector at the
output of the bridge. This model is historical and has worked pretty
well so far, but causes several issues:
- It prevents supporting more complex display pipelines where DRM
connector operations are split over multiple components. For instance a
pipeline with a bridge connected to the DDC signals to read EDID data,
and another one connected to the HPD signal to detect connection and
disconnection, will not be possible to support through this model.
- It requires every bridge driver to implement similar connector
handling code, resulting in code duplication.
- It assumes that a bridge will either be wired to a connector or to
another bridge, but doesn't support bridges that can be used in both
positions very well (although there is some ad-hoc support for this in
the analogix_dp bridge driver).
In order to solve these issues, ownership of the connector should be
moved to the display controller driver (where it can be implemented
using helpers provided by the core).
Extend the bridge API to allow disabling connector creation in bridge
drivers as a first step towards the new model. The new flags argument to
the bridge .attach() operation allows instructing the bridge driver to
skip creating a connector. Unconditionally set the new flags argument to
0 for now to keep the existing behaviour, and modify all existing bridge
drivers to return an error when connector creation is not requested as
they don't support this feature yet.
The change is based on the following semantic patch, with manual review
and edits.
@ rule1 @
identifier funcs;
identifier fn;
@@
struct drm_bridge_funcs funcs = {
...,
.attach = fn
};
@ depends on rule1 @
identifier rule1.fn;
identifier bridge;
statement S, S1;
@@
int fn(
struct drm_bridge *bridge
+ , enum drm_bridge_attach_flags flags
)
{
... when != S
+ if (flags & DRM_BRIDGE_ATTACH_NO_CONNECTOR) {
+ DRM_ERROR("Fix bridge driver to make connector optional!");
+ return -EINVAL;
+ }
+
S1
...
}
@ depends on rule1 @
identifier rule1.fn;
identifier bridge, flags;
expression E1, E2, E3;
@@
int fn(
struct drm_bridge *bridge,
enum drm_bridge_attach_flags flags
) {
<...
drm_bridge_attach(E1, E2, E3
+ , flags
)
...>
}
@@
expression E1, E2, E3;
@@
drm_bridge_attach(E1, E2, E3
+ , 0
)
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Tested-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200226112514.12455-10-laurent.pinchart@ideasonboard.com
2020-02-26 19:24:29 +08:00
|
|
|
return drm_bridge_attach(bridge->encoder, thc63->next, bridge, flags);
|
2018-04-18 22:40:29 +08:00
|
|
|
}
|
|
|
|
|
2018-08-22 22:04:06 +08:00
|
|
|
static enum drm_mode_status thc63_mode_valid(struct drm_bridge *bridge,
|
2020-05-26 09:14:48 +08:00
|
|
|
const struct drm_display_info *info,
|
2018-08-22 22:04:06 +08:00
|
|
|
const struct drm_display_mode *mode)
|
|
|
|
{
|
2019-03-05 03:56:07 +08:00
|
|
|
struct thc63_dev *thc63 = to_thc63(bridge);
|
|
|
|
unsigned int min_freq;
|
|
|
|
unsigned int max_freq;
|
|
|
|
|
2018-08-22 22:04:06 +08:00
|
|
|
/*
|
2019-03-05 03:56:07 +08:00
|
|
|
* The THC63LVD1024 pixel rate range is 8 to 135 MHz in all modes but
|
|
|
|
* dual-in, single-out where it is 40 to 150 MHz. As dual-in, dual-out
|
|
|
|
* isn't supported by the driver yet, simply derive the limits from the
|
|
|
|
* input mode.
|
2018-08-22 22:04:06 +08:00
|
|
|
*/
|
2019-03-05 03:56:07 +08:00
|
|
|
if (thc63->timings.dual_link) {
|
|
|
|
min_freq = 40000;
|
|
|
|
max_freq = 150000;
|
|
|
|
} else {
|
|
|
|
min_freq = 8000;
|
|
|
|
max_freq = 135000;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (mode->clock < min_freq)
|
2018-08-22 22:04:06 +08:00
|
|
|
return MODE_CLOCK_LOW;
|
|
|
|
|
2019-03-05 03:56:07 +08:00
|
|
|
if (mode->clock > max_freq)
|
2018-08-22 22:04:06 +08:00
|
|
|
return MODE_CLOCK_HIGH;
|
|
|
|
|
|
|
|
return MODE_OK;
|
|
|
|
}
|
|
|
|
|
2018-04-18 22:40:29 +08:00
|
|
|
static void thc63_enable(struct drm_bridge *bridge)
|
|
|
|
{
|
|
|
|
struct thc63_dev *thc63 = to_thc63(bridge);
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = regulator_enable(thc63->vcc);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(thc63->dev,
|
|
|
|
"Failed to enable regulator \"vcc\": %d\n", ret);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
gpiod_set_value(thc63->pdwn, 0);
|
|
|
|
gpiod_set_value(thc63->oe, 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void thc63_disable(struct drm_bridge *bridge)
|
|
|
|
{
|
|
|
|
struct thc63_dev *thc63 = to_thc63(bridge);
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
gpiod_set_value(thc63->oe, 0);
|
|
|
|
gpiod_set_value(thc63->pdwn, 1);
|
|
|
|
|
|
|
|
ret = regulator_disable(thc63->vcc);
|
|
|
|
if (ret)
|
|
|
|
dev_err(thc63->dev,
|
|
|
|
"Failed to disable regulator \"vcc\": %d\n", ret);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct drm_bridge_funcs thc63_bridge_func = {
|
|
|
|
.attach = thc63_attach,
|
2018-08-22 22:04:06 +08:00
|
|
|
.mode_valid = thc63_mode_valid,
|
2018-04-18 22:40:29 +08:00
|
|
|
.enable = thc63_enable,
|
|
|
|
.disable = thc63_disable,
|
|
|
|
};
|
|
|
|
|
|
|
|
static int thc63_parse_dt(struct thc63_dev *thc63)
|
|
|
|
{
|
2019-03-05 03:56:07 +08:00
|
|
|
struct device_node *endpoint;
|
2018-04-18 22:40:29 +08:00
|
|
|
struct device_node *remote;
|
|
|
|
|
2019-03-05 03:56:07 +08:00
|
|
|
endpoint = of_graph_get_endpoint_by_regs(thc63->dev->of_node,
|
|
|
|
THC63_RGB_OUT0, -1);
|
|
|
|
if (!endpoint) {
|
2018-04-18 22:40:29 +08:00
|
|
|
dev_err(thc63->dev, "Missing endpoint in port@%u\n",
|
|
|
|
THC63_RGB_OUT0);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
2019-03-05 03:56:07 +08:00
|
|
|
remote = of_graph_get_remote_port_parent(endpoint);
|
|
|
|
of_node_put(endpoint);
|
2018-04-18 22:40:29 +08:00
|
|
|
if (!remote) {
|
|
|
|
dev_err(thc63->dev, "Endpoint in port@%u unconnected\n",
|
|
|
|
THC63_RGB_OUT0);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!of_device_is_available(remote)) {
|
|
|
|
dev_err(thc63->dev, "port@%u remote endpoint is disabled\n",
|
|
|
|
THC63_RGB_OUT0);
|
|
|
|
of_node_put(remote);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
thc63->next = of_drm_find_bridge(remote);
|
|
|
|
of_node_put(remote);
|
|
|
|
if (!thc63->next)
|
|
|
|
return -EPROBE_DEFER;
|
|
|
|
|
2019-03-05 03:56:07 +08:00
|
|
|
endpoint = of_graph_get_endpoint_by_regs(thc63->dev->of_node,
|
|
|
|
THC63_LVDS_IN1, -1);
|
|
|
|
if (endpoint) {
|
|
|
|
remote = of_graph_get_remote_port_parent(endpoint);
|
|
|
|
of_node_put(endpoint);
|
|
|
|
|
|
|
|
if (remote) {
|
|
|
|
if (of_device_is_available(remote))
|
|
|
|
thc63->timings.dual_link = true;
|
|
|
|
of_node_put(remote);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
dev_dbg(thc63->dev, "operating in %s-link mode\n",
|
|
|
|
thc63->timings.dual_link ? "dual" : "single");
|
|
|
|
|
2018-04-18 22:40:29 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int thc63_gpio_init(struct thc63_dev *thc63)
|
|
|
|
{
|
|
|
|
thc63->oe = devm_gpiod_get_optional(thc63->dev, "oe", GPIOD_OUT_LOW);
|
|
|
|
if (IS_ERR(thc63->oe)) {
|
|
|
|
dev_err(thc63->dev, "Unable to get \"oe-gpios\": %ld\n",
|
|
|
|
PTR_ERR(thc63->oe));
|
|
|
|
return PTR_ERR(thc63->oe);
|
|
|
|
}
|
|
|
|
|
|
|
|
thc63->pdwn = devm_gpiod_get_optional(thc63->dev, "powerdown",
|
|
|
|
GPIOD_OUT_HIGH);
|
|
|
|
if (IS_ERR(thc63->pdwn)) {
|
|
|
|
dev_err(thc63->dev, "Unable to get \"powerdown-gpios\": %ld\n",
|
|
|
|
PTR_ERR(thc63->pdwn));
|
|
|
|
return PTR_ERR(thc63->pdwn);
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int thc63_probe(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct thc63_dev *thc63;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
thc63 = devm_kzalloc(&pdev->dev, sizeof(*thc63), GFP_KERNEL);
|
|
|
|
if (!thc63)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
thc63->dev = &pdev->dev;
|
|
|
|
platform_set_drvdata(pdev, thc63);
|
|
|
|
|
2019-11-09 01:32:08 +08:00
|
|
|
thc63->vcc = devm_regulator_get(thc63->dev, "vcc");
|
2018-04-18 22:40:29 +08:00
|
|
|
if (IS_ERR(thc63->vcc)) {
|
|
|
|
if (PTR_ERR(thc63->vcc) == -EPROBE_DEFER)
|
|
|
|
return -EPROBE_DEFER;
|
|
|
|
|
|
|
|
dev_err(thc63->dev, "Unable to get \"vcc\" supply: %ld\n",
|
|
|
|
PTR_ERR(thc63->vcc));
|
|
|
|
return PTR_ERR(thc63->vcc);
|
|
|
|
}
|
|
|
|
|
|
|
|
ret = thc63_gpio_init(thc63);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
ret = thc63_parse_dt(thc63);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
thc63->bridge.driver_private = thc63;
|
|
|
|
thc63->bridge.of_node = pdev->dev.of_node;
|
|
|
|
thc63->bridge.funcs = &thc63_bridge_func;
|
2019-03-05 03:56:07 +08:00
|
|
|
thc63->bridge.timings = &thc63->timings;
|
2018-04-18 22:40:29 +08:00
|
|
|
|
|
|
|
drm_bridge_add(&thc63->bridge);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int thc63_remove(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct thc63_dev *thc63 = platform_get_drvdata(pdev);
|
|
|
|
|
|
|
|
drm_bridge_remove(&thc63->bridge);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct of_device_id thc63_match[] = {
|
|
|
|
{ .compatible = "thine,thc63lvd1024", },
|
|
|
|
{ },
|
|
|
|
};
|
|
|
|
MODULE_DEVICE_TABLE(of, thc63_match);
|
|
|
|
|
|
|
|
static struct platform_driver thc63_driver = {
|
|
|
|
.probe = thc63_probe,
|
|
|
|
.remove = thc63_remove,
|
|
|
|
.driver = {
|
|
|
|
.name = "thc63lvd1024",
|
|
|
|
.of_match_table = thc63_match,
|
|
|
|
},
|
|
|
|
};
|
|
|
|
module_platform_driver(thc63_driver);
|
|
|
|
|
|
|
|
MODULE_AUTHOR("Jacopo Mondi <jacopo@jmondi.org>");
|
|
|
|
MODULE_DESCRIPTION("Thine THC63LVD1024 LVDS decoder DRM bridge driver");
|
|
|
|
MODULE_LICENSE("GPL v2");
|