From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <abhinavk@codeaurora.org>,
Jonathan Marek <jonathan@marek.ca>,
Stephen Boyd <sboyd@kernel.org>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>
Subject: Re: [PATCH] drm/msm/dp: remove most of usbpd-related remains
Date: Sun, 16 May 2021 15:18:31 +0300 [thread overview]
Message-ID: <CAA8EJpq4tUQRuzXjW58mbzi9KhZHnxzhrTdLGBh3Zw4qmCcmCA@mail.gmail.com> (raw)
In-Reply-To: <20210516054136.GR2484@yoga>
On Sun, 16 May 2021 at 08:41, Bjorn Andersson
<bjorn.andersson@linaro.org> wrote:
>
> On Sat 15 May 14:56 CDT 2021, Dmitry Baryshkov wrote:
>
> > Remove most of remains of downstream usbpd code. Mainline kernel uses
> > different approach for managing Type-C / USB-PD, so this remains unused.
> > Do not touch usbpd callbacks for now, since they look usefull enough as
> > an example of how to handle connect/disconnect (to be rewritten into .
> >
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > ---
> > drivers/gpu/drm/msm/Makefile | 1 -
> > drivers/gpu/drm/msm/dp/dp_ctrl.c | 4 +-
> > drivers/gpu/drm/msm/dp/dp_ctrl.h | 3 +-
> > drivers/gpu/drm/msm/dp/dp_debug.c | 6 +--
> > drivers/gpu/drm/msm/dp/dp_debug.h | 4 +-
> > drivers/gpu/drm/msm/dp/dp_display.c | 36 ++-------------
> > drivers/gpu/drm/msm/dp/dp_hpd.c | 69 -----------------------------
> > drivers/gpu/drm/msm/dp/dp_hpd.h | 51 ---------------------
> > drivers/gpu/drm/msm/dp/dp_power.c | 2 +-
> > drivers/gpu/drm/msm/dp/dp_power.h | 3 +-
> > 10 files changed, 11 insertions(+), 168 deletions(-)
> > delete mode 100644 drivers/gpu/drm/msm/dp/dp_hpd.c
> >
> [..]
> > diff --git a/drivers/gpu/drm/msm/dp/dp_hpd.c b/drivers/gpu/drm/msm/dp/dp_hpd.c
>
> It seems to me that this would be a reasonable place to plug in the
> typec_mux stuff. And as we're starting that exercise we should perhaps
> hold off on applying until we've figured out how that would look?
I'm fine with holding this for a while. Note, that actual code
handling the connection/disconnection is left in place. I've just
dropped unused data structures and related code.
In fact this started as I started looking for the place to put
typec-mux code and whether fields from dp_usbpd struct are used or not
(they are not).
--
With best wishes
Dmitry
prev parent reply other threads:[~2021-05-16 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 19:56 [PATCH] drm/msm/dp: remove most of usbpd-related remains Dmitry Baryshkov
2021-05-16 5:41 ` Bjorn Andersson
2021-05-16 12:18 ` 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=CAA8EJpq4tUQRuzXjW58mbzi9KhZHnxzhrTdLGBh3Zw4qmCcmCA@mail.gmail.com \
--to=dmitry.baryshkov@linaro.org \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sboyd@kernel.org \
--cc=sean@poorly.run \
/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;
as well as URLs for NNTP newsgroup(s).