From: Michael Riesch <michael.riesch@wolfvision.net>
To: Sascha Hauer <sha@pengutronix.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
Sandy Huang <hjc@rock-chips.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v2 5/6] drm/rockchip: vop2: add support for the rgb output block
Date: Thu, 19 Jan 2023 17:14:07 +0100 [thread overview]
Message-ID: <6e7844f0-2a41-6542-9a0c-4837233f1251@wolfvision.net> (raw)
In-Reply-To: <20230119151734.GH24755@pengutronix.de>
Hi Sascha,
On 1/19/23 16:17, Sascha Hauer wrote:
> Hi Michael,
>
> On Thu, Jan 19, 2023 at 03:39:10PM +0100, Michael Riesch wrote:
>> The Rockchip VOP2 features an internal RGB output block, which can be
>> attached to the video port 2 of the VOP2. Add support for this output
>> block.
>>
>> Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
>> ---
>> v2:
>> - move away from wrong assumption that the RGB block is always
>> connected to video port 2 -> check devicetree to find RGB block
>
> Traces of that assumption are still in the commmit message.
Oops, this needs fixing of course...
>> drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 44 ++++++++++++++++++++
>> 1 file changed, 44 insertions(+)
>>
>> +static int vop2_find_rgb_encoder(struct vop2 *vop2)
>> +{
>> + struct device_node *node = vop2->dev->of_node;
>> + struct device_node *endpoint;
>> + int i;
>> +
>> + for (i = 0; i < vop2->data->nr_vps; i++) {
>> + endpoint = of_graph_get_endpoint_by_regs(node, i,
>> + ROCKCHIP_VOP2_EP_RGB0);
>> + if (!endpoint)
>> + continue;
>> +
>> + of_node_put(endpoint);
>> + return i;
>> + }
>> +
>> + return -ENOENT;
>> +}
>> +
>> static struct reg_field vop2_cluster_regs[VOP2_WIN_MAX_REG] = {
>> [VOP2_WIN_ENABLE] = REG_FIELD(RK3568_CLUSTER_WIN_CTRL0, 0, 0),
>> [VOP2_WIN_FORMAT] = REG_FIELD(RK3568_CLUSTER_WIN_CTRL0, 1, 5),
>> @@ -2698,11 +2721,29 @@ static int vop2_bind(struct device *dev, struct device *master, void *data)
>> if (ret)
>> return ret;
>>
>> + ret = vop2_find_rgb_encoder(vop2);
>> + if (ret > 0) {
>
> '0' seems to be a valid vp as well. Shouldn't this be ret >= 0?
...and you are right of course. What a stupid mistake.
Will fix these in v3.
Best regards,
Michael
>
>> + vop2->rgb = rockchip_rgb_init(dev, &vop2->vps[ret].crtc,
>> + vop2->drm, ret);
>> + if (IS_ERR(vop2->rgb)) {
>> + if (PTR_ERR(vop2->rgb) == -EPROBE_DEFER) {
>> + ret = PTR_ERR(vop2->rgb);
>> + goto err_crtcs;
>> + }
>> + vop2->rgb = NULL;
>> + }
>> + }
>> +
>
> Sascha
>
next prev parent reply other threads:[~2023-01-19 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 14:39 [PATCH v2 0/6] " Michael Riesch
2023-01-19 14:39 ` [PATCH v2 1/6] drm/rockchip: vop2: initialize possible_crtcs properly Michael Riesch
2023-01-19 14:39 ` [PATCH v2 2/6] drm/rockchip: rgb: embed drm_encoder into rockchip_encoder Michael Riesch
2023-01-19 14:39 ` [PATCH v2 3/6] drm/rockchip: rgb: add video_port parameter to init function Michael Riesch
2023-01-19 14:39 ` [PATCH v2 4/6] drm/rockchip: vop2: use symmetric function pair vop2_{create,destroy}_crtcs Michael Riesch
2023-01-19 14:39 ` [PATCH v2 5/6] drm/rockchip: vop2: add support for the rgb output block Michael Riesch
2023-01-19 15:17 ` Sascha Hauer
2023-01-19 16:14 ` Michael Riesch [this message]
2023-01-19 14:39 ` [PATCH v2 6/6] arm64: dts: rockchip: add pinctrls for 16-bit/18-bit rgb interface to rk356x Michael Riesch
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=6e7844f0-2a41-6542-9a0c-4837233f1251@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=sha@pengutronix.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
all inboxes | Powered by JetHome®