From: Archit Taneja <architt@codeaurora.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>,
Sean Paul <seanpaul@chromium.org>
Cc: Eric Anholt <eric@anholt.net>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
CK Hu <ck.hu@mediatek.com>,
dri-devel@lists.freedesktop.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Yannick Fertre <yannick.fertre@st.com>,
Philippe Cornu <philippe.cornu@st.com>,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge.
Date: Tue, 6 Jun 2017 15:45:35 +0530 [thread overview]
Message-ID: <20e1423a-b7b5-5f9d-be19-8b5d225f3aed@codeaurora.org> (raw)
In-Reply-To: <20170606105717.1ae5983a@bbrezillon>
On 06/06/2017 02:27 PM, Boris Brezillon wrote:
> Hi Archit,
>
> On Mon, 5 Jun 2017 21:06:20 +0530
> Archit Taneja <architt@codeaurora.org> wrote:
>
>> Hi,
>>
>> When pushing to drm-misc-next, I got a minor merge conflict when dim tried
>> to rebuild drm-tip.
>>
>> The reason for the conflict was because the following commit was present
>> in drm-tip but not in drm-misc:
>>
>> https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c?id=6bee9b78a7a5ea257b24d93974538938c82b1169
>>
>> I fixed the conflict such that drm-tip is rebuit successfully. I'd
>> however like if Eric and Boris could have a look at atmel_hlcdc_output.c
>> to check if things are okay.
>
> Where can I find the fix you made to fix this problem?
+Sean, I missed adding him in the original message.
The fix is a part of the commit that merged drm-misc-next into drm-tip:
https://cgit.freedesktop.org/drm-tip/commit/?id=62a258c9c517c7c97bc4545f77af21ee03e23e1a
The commit "drm/atmel-hlcdc: Fix output initialization" was a part of 4.12-rc2.
drm-misc-next is still based off 4.12-rc1, so this commit wasn't present.
Sean will observe some minor merge conflicts when he rebases drm-misc-next onto
a more recent tag from Linus.
Thanks,
Archit
>
> [...]
>
>>> if (panel) {
>>> - output->connector.dpms = DRM_MODE_DPMS_OFF;
>>> - output->connector.polled = DRM_CONNECTOR_POLL_CONNECT;
>>> - drm_connector_helper_add(&output->connector,
>>> - &atmel_hlcdc_panel_connector_helper_funcs);
>>> - ret = drm_connector_init(dev, &output->connector,
>>> - &atmel_hlcdc_panel_connector_funcs,
>>> - DRM_MODE_CONNECTOR_Unknown);
>>> - if (ret)
>>> - goto err_encoder_cleanup;
>>> -
>>> - drm_mode_connector_attach_encoder(&output->connector,
>>> - &output->encoder);
>>> -
>>> - ret = drm_panel_attach(panel, &output->connector);
>>> - if (ret) {
>>> - drm_connector_cleanup(&output->connector);
>>> - goto err_encoder_cleanup;
>>> - }
>>> -
>>> - output->panel = panel;
>>> + bridge = drm_panel_bridge_add(panel, DRM_MODE_CONNECTOR_Unknown);
>>> + if (IS_ERR(bridge))
>>> + return PTR_ERR(bridge);
>>>
>>> return 0;
>
> Just noticed that this is wrong. We should not return here, otherwise
> the panel bridge is never attached to the encoder.
>
>>> }
>>>
>>> if (bridge) {
>>> - ret = drm_bridge_attach(&output->encoder, bridge, NULL);
>>> + ret = drm_bridge_attach(encoder, bridge, NULL);
>>> if (!ret)
>>> return 0;
>>> +
>>> + if (panel)
>>> + drm_panel_bridge_remove(bridge);
>>> }
>>>
>>> -err_encoder_cleanup:
>>> - drm_encoder_cleanup(&output->encoder);
>>> + drm_encoder_cleanup(encoder);
>>>
>>> return ret;
>>> }
>>>
>>
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-06-06 10:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 18:31 [PATCH v2 1/7] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Eric Anholt
2017-05-11 18:31 ` [PATCH v2 2/7] drm/vc4: Switch DSI to the panel-bridge layer, and support bridges Eric Anholt
2017-05-12 8:02 ` Boris Brezillon
2017-05-11 18:31 ` [PATCH v2 3/7] drm/vc4: Switch DPI to using the panel-bridge helper Eric Anholt
2017-05-12 8:04 ` Boris Brezillon
2017-05-11 18:31 ` [PATCH v2 4/7] drm/mediatek: Use " Eric Anholt
2017-05-12 8:07 ` Boris Brezillon
2017-05-11 18:31 ` [PATCH v2 5/7] drm/ltdc: " Eric Anholt
2017-05-12 8:17 ` Boris Brezillon
2017-05-30 16:55 ` Philippe CORNU
2017-05-31 6:26 ` Boris Brezillon
2017-05-31 8:01 ` Archit Taneja
2017-05-31 8:07 ` Boris Brezillon
2017-05-31 8:35 ` Archit Taneja
2017-06-01 9:53 ` Philippe CORNU
2017-05-11 18:31 ` [PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func Eric Anholt
2017-05-11 19:15 ` Boris Brezillon
2017-05-11 18:31 ` [PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge Eric Anholt
2017-05-11 19:15 ` Boris Brezillon
2017-05-12 7:35 ` Daniel Vetter
2017-06-05 15:36 ` Archit Taneja
2017-06-06 8:57 ` Boris Brezillon
2017-06-06 10:15 ` Archit Taneja [this message]
2017-05-12 7:33 ` [PATCH v2 1/7] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Boris Brezillon
2017-05-12 10:15 ` Archit Taneja
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=20e1423a-b7b5-5f9d-be19-8b5d225f3aed@codeaurora.org \
--to=architt@codeaurora.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=boris.brezillon@free-electrons.com \
--cc=ck.hu@mediatek.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=philippe.cornu@st.com \
--cc=seanpaul@chromium.org \
--cc=yannick.fertre@st.com \
/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
Powered by JetHome