From: sonika <sonika.jindal@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Thierry Reding <treding@nvidia.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC] drm: Add utility function to check for edp1.4
Date: Tue, 04 Nov 2014 11:25:41 +0530 [thread overview]
Message-ID: <54586A5D.4030200@intel.com> (raw)
In-Reply-To: <CAKMK7uGZAqxj_oNv66tJ9DdW_dbJAQnH-eQkBtMLEvA2QL=BzA@mail.gmail.com>
On Monday 03 November 2014 01:58 PM, Daniel Vetter wrote:
> On Mon, Nov 3, 2014 at 9:25 AM, Thierry Reding <treding@nvidia.com> wrote:
>>> The idea is that you'd grab the DPCD field anyway since it's needed all
>>> over the place. We have a pile of helpers already that take exactly this
>>> block and decode parts of it. So I think this makes sense - dp aux is fast
>>> but not entirely free, so caching seems useful.
>> If we want to always cache part of the DPCD wouldn't it be better to add
>> the cache to struct drm_dp_aux instead of having to duplicate this in
>> every driver?
> Right now we don't (yet) have helper functions to probe SST DP sinks,
> so there's not really a good place to put it. But yeah longer-term I
> hope that some shared SST sink probe functions shows up (especially to
> handle all the various crazy corner-cases with VGA probing, e.g. the
> apple vga dongle patch Dave sent out many aeons ago), and then putting
> that cache into the dp aux struct makes sense. But before that happens
> I don't think it makes a lot of sense really, since then we'd also
> need to add code to invalidate that cache. Simpler if drivers just
> take care of that themselves.
> -Daniel
For the edp revision, I am feeling that having a function which simply
reads DP_EDP_REV,
and returns it doesn't add much value.
So, I am thinking to put that part in driver itself. Please let me know
if you feel otherwise.
-Sonika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-11-04 5:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 6:15 [RFC] drm: Add utility function to check for edp1.4 sonika.jindal
2014-10-29 13:42 ` Thierry Reding
2014-10-30 4:14 ` sonika
2014-10-31 16:06 ` Daniel Vetter
2014-11-03 8:25 ` Thierry Reding
2014-11-03 8:28 ` Daniel Vetter
2014-11-04 5:55 ` sonika [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=54586A5D.4030200@intel.com \
--to=sonika.jindal@intel.com \
--cc=alexdeucher@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=treding@nvidia.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