From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: James Qian Wang <james.qian.wang@arm.com>,
MaliDP Maintainers <malidp@foss.arm.com>,
DRI devel <dri-devel@lists.freedesktop.org>
Subject: [PULL v2] malidp-next
Date: Mon, 1 Apr 2019 20:28:34 +0100 [thread overview]
Message-ID: <20190401192833.GW21747@e110455-lin.cambridge.arm.com> (raw)
Hi DRM maintainers,
This is a respin of the last week's pull request as I have discovered
via the kbuild test bot that one of the commits was not bisectable.
This pull requests adds initial Mali D71 support into the Arm "komeda" DRM
driver. The code has been reviewed at the end of last year, I just been
too slow with pushing it into mainline. Since it started baking in
linux-next we had a kbuild-bot issue raised and one from Joe Perches on
the MAINTAINERS entry, for which I'm including fixes here.
Please pull,
Liviu
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://linux-arm.org/linux-ld.git for-upstream/mali-dp
for you to fetch changes up to 04c8a1ec395b22f060b836b72d2d4480e7e859f8:
MAINTAINERS: Fix pattern for Documentation path for Arm Mali Komeda (2019-04-01 20:22:08 +0100)
----------------------------------------------------------------
Liviu Dudau (2):
arm/komeda: Compile komeda_debugfs_init() only if CONFIG_DEBUG_FS is enabled
MAINTAINERS: Fix pattern for Documentation path for Arm Mali Komeda
james qian wang (Arm Technology China) (7):
drm/komeda: Add d71_enum_resources and d71_cleanup
drm/komeda: Add d71 layer
drm/komeda: Add d71 compiz component
drm/komeda: Add D71 improc and timing_ctrlr
drm/komeda: Add komeda_assemble_pipelines
drm/komeda: Add irq handling
drm/komeda: Add debugfs node "register" for register dump
MAINTAINERS | 2 +-
drivers/gpu/drm/arm/display/include/malidp_utils.h | 31 +
drivers/gpu/drm/arm/display/komeda/Makefile | 3 +-
.../gpu/drm/arm/display/komeda/d71/d71_component.c | 684 +++++++++++++++++++++
drivers/gpu/drm/arm/display/komeda/d71/d71_dev.c | 377 +++++++++++-
drivers/gpu/drm/arm/display/komeda/d71/d71_dev.h | 50 ++
drivers/gpu/drm/arm/display/komeda/d71/d71_regs.h | 530 ++++++++++++++++
drivers/gpu/drm/arm/display/komeda/komeda_crtc.c | 18 +
drivers/gpu/drm/arm/display/komeda/komeda_dev.c | 66 ++
drivers/gpu/drm/arm/display/komeda/komeda_dev.h | 51 ++
drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 38 +-
drivers/gpu/drm/arm/display/komeda/komeda_kms.h | 5 +
.../gpu/drm/arm/display/komeda/komeda_pipeline.c | 111 +++-
.../gpu/drm/arm/display/komeda/komeda_pipeline.h | 48 +-
14 files changed, 1983 insertions(+), 31 deletions(-)
create mode 100644 drivers/gpu/drm/arm/display/komeda/d71/d71_component.c
create mode 100644 drivers/gpu/drm/arm/display/komeda/d71/d71_dev.h
create mode 100644 drivers/gpu/drm/arm/display/komeda/d71/d71_regs.h
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2019-04-01 19:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190401192833.GW21747@e110455-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=malidp@foss.arm.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 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.