public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Mrzyglod <daniel.t.mrzyglod@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v7 0/3] Remove global igt_global_mmio
Date: Fri, 16 Aug 2019 16:53:14 +0200	[thread overview]
Message-ID: <20190816145317.4227-1-daniel.t.mrzyglod@intel.com> (raw)

      This patchset remove need for global igt_global_mmio pointer and structures.
In the end igt_global_mmio was kept for legacy reason.
Right now every device could have their own *igt_mmio pointer.
Current behaviour limit number of concurrent PCI device. 
There is a need to run multiple devices.

v2: fixed bugs pointed out in review
v3: divide series to more patches - fix bugs
v4: reword fix bugs
v5: removed patch 03/06 from the previous series due to sugestions
    add fd to gem_mappable_aperture_size()
v6: remove not needed patches. leave igt_global mmio for legacy reason.
v7: cosmetick changes

Daniel Mrzyglod (2):
  lib/intel_mmio: add funtions for read/write register funtions
  lib/intel_mmio: add additional api for multiple devices

Michał Winiarski (1):
  lib/igt_device: add igt_device_get_pci_addr by fd

 benchmarks/gem_latency.c      |   3 +-
 benchmarks/gem_wsim.c         |   3 +-
 lib/igt_device.c              | 124 +++++++++++++++++++
 lib/igt_device.h              |   1 +
 lib/intel_io.h                |  89 +++++++++-----
 lib/intel_iosf.c              |  74 +++++++-----
 lib/intel_mmio.c              | 218 +++++++++++++++++++++++++---------
 tests/i915/gem_exec_latency.c |   4 +-
 tests/i915/gem_exec_parse.c   |  13 +-
 tests/i915/gem_workarounds.c  |   3 +-
 tests/i915/i915_pm_lpsp.c     |   6 +-
 tools/intel_audio_dump.c      |   6 +-
 tools/intel_backlight.c       |   3 +-
 tools/intel_display_poller.c  |   5 +-
 tools/intel_forcewaked.c      |  15 +--
 tools/intel_gpu_time.c        |   3 +-
 tools/intel_infoframes.c      |   5 +-
 tools/intel_l3_parity.c       |  11 +-
 tools/intel_lid.c             |   3 +-
 tools/intel_panel_fitter.c    |   5 +-
 tools/intel_perf_counters.c   |  10 +-
 tools/intel_reg.c             |  23 ++--
 tools/intel_reg_checker.c     |   3 +-
 tools/intel_watermark.c       |  42 ++++---
 24 files changed, 489 insertions(+), 183 deletions(-)

-- 
2.21.0

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2019-08-16 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 14:53 Daniel Mrzyglod [this message]
2019-08-16 14:53 ` [igt-dev] [PATCH i-g-t v7 1/3] lib/igt_device: add igt_device_get_pci_addr by fd Daniel Mrzyglod
2019-08-16 14:53 ` [igt-dev] [PATCH i-g-t v7 2/3] lib/intel_mmio: add funtions for read/write register funtions Daniel Mrzyglod
2019-08-16 19:43   ` Chris Wilson
2019-08-19 13:19     ` Mrzyglod, Daniel T
2019-08-16 14:53 ` [igt-dev] [PATCH i-g-t v7 3/3] lib/intel_mmio: add additional api for multiple devices Daniel Mrzyglod
2019-08-16 19:50   ` Chris Wilson
2019-08-16 15:43 ` [igt-dev] ✓ Fi.CI.BAT: success for Remove global igt_global_mmio (rev7) Patchwork
2019-08-17  7:43 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190816145317.4227-1-daniel.t.mrzyglod@intel.com \
    --to=daniel.t.mrzyglod@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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