From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Mika Kahola <mika.kahola@intel.com>,
daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, jim.bride@linux.intel.com
Subject: Re: [PATCH v6 09/10] drm/i915: Update bits per component for display info
Date: Tue, 2 Aug 2016 15:18:52 +0200 [thread overview]
Message-ID: <20160802131852.GK6232@phenom.ffwll.local> (raw)
In-Reply-To: <20160802114125.GU4329@intel.com>
On Tue, Aug 02, 2016 at 02:41:25PM +0300, Ville Syrjälä wrote:
> On Tue, Aug 02, 2016 at 02:23:13PM +0300, Mika Kahola wrote:
> > On Tue, 2016-07-12 at 15:51 +0200, Daniel Vetter wrote:
> > > On Wed, Jul 06, 2016 at 02:04:53PM +0300, Mika Kahola wrote:
> > > > DisplayPort branch device may define max supported bits per
> > > > component. Update display info based on this value if bpc
> > > > is defined.
> > > >
> > > > v2: cleanup to match the drm_dp_helper.c patches introduced
> > > > earlier in this series
> > > >
> > > > Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/intel_dp.c | 9 +++++++++
> > > > 1 file changed, 9 insertions(+)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> > > > index 76a654e..53ec844 100644
> > > > --- a/drivers/gpu/drm/i915/intel_dp.c
> > > > +++ b/drivers/gpu/drm/i915/intel_dp.c
> > > > @@ -3932,6 +3932,14 @@ intel_dp_detect_dpcd(struct intel_dp *intel_dp)
> > > > uint8_t *dpcd = intel_dp->dpcd;
> > > > uint8_t type;
> > > >
> > > > + if (dpcd[DP_DOWNSTREAMPORT_PRESENT] & DP_DWN_STRM_PORT_PRESENT) {
> > > > + int bpc = drm_dp_downstream_max_bpc(dpcd,
> > > > + intel_dp->downstream_ports);
> > > > +
> > > > + if (bpc > 0)
> > > > + intel_dp->attached_connector->base.display_info.bpc = bpc;
> > > > + }
> > >
> > > I think a function in the dp helpers to correctly fill out the connector's
> > > display info would be neater.
> > > -Daniel
> > Ok. I can move this stuff to be part of dp helper routine.
>
> I'm not sure frobbing with display_info is a good idea here since that
> that one has so far been the EDID parsers domain. The ordering between
> all this stuff is already very poorly defined/buggy, so some bigger
> cleanup is probably needed. I have some patches to the EDID parser that
> I should send out that at least make it a bit clearer where it fills out
> the display_info stuff.
+1 for bigger cleanup. A helper which does all the dp sink detection
(grabs edid, dpcd and everything else and then computes restrictions)
would be _real_ awesome I think. Even better if you can trick some other
driver into using it too.
Tomeu from collabora just volunteered himself to clean up the analogix dp
support and switch over to the helpers. He's rather active on irc, so
great guinea-pig to volutneer for this and work together with.
-Daniel
>
> > Cheers,
> > Mika
> > >
> > > > +
> > > > if (!intel_dp_get_dpcd(intel_dp))
> > > > return connector_status_disconnected;
> > > >
> > > > @@ -3968,6 +3976,7 @@ intel_dp_detect_dpcd(struct intel_dp *intel_dp)
> > > > return connector_status_unknown;
> > > > }
> > > >
> > > > +
> > > > /* Anything else is out of spec, warn and ignore */
> > > > DRM_DEBUG_KMS("Broken DP branch device, ignoring\n");
> > > > return connector_status_disconnected;
> > > > --
> > > > 1.9.1
> > > >
> > >
> >
> > --
> > Mika Kahola - Intel OTC
>
> --
> Ville Syrjälä
> Intel OTC
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-02 13:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 11:04 [PATCH v6 00/10] drm/i915: DP branch devices Mika Kahola
2016-07-06 11:04 ` [PATCH v6 01/10] drm: Add missing DP downstream port types Mika Kahola
2016-07-25 15:03 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 02/10] drm: Drop VGA from bpc definitions Mika Kahola
2016-07-25 15:03 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 03/10] drm: Helper to read max clock rate Mika Kahola
2016-07-25 15:05 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 04/10] drm: Helper to read max bits per component Mika Kahola
2016-07-25 15:07 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 05/10] drm: Read DP branch device id Mika Kahola
2016-07-25 15:08 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 06/10] drm: Read DP branch device HW revision Mika Kahola
2016-07-12 13:54 ` Daniel Vetter
2016-08-02 11:16 ` Mika Kahola
2016-07-06 11:04 ` [PATCH v6 07/10] drm: Read DP branch device SW revision Mika Kahola
2016-07-25 15:09 ` Jim Bride
2016-07-06 11:04 ` [PATCH v6 08/10] drm/i915: Check pixel rate for DP to VGA dongle Mika Kahola
2016-07-12 13:50 ` Daniel Vetter
2016-08-02 11:18 ` Mika Kahola
2016-07-06 11:04 ` [PATCH v6 09/10] drm/i915: Update bits per component for display info Mika Kahola
2016-07-12 13:51 ` Daniel Vetter
2016-08-02 11:23 ` Mika Kahola
2016-08-02 11:41 ` Ville Syrjälä
2016-08-02 13:18 ` Daniel Vetter [this message]
2016-07-06 11:04 ` [PATCH v6 10/10] drm/i915: Add DP branch device info on debugfs Mika Kahola
2016-07-12 13:52 ` Daniel Vetter
2016-07-06 11:50 ` ✗ Ro.CI.BAT: failure for drm/i915: DP branch devices (rev6) Patchwork
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=20160802131852.GK6232@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jim.bride@linux.intel.com \
--cc=mika.kahola@intel.com \
--cc=ville.syrjala@linux.intel.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