From: Andrzej Hajda <a.hajda@samsung.com>
To: Sam Ravnborg <sam@ravnborg.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Jernej Skrabec <jernej.skrabec@siol.net>,
linux-samsung-soc@vger.kernel.org,
Jonas Karlman <jonas@kwiboo.se>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH RESEND] drm/bridge: tc358764: restore connector support
Date: Mon, 5 Oct 2020 16:27:18 +0200 [thread overview]
Message-ID: <fd29eebc-d9dc-374a-db98-b08613f505f8@samsung.com> (raw)
In-Reply-To: <20201004191441.GA551257@ravnborg.org>
W dniu 04.10.2020 o 21:14, Sam Ravnborg pisze:
> Hi Marek.
>
> On Wed, Sep 30, 2020 at 01:40:42PM +0200, Marek Szyprowski wrote:
>> This patch restores DRM connector registration in the TC358764 bridge
>> driver and restores usage of the old drm_panel_* API, thus allows dynamic
>> panel registration. This fixes panel operation on Exynos5250-based
>> Arndale board.
>>
>> This is equivalent to the revert of the following commits:
>> 1644127f83bc "drm/bridge: tc358764: add drm_panel_bridge support"
>> 385ca38da29c "drm/bridge: tc358764: drop drm_connector_(un)register"
>> and removal of the calls to drm_panel_attach()/drm_panel_detach(), which
>> were no-ops and has been removed in meanwhile.
>>
>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
> Thanks for providing the revert so we can have this fixed in upstream.
> So far I have had no time to dive deeper into what is going wrong but
> and the revert is the right cause of action for now.
>
> I expect Andrzej to pick it up as he has already reviewed it.
>
> Sam
Done
Regards
Andrzej
prev parent reply other threads:[~2020-10-05 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200930114050eucas1p2fd39f213b4cf82068b79c97992a9acc7@eucas1p2.samsung.com>
2020-09-30 11:40 ` Marek Szyprowski
2020-10-04 19:14 ` Sam Ravnborg
2020-10-05 14:27 ` Andrzej Hajda [this message]
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=fd29eebc-d9dc-374a-db98-b08613f505f8@samsung.com \
--to=a.hajda@samsung.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=narmstrong@baylibre.com \
--cc=sam@ravnborg.org \
/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®