From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
Sean Paul <sean@poorly.run>,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
Hsin-Yi Wang <hsinyi@chromium.org>,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH] drm/msm/dsi: Set panel orientation when directly connected
Date: Thu, 1 Sep 2022 11:42:22 +0300 [thread overview]
Message-ID: <23615048-dae5-d972-9b10-ff1356c0a02f@linaro.org> (raw)
In-Reply-To: <20220706191442.1150634-1-swboyd@chromium.org>
On 06/07/2022 22:14, Stephen Boyd wrote:
> Set the panel orientation in drm when the panel is directly connected,
> i.e. we're not using an external bridge. The external bridge case is
> already handled by the panel bridge code, so we only update the path we
> take when the panel is directly connected/internal. This silences a
> warning splat coming from __drm_mode_object_add() on Wormdingler boards.
>
> Cc: Hsin-Yi Wang <hsinyi@chromium.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
>
> This relies on commit 5e41b01a7808 ("drm/panel: Add an API to allow drm
> to set orientation from panel") which is in drm-misc
With the msm/dsi being switched to DRM_PANEL_BRIDGE this is no longer
relevant. Dropping this from the queue.
--
With best wishes
Dmitry
prev parent reply other threads:[~2022-09-01 8:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 19:14 Stephen Boyd
2022-07-07 21:11 ` Abhinav Kumar
2022-07-07 21:21 ` Stephen Boyd
2022-07-07 21:25 ` [Freedreno] " Abhinav Kumar
2022-07-08 15:25 ` Doug Anderson
2022-07-08 16:00 ` Abhinav Kumar
2022-07-08 19:42 ` Abhinav Kumar
2022-07-08 20:58 ` Dmitry Baryshkov
2022-07-08 21:17 ` Abhinav Kumar
2022-07-20 20:46 ` Rob Clark
2022-07-20 22:42 ` Doug Anderson
2022-08-17 20:48 ` Doug Anderson
2022-08-18 23:11 ` [Freedreno] " Abhinav Kumar
2022-09-01 8:42 ` Dmitry Baryshkov [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=23615048-dae5-d972-9b10-ff1356c0a02f@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hsinyi@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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®