From: Dave Airlie <airlied@gmail.com> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Cc: dri-devel <dri-devel@lists.freedesktop.org>, linux-renesas-soc@vger.kernel.org, Linux Media Mailing List <linux-media@vger.kernel.org> Subject: Re: [PATCH 0/2] Renesas R-Car Gen3 DU alpha and z-order support Date: Fri, 22 Apr 2016 05:45:34 +1000 [thread overview] Message-ID: <CAPM=9txvkSgKZxkiAr-EoGBP8=b-jo3bxibt5Xam=7qCq8w6AA@mail.gmail.com> (raw) In-Reply-To: <1461201253-12170-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com> On 21 April 2016 at 11:14, Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> wrote: > Hello, > > This patch series implement support for alpha and z-order configuration in the > R-Car DU driver for the Gen3 SoCs family. > > The Gen3 SoCs delegate composition to an external IP core called VSP, > supported by a V4L2 driver. The DU driver interfaces with the VSP driver using > direct function calls. Alpha and z-order configuration is implemented in the > VSP driver, the DU driver thus just needs to pass the values using the VSP > API. > > This series depends on a large VSP series that has been merged in the Linux > media git tree for v4.7. Dave, instead of merging the media tree in your tree > to pull the dependency in, it would be easier to get those two patches > upstream through the media tree. I don't expect any conflict related to the > DU driver for v4.7. If you're fine with that, could you ack the patches ? > > Laurent Pinchart (2): > drm: rcar-du: Add Z-order support for VSP planes > drm: rcar-du: Add alpha support for VSP planes > Seems fine, Acked-by: Dave AIrlie <airlied@redhat.com> for inclusion via media. Dave. > drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 16 ++++++++++++---- > drivers/gpu/drm/rcar-du/rcar_du_vsp.h | 2 ++ > 2 files changed, 14 insertions(+), 4 deletions(-) > > -- > Regards, > > Laurent Pinchart > > _______________________________________________ > 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: Dave Airlie <airlied@gmail.com> To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Cc: linux-renesas-soc@vger.kernel.org, dri-devel <dri-devel@lists.freedesktop.org>, Linux Media Mailing List <linux-media@vger.kernel.org> Subject: Re: [PATCH 0/2] Renesas R-Car Gen3 DU alpha and z-order support Date: Fri, 22 Apr 2016 05:45:34 +1000 [thread overview] Message-ID: <CAPM=9txvkSgKZxkiAr-EoGBP8=b-jo3bxibt5Xam=7qCq8w6AA@mail.gmail.com> (raw) In-Reply-To: <1461201253-12170-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com> On 21 April 2016 at 11:14, Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> wrote: > Hello, > > This patch series implement support for alpha and z-order configuration in the > R-Car DU driver for the Gen3 SoCs family. > > The Gen3 SoCs delegate composition to an external IP core called VSP, > supported by a V4L2 driver. The DU driver interfaces with the VSP driver using > direct function calls. Alpha and z-order configuration is implemented in the > VSP driver, the DU driver thus just needs to pass the values using the VSP > API. > > This series depends on a large VSP series that has been merged in the Linux > media git tree for v4.7. Dave, instead of merging the media tree in your tree > to pull the dependency in, it would be easier to get those two patches > upstream through the media tree. I don't expect any conflict related to the > DU driver for v4.7. If you're fine with that, could you ack the patches ? > > Laurent Pinchart (2): > drm: rcar-du: Add Z-order support for VSP planes > drm: rcar-du: Add alpha support for VSP planes > Seems fine, Acked-by: Dave AIrlie <airlied@redhat.com> for inclusion via media. Dave. > drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 16 ++++++++++++---- > drivers/gpu/drm/rcar-du/rcar_du_vsp.h | 2 ++ > 2 files changed, 14 insertions(+), 4 deletions(-) > > -- > Regards, > > Laurent Pinchart > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel _______________________________________________ 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-21 19:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-21 1:14 [PATCH 0/2] Renesas R-Car Gen3 DU alpha and z-order support Laurent Pinchart 2016-04-21 1:14 ` Laurent Pinchart 2016-04-21 1:14 ` [PATCH 1/2] drm: rcar-du: Add Z-order support for VSP planes Laurent Pinchart 2016-04-21 16:10 ` Daniel Vetter 2016-04-21 16:10 ` Daniel Vetter 2016-04-21 21:00 ` Laurent Pinchart 2016-04-22 8:29 ` Daniel Vetter 2016-04-21 1:14 ` [PATCH 2/2] drm: rcar-du: Add alpha " Laurent Pinchart 2016-04-21 1:14 ` Laurent Pinchart 2016-04-21 19:45 ` Dave Airlie [this message] 2016-04-21 19:45 ` [PATCH 0/2] Renesas R-Car Gen3 DU alpha and z-order support Dave Airlie
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='CAPM=9txvkSgKZxkiAr-EoGBP8=b-jo3bxibt5Xam=7qCq8w6AA@mail.gmail.com' \ --to=airlied@gmail.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=laurent.pinchart+renesas@ideasonboard.com \ --cc=linux-media@vger.kernel.org \ --cc=linux-renesas-soc@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.