From: Liviu Dudau <Liviu.Dudau@arm.com> To: Emil Velikov <emil.l.velikov@gmail.com> Cc: Dave Airlie <airlied@gmail.com>, Daniel Stone <daniel@fooishbar.org>, David Brown <David.Brown@arm.com>, Brian Starkey <Brian.Starkey@arm.com>, devicetree <devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, DRI devel <dri-devel@lists.freedesktop.org> Subject: Re: [RFC][PATCH 2/2] drm/arm: Add support for Mali Display Processors Date: Wed, 13 Apr 2016 14:48:57 +0100 [thread overview] Message-ID: <20160413134857.GN16063@e106497-lin.cambridge.arm.com> (raw) In-Reply-To: <CACvgo51+1MDaDq5=TpFQeSBuKgRM33Pa71apEVHSo90jgKmViw@mail.gmail.com> On Wed, Apr 13, 2016 at 12:48:05PM +0100, Emil Velikov wrote: > Hi Liviu, Hi Emil, > > On 1 April 2016 at 17:21, Liviu Dudau <Liviu.Dudau@arm.com> wrote: > > Add support for the new family of Display Processors from ARM Ltd. > > This commit adds basic support for Mali DP500, DP550 and DP650 > > parts, with only the display engine being supported at the moment. > > > > Cc: David Brown <David.Brown@arm.com> > > Cc: Brian Starkey <Brian.Starkey@arm.com> > > > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> > > --- > > drivers/gpu/drm/arm/Kconfig | 15 + > > drivers/gpu/drm/arm/Makefile | 2 + > > drivers/gpu/drm/arm/malidp_crtc.c | 276 +++++++++++++ > > drivers/gpu/drm/arm/malidp_drv.c | 486 ++++++++++++++++++++++ > > drivers/gpu/drm/arm/malidp_drv.h | 49 +++ > > drivers/gpu/drm/arm/malidp_hw.c | 777 ++++++++++++++++++++++++++++++++++++ > > drivers/gpu/drm/arm/malidp_hw.h | 192 +++++++++ > > drivers/gpu/drm/arm/malidp_planes.c | 342 ++++++++++++++++ > > drivers/gpu/drm/arm/malidp_regs.h | 172 ++++++++ > > 9 files changed, 2311 insertions(+) > > create mode 100644 drivers/gpu/drm/arm/malidp_crtc.c > > create mode 100644 drivers/gpu/drm/arm/malidp_drv.c > > create mode 100644 drivers/gpu/drm/arm/malidp_drv.h > > create mode 100644 drivers/gpu/drm/arm/malidp_hw.c > > create mode 100644 drivers/gpu/drm/arm/malidp_hw.h > > create mode 100644 drivers/gpu/drm/arm/malidp_planes.c > > create mode 100644 drivers/gpu/drm/arm/malidp_regs.h > > > Since the current MAINTAINERS include the whole drm/arm folder, one > could just generalise the heading alike > > s/ARM HDLCD DRM DRIVER/ARM DRM DRIVERS/ For the Mali DP drivers we are planning to have a shared maintainership as it is covering quite a few HW versions and is a more complex driver. HDLCD is a very simple driver (and hardware part) so I'm going to keep that maintainership on my name, but the rest of Mali DP will have a wider support team. It is the reason why the patchset does not have a MAINTAINERS update. Best regards, Liviu > > ... and fold the bindings in a similar fashion (or just update to > include the new one) > > git mv Documentation/devicetree/bindings/display/arm{\,,/}foo.txt > > -Emil > -- ==================== | I would like to | | fix the world, | | but they're not | | giving me the | \ source code! / --------------- ¯\_(ツ)_/¯
WARNING: multiple messages have this Message-ID (diff)
From: Liviu Dudau <Liviu.Dudau@arm.com> To: Emil Velikov <emil.l.velikov@gmail.com> Cc: devicetree <devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, DRI devel <dri-devel@lists.freedesktop.org> Subject: Re: [RFC][PATCH 2/2] drm/arm: Add support for Mali Display Processors Date: Wed, 13 Apr 2016 14:48:57 +0100 [thread overview] Message-ID: <20160413134857.GN16063@e106497-lin.cambridge.arm.com> (raw) In-Reply-To: <CACvgo51+1MDaDq5=TpFQeSBuKgRM33Pa71apEVHSo90jgKmViw@mail.gmail.com> On Wed, Apr 13, 2016 at 12:48:05PM +0100, Emil Velikov wrote: > Hi Liviu, Hi Emil, > > On 1 April 2016 at 17:21, Liviu Dudau <Liviu.Dudau@arm.com> wrote: > > Add support for the new family of Display Processors from ARM Ltd. > > This commit adds basic support for Mali DP500, DP550 and DP650 > > parts, with only the display engine being supported at the moment. > > > > Cc: David Brown <David.Brown@arm.com> > > Cc: Brian Starkey <Brian.Starkey@arm.com> > > > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> > > --- > > drivers/gpu/drm/arm/Kconfig | 15 + > > drivers/gpu/drm/arm/Makefile | 2 + > > drivers/gpu/drm/arm/malidp_crtc.c | 276 +++++++++++++ > > drivers/gpu/drm/arm/malidp_drv.c | 486 ++++++++++++++++++++++ > > drivers/gpu/drm/arm/malidp_drv.h | 49 +++ > > drivers/gpu/drm/arm/malidp_hw.c | 777 ++++++++++++++++++++++++++++++++++++ > > drivers/gpu/drm/arm/malidp_hw.h | 192 +++++++++ > > drivers/gpu/drm/arm/malidp_planes.c | 342 ++++++++++++++++ > > drivers/gpu/drm/arm/malidp_regs.h | 172 ++++++++ > > 9 files changed, 2311 insertions(+) > > create mode 100644 drivers/gpu/drm/arm/malidp_crtc.c > > create mode 100644 drivers/gpu/drm/arm/malidp_drv.c > > create mode 100644 drivers/gpu/drm/arm/malidp_drv.h > > create mode 100644 drivers/gpu/drm/arm/malidp_hw.c > > create mode 100644 drivers/gpu/drm/arm/malidp_hw.h > > create mode 100644 drivers/gpu/drm/arm/malidp_planes.c > > create mode 100644 drivers/gpu/drm/arm/malidp_regs.h > > > Since the current MAINTAINERS include the whole drm/arm folder, one > could just generalise the heading alike > > s/ARM HDLCD DRM DRIVER/ARM DRM DRIVERS/ For the Mali DP drivers we are planning to have a shared maintainership as it is covering quite a few HW versions and is a more complex driver. HDLCD is a very simple driver (and hardware part) so I'm going to keep that maintainership on my name, but the rest of Mali DP will have a wider support team. It is the reason why the patchset does not have a MAINTAINERS update. Best regards, Liviu > > ... and fold the bindings in a similar fashion (or just update to > include the new one) > > git mv Documentation/devicetree/bindings/display/arm{\,,/}foo.txt > > -Emil > -- ==================== | 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
next prev parent reply other threads:[~2016-04-13 13:49 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-01 16:21 [RFC][PATCH 0/2] Initial support for ARM Mali Display Processors Liviu Dudau 2016-04-01 16:21 ` Liviu Dudau 2016-04-01 16:21 ` [RFC][PATCH 1/2] dt/bindings: display: Add DT bindings for " Liviu Dudau 2016-04-01 16:21 ` Liviu Dudau 2016-04-01 16:47 ` Mark Rutland 2016-04-01 16:47 ` Mark Rutland 2016-04-04 9:02 ` Liviu Dudau 2016-04-04 9:02 ` Liviu Dudau 2016-04-04 5:16 ` Rob Herring 2016-04-04 9:01 ` Liviu Dudau 2016-04-04 9:01 ` Liviu Dudau 2016-04-01 16:21 ` [RFC][PATCH 2/2] drm/arm: Add support " Liviu Dudau 2016-04-12 15:47 ` Daniel Vetter 2016-04-12 15:47 ` Daniel Vetter 2016-04-12 17:13 ` Liviu Dudau 2016-04-12 17:13 ` Liviu Dudau 2016-04-12 19:30 ` Daniel Vetter 2016-04-12 19:30 ` Daniel Vetter 2016-04-12 15:58 ` Daniel Vetter 2016-04-12 15:58 ` Daniel Vetter 2016-04-12 17:16 ` Liviu Dudau 2016-04-12 17:16 ` Liviu Dudau 2016-04-12 19:31 ` Daniel Vetter 2016-04-12 19:31 ` Daniel Vetter 2016-04-13 11:48 ` Emil Velikov 2016-04-13 11:48 ` Emil Velikov 2016-04-13 13:48 ` Liviu Dudau [this message] 2016-04-13 13:48 ` Liviu Dudau 2016-04-13 15:29 ` Emil Velikov 2016-04-13 15:29 ` Emil Velikov
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=20160413134857.GN16063@e106497-lin.cambridge.arm.com \ --to=liviu.dudau@arm.com \ --cc=Brian.Starkey@arm.com \ --cc=David.Brown@arm.com \ --cc=airlied@gmail.com \ --cc=daniel@fooishbar.org \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=emil.l.velikov@gmail.com \ --cc=linux-kernel@vger.kernel.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: linkBe 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.