All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jani Nikula <jani.nikula@linux.intel.com>
Cc: "DRM maintainer tools announcements, discussion,
	and development" <dim-tools@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Manasi Navare <manasi.d.navare@intel.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PULL] topic/phy-compliance
Date: Thu, 16 Apr 2020 15:41:55 +0300	[thread overview]
Message-ID: <158704091547.9336.6038156980180850144@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <87imi15gw0.fsf@intel.com>

Quoting Jani Nikula (2020-04-15 10:48:15)
> On Wed, 15 Apr 2020, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > On Wed, Apr 15, 2020 at 8:40 AM Jani Nikula <jani.nikula@linux.intel.com> wrote:
> >>
> >> On Wed, 08 Apr 2020, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> >> > Hey,
> >> >
> >> > Here's a pull request to pull in the DP PHY Compliance series.
> >> > It's based on top of drm/drm-next, and contains all patches for core, amd and i915. :)
> >>
> >> Ping, I don't see this merged in any tree yet.
> >
> > Generally topic pull requests get pulled into all relevant trees,
> > which would be drm-misc, drm-intel and drm-amd here. All of the
> > optional ofc if you do instead maintainer-acks for merging through
> > another tree.
> >
> > Since I wasn't involved in this no idea who requested the topic tree
> > instead of acks, and the pull isn't addressed to specific people who
> > should pull it in (I generally add that to avoid confusion like this
> > here), but this aint something that drm.git needs to pull. Just stuff
> > it into one of the trees as usual. Also just noticed that amd
> > maintainers arent even cc'ed, adding Alex. You guys pls figure this
> > out :-)
> 
> It seemed like drm-misc and drm-intel would be out-of-sync for too long
> before we'd get all of them eventually (back)merged together, so I
> leaned towards the topic branch. Of course, the point starts to be moot
> if it has already taken more than a week to merge this anywhere...
> 
> And I'm pinging about merging the topic pull to drm-misc and drm-intel;
> I'm currently not covering drm-intel.

Pulled to drm-intel-next-queued now.

Regards, Joonas

> 
> BR,
> Jani.
> 
> 
> 
> 
> > -Daniel
> >
> >>
> >> BR,
> >> Jani.
> >>
> >>
> >> >
> >> > Cheers,
> >> > Maarten
> >> >
> >> > topic/phy-compliance-2020-04-08:
> >> > Topic pull request for topic/phy-compliance:
> >> > - Standardize DP_PHY_TEST_PATTERN name.
> >> > - Add support for setting/getting test pattern from sink.
> >> > - Implement DP PHY compliance to i915.
> >> > The following changes since commit 12ab316ced2c5f32ced0e6300a054db644b5444a:
> >> >
> >> >   Merge tag 'amd-drm-next-5.7-2020-04-01' of git://people.freedesktop.org/~agd5f/linux into drm-next (2020-04-08 09:34:27 +1000)
> >> >
> >> > are available in the Git repository at:
> >> >
> >> >   git://anongit.freedesktop.org/drm/drm-misc tags/topic/phy-compliance-2020-04-08
> >> >
> >> > for you to fetch changes up to 8cdf727119289db3a98835662eb28e1c5ad835f1:
> >> >
> >> >   drm/i915/dp: Program vswing, pre-emphasis, test-pattern (2020-04-08 14:41:09 +0200)
> >> >
> >> > ----------------------------------------------------------------
> >> > Topic pull request for topic/phy-compliance:
> >> > - Standardize DP_PHY_TEST_PATTERN name.
> >> > - Add support for setting/getting test pattern from sink.
> >> > - Implement DP PHY compliance to i915.
> >> >
> >> > ----------------------------------------------------------------
> >> > Animesh Manna (7):
> >> >       drm/amd/display: Align macro name as per DP spec
> >> >       drm/dp: get/set phy compliance pattern
> >> >       drm/i915/dp: Made intel_dp_adjust_train() non-static
> >> >       drm/i915/dp: Preparation for DP phy compliance auto test
> >> >       drm/i915/dp: Add debugfs entry for DP phy compliance
> >> >       drm/i915/dp: Register definition for DP compliance register
> >> >       drm/i915/dp: Program vswing, pre-emphasis, test-pattern
> >> >
> >> >  drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c   |   2 +-
> >> >  drivers/gpu/drm/drm_dp_helper.c                    |  94 +++++++++++
> >> >  .../gpu/drm/i915/display/intel_display_debugfs.c   |  12 +-
> >> >  drivers/gpu/drm/i915/display/intel_display_types.h |   1 +
> >> >  drivers/gpu/drm/i915/display/intel_dp.c            | 171 +++++++++++++++++++++
> >> >  drivers/gpu/drm/i915/display/intel_dp.h            |   1 +
> >> >  .../gpu/drm/i915/display/intel_dp_link_training.c  |   9 +-
> >> >  .../gpu/drm/i915/display/intel_dp_link_training.h  |   4 +
> >> >  drivers/gpu/drm/i915/i915_reg.h                    |  18 +++
> >> >  include/drm/drm_dp_helper.h                        |  33 +++-
> >> >  10 files changed, 337 insertions(+), 8 deletions(-)
> >>
> >> --
> >> Jani Nikula, Intel Open Source Graphics Center
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jani Nikula <jani.nikula@linux.intel.com>
Cc: "DRM maintainer tools announcements, discussion,
	and development" <dim-tools@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Maxime Ripard <mripard@kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [Intel-gfx] [PULL] topic/phy-compliance
Date: Thu, 16 Apr 2020 15:41:55 +0300	[thread overview]
Message-ID: <158704091547.9336.6038156980180850144@jlahtine-desk.ger.corp.intel.com> (raw)
In-Reply-To: <87imi15gw0.fsf@intel.com>

Quoting Jani Nikula (2020-04-15 10:48:15)
> On Wed, 15 Apr 2020, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> > On Wed, Apr 15, 2020 at 8:40 AM Jani Nikula <jani.nikula@linux.intel.com> wrote:
> >>
> >> On Wed, 08 Apr 2020, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> >> > Hey,
> >> >
> >> > Here's a pull request to pull in the DP PHY Compliance series.
> >> > It's based on top of drm/drm-next, and contains all patches for core, amd and i915. :)
> >>
> >> Ping, I don't see this merged in any tree yet.
> >
> > Generally topic pull requests get pulled into all relevant trees,
> > which would be drm-misc, drm-intel and drm-amd here. All of the
> > optional ofc if you do instead maintainer-acks for merging through
> > another tree.
> >
> > Since I wasn't involved in this no idea who requested the topic tree
> > instead of acks, and the pull isn't addressed to specific people who
> > should pull it in (I generally add that to avoid confusion like this
> > here), but this aint something that drm.git needs to pull. Just stuff
> > it into one of the trees as usual. Also just noticed that amd
> > maintainers arent even cc'ed, adding Alex. You guys pls figure this
> > out :-)
> 
> It seemed like drm-misc and drm-intel would be out-of-sync for too long
> before we'd get all of them eventually (back)merged together, so I
> leaned towards the topic branch. Of course, the point starts to be moot
> if it has already taken more than a week to merge this anywhere...
> 
> And I'm pinging about merging the topic pull to drm-misc and drm-intel;
> I'm currently not covering drm-intel.

Pulled to drm-intel-next-queued now.

Regards, Joonas

> 
> BR,
> Jani.
> 
> 
> 
> 
> > -Daniel
> >
> >>
> >> BR,
> >> Jani.
> >>
> >>
> >> >
> >> > Cheers,
> >> > Maarten
> >> >
> >> > topic/phy-compliance-2020-04-08:
> >> > Topic pull request for topic/phy-compliance:
> >> > - Standardize DP_PHY_TEST_PATTERN name.
> >> > - Add support for setting/getting test pattern from sink.
> >> > - Implement DP PHY compliance to i915.
> >> > The following changes since commit 12ab316ced2c5f32ced0e6300a054db644b5444a:
> >> >
> >> >   Merge tag 'amd-drm-next-5.7-2020-04-01' of git://people.freedesktop.org/~agd5f/linux into drm-next (2020-04-08 09:34:27 +1000)
> >> >
> >> > are available in the Git repository at:
> >> >
> >> >   git://anongit.freedesktop.org/drm/drm-misc tags/topic/phy-compliance-2020-04-08
> >> >
> >> > for you to fetch changes up to 8cdf727119289db3a98835662eb28e1c5ad835f1:
> >> >
> >> >   drm/i915/dp: Program vswing, pre-emphasis, test-pattern (2020-04-08 14:41:09 +0200)
> >> >
> >> > ----------------------------------------------------------------
> >> > Topic pull request for topic/phy-compliance:
> >> > - Standardize DP_PHY_TEST_PATTERN name.
> >> > - Add support for setting/getting test pattern from sink.
> >> > - Implement DP PHY compliance to i915.
> >> >
> >> > ----------------------------------------------------------------
> >> > Animesh Manna (7):
> >> >       drm/amd/display: Align macro name as per DP spec
> >> >       drm/dp: get/set phy compliance pattern
> >> >       drm/i915/dp: Made intel_dp_adjust_train() non-static
> >> >       drm/i915/dp: Preparation for DP phy compliance auto test
> >> >       drm/i915/dp: Add debugfs entry for DP phy compliance
> >> >       drm/i915/dp: Register definition for DP compliance register
> >> >       drm/i915/dp: Program vswing, pre-emphasis, test-pattern
> >> >
> >> >  drivers/gpu/drm/amd/display/dc/core/dc_link_dp.c   |   2 +-
> >> >  drivers/gpu/drm/drm_dp_helper.c                    |  94 +++++++++++
> >> >  .../gpu/drm/i915/display/intel_display_debugfs.c   |  12 +-
> >> >  drivers/gpu/drm/i915/display/intel_display_types.h |   1 +
> >> >  drivers/gpu/drm/i915/display/intel_dp.c            | 171 +++++++++++++++++++++
> >> >  drivers/gpu/drm/i915/display/intel_dp.h            |   1 +
> >> >  .../gpu/drm/i915/display/intel_dp_link_training.c  |   9 +-
> >> >  .../gpu/drm/i915/display/intel_dp_link_training.h  |   4 +
> >> >  drivers/gpu/drm/i915/i915_reg.h                    |  18 +++
> >> >  include/drm/drm_dp_helper.h                        |  33 +++-
> >> >  10 files changed, 337 insertions(+), 8 deletions(-)
> >>
> >> --
> >> Jani Nikula, Intel Open Source Graphics Center
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-04-16 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 12:49 [PULL] topic/phy-compliance Maarten Lankhorst
2020-04-08 12:49 ` [Intel-gfx] " Maarten Lankhorst
2020-04-15  6:40 ` Jani Nikula
2020-04-15  6:40   ` [Intel-gfx] " Jani Nikula
2020-04-15  7:00   ` Daniel Vetter
2020-04-15  7:00     ` [Intel-gfx] " Daniel Vetter
2020-04-15  7:48     ` Jani Nikula
2020-04-15  7:48       ` [Intel-gfx] " Jani Nikula
2020-04-16 12:41       ` Joonas Lahtinen [this message]
2020-04-16 12:41         ` Joonas Lahtinen
2020-04-17  8:23 ` Thomas Zimmermann
2020-04-17  8:23   ` [Intel-gfx] " Thomas Zimmermann

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=158704091547.9336.6038156980180850144@jlahtine-desk.ger.corp.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=alexdeucher@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=manasi.d.navare@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tzimmermann@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.