From: Thierry Reding <thierry.reding@gmail.com>
To: abhinavk@codeaurora.org
Cc: dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
treding@nvidia.com, daniel.vetter@ffwll.ch, varar@quicinc.com,
seanpaul@chromium.org, aravindh@codeaurora.org,
chandanu@codeaurora.org
Subject: Re: Reverting https://patchwork.freedesktop.org/patch/336850/
Date: Mon, 2 Mar 2020 09:09:12 +0100 [thread overview]
Message-ID: <20200302080912.GA1690850@ulmo> (raw)
In-Reply-To: <8bec962794df6fd8f1384d457060234e@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Fri, Feb 28, 2020 at 05:35:51PM -0800, abhinavk@codeaurora.org wrote:
> Hi Thierry
>
> For DP drivers using MSM chipsets, we are using drm_dp_link_configure,
> drm_dp_link_power_up and drm_dp_link_power_down functions. Here is the patch
> for reference:
>
> https://patchwork.freedesktop.org/patch/343346/
>
> We will be posting a newer version of the driver soon.
>
> For that, we plan to revert https://patchwork.freedesktop.org/patch/336850/
> as now there are more users of the functions and not just tegra.
>
> Let us know if this is the right approach or shall we make the required
> functions local to our drivers.
I think reimplementing these locally in you drivers is the preferred
way. It's not so much a lack of users (there were 5 or so in total when
I made the change to remove these helpers), but rather the general
approach that was being criticized by other driver maintainers. I'm not
aware of any of their opinions having changed on this subject, so I'd
recommend going down the path of least resistance.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-02 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 1:35 Reverting https://patchwork.freedesktop.org/patch/336850/ abhinavk
2020-03-02 8:09 ` Thierry Reding [this message]
2020-03-02 20:41 ` abhinavk
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=20200302080912.GA1690850@ulmo \
--to=thierry.reding@gmail.com \
--cc=abhinavk@codeaurora.org \
--cc=aravindh@codeaurora.org \
--cc=chandanu@codeaurora.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=treding@nvidia.com \
--cc=varar@quicinc.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