dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Pet Weng" <pet.weng@ite.com.tw>,
	"Andrzej Hajda" <andrzej.hajda@intel.com>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Robert Foss" <rfoss@kernel.org>,
	"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"Hermes Wu" <hermes.Wu@ite.com.tw>,
	"Kenneth Hung" <kenneth.Hung@ite.com.tw>,
	"Pin-yen Lin" <treapking@google.com>
Subject: Re: [PATCH v5 2/3] drm/bridge: Add ITE IT61620 MIPI DSI to HDMI bridge driver
Date: Wed, 31 Dec 2025 11:37:38 +0100	[thread overview]
Message-ID: <DFCC4L42EGF0.3DRXWVXVWSF40@bootlin.com> (raw)
In-Reply-To: <20251222-it61620-0714-v5-2-afb6479ad3ca@ite.com.tw>

Hello Pet,

On Mon Dec 22, 2025 at 4:10 AM CET, Pet Weng wrote:
> This adds support for the ITE IT61620 bridge chip which converts
> MIPI DSI input to HDMI output. The Driver implements the basic
> bridge functions and integrates with the DRM bridge and connector
> frameworks.
>
> Supported fetures include:
            ^ features

> MIPI DSI input handling
> HDMI output setup
> Basic mode configuration
> I2C-based control and initialization
> HDCP 1.4 handling
>
> HPD handling clarification:
> Although IT61620 has an HPD pin, hotplug detection is handled by the
> system connector. The bridge only receives HPD notifications, and the
> HPD pin is used solely for short pulses during HDCP authentication.
> Therefore, this bridge does not implement OP_HPD or OP_DETECT, as it
> does not originate or determine hotplug or connection status.
>
> This driver will be used on platforms embedding the IT61620 for
> video output via HDMI from SoCs with MIPI DSI output.
>
> Signed-off-by: Pet Weng <pet.weng@ite.com.tw>

[...]

> +static int it61620_probe(struct i2c_client *client)
> +{
> +	struct device *dev = &client->dev;
> +	struct device_node *np = dev->of_node;
> +	struct mipi_dsi_host *host;
> +	struct it61620 *it61620;
> +	int ret = 0;
> +
> +	it61620 = devm_drm_bridge_alloc(dev, struct it61620, bridge,
> +					&it61620_bridge_funcs);
> +	if (IS_ERR(it61620))
> +		return PTR_ERR(it61620);
> +
> +	it61620->dev = dev;
> +	it61620->chip_info = of_device_get_match_data(dev);
> +
> +	host = drm_of_get_dsi_bus(dev);
> +	if (IS_ERR(host))
> +		return dev_err_probe(dev, PTR_ERR(host),
> +				     "failed to find dsi host\n");
> +
> +	ret = it61620_i2c_and_regmap_init(client, it61620);
> +	if (ret < 0)
> +		return ret;
> +
> +	i2c_set_clientdata(client, it61620);
> +
> +	ret = it61620_init_power(it61620);
> +	if (ret < 0)
> +		return ret;
> +
> +	it61620_config_default(it61620);
> +
> +	ret = it61620_parse_dt(it61620);
> +	if (ret < 0)
> +		return ret;
> +
> +	if (!client->irq)
> +		return dev_err_probe(dev, -ENODEV,
> +				     "Failed to get INTP IRQ\n");
> +
> +	ret = devm_request_threaded_irq(&client->dev, client->irq, NULL,
> +					it61620_int_threaded_handler,
> +					IRQF_TRIGGER_LOW | IRQF_ONESHOT |
> +					IRQF_NO_AUTOEN,
> +					"it61620-intp", it61620);
> +	if (ret < 0)
> +		return dev_err_probe(dev, ret,
> +				     "failed to request INTP threaded IRQ\n");
> +
> +	INIT_DELAYED_WORK(&it61620->hdcp_work, it61620_hdcp_work);
> +	init_waitqueue_head(&it61620->wq);
> +
> +	mutex_init(&it61620->ddc_lock);
> +
> +	pm_runtime_enable(dev);
> +	pm_runtime_set_autosuspend_delay(dev, 1000);
> +	pm_runtime_use_autosuspend(dev);
> +
> +	it61620->bridge.funcs = &it61620_bridge_funcs;

You don't have to set the funcs. They are already set by
devm_drm_bridge_alloc() above.

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2025-12-31 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  3:10 [PATCH v5 0/3] Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2025-12-22  3:10 ` [PATCH v5 1/3] dt-binding: display: Add ITE IT61620 MIPI DSI to HDMI bridge Pet Weng
2025-12-22  8:50   ` Krzysztof Kozlowski
2025-12-22  3:10 ` [PATCH v5 2/3] drm/bridge: Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2025-12-31 10:37   ` Luca Ceresoli [this message]
2025-12-22  3:10 ` [PATCH v5 3/3] MAINTAINERS: Add entry for ITE IT61620 MIPI " Pet Weng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DFCC4L42EGF0.3DRXWVXVWSF40@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hermes.Wu@ite.com.tw \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kenneth.Hung@ite.com.tw \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=pet.weng@ite.com.tw \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=treapking@google.com \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox