From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Toru Oishi <toru.oishi.zj@rvc.renesas.com>
Subject: Re: [PATCH v2 00/32] VSP: Add R-Car Gen3 support
Date: Sun, 13 Dec 2015 18:53:38 +0000 [thread overview]
Message-ID: <53707193.Qr7t8enSnR@avalon> (raw)
In-Reply-To: <566A8CAF.9080200@rvc.renesas.com>
Hello Khiem,
On Friday 11 December 2015 15:43:27 Khiem Nguyen wrote:
> On 12/6/2015 5:54 AM, Laurent Pinchart wrote:
> > On Saturday 05 December 2015 11:57:49 Geert Uytterhoeven wrote:
> >> On Sat, Dec 5, 2015 at 3:12 AM, Laurent Pinchart wrote:
> >>> This patch set adds support for the Renesas R-Car Gen3 SoC family to the
> >>> VSP1 driver. The large number of patches is caused by a change in the
> >>> display controller architecture that makes usage of the VSP mandatory as
> >>> the display controller has lost the ability to read data from memory.
> >>>
> >>> Patch 01/32 to 27/32 prepare for the implementation of an API exported
> >>> to the DRM driver in patch 28/32. Patches 31/32 enables support for the
> >>> R-Car Gen3 family, and patch 32/32 finally enhances perfomances by
> >>> implementing support for display lists.
> >>>
> >>> The major change compared to v1 is the usage of the IP version register
> >>> instead of DT properties to configure device parameters such as the
> >>> number of BRU inputs or the availability of the BRU.
> >>
> >> Thanks for your series!
> >>
> >> As http://git.linuxtv.org/pinchartl/media.git/tag/?id=vsp1-kms-20151112
> >> is getting old, and has lots of conflicts with recent -next, do you plan
> >> to publish this in a branch, and a separate branch for integration, to
> >> ease integration in renesas-drivers?
> >>
> >> Alternatively, I can just import the series you posted, but having the
> >> broken-out integration part would be nice.
> >
> > The issue I'm facing is that there's more than just two series. Beside the
> > base VSP patches from this series, I have a series of DRM patches that
> > depend on this one, a series of V4L2 core patches, another series of VSP
> > patches that I still need to finish and a bunch of integration patches.
> > As some of these have dependencies on H3 CCF support that hasn't landed
> > in Simon's tree yet, I have merged your topic/cpg-mssr-v6 and
> > topic/r8a7795-drivers-sh-v1 branches into my tree for development.
> >
> > I could keep all series in separate branches and merge the two topic
> > branches last, but that's not very handy during development when I have
> > to continuously rebase my patches. Is there a way I could handle this
> > that would make your life easier while not making mine more difficult ?
> >
> > In the meantime I've pushed vsp1-kms-20151206 to
> > git://linuxtv.org/pinchartl/media.git.
>
> I failed to confirm DU (VGA port) with above branch.
>
> To make DU (VGA port) work,
> it seems I need to merge more branches like topic/cpg-mssr-v6
> and topic/r8a7795-drivers-sh-v1 branches from renesas-drivers repo, is
> it correct ?
The
git://linuxtv.org/pinchartl/media.git vsp1-kms-20151206
branch already contains topic/r8a7795-drivers-sh-v1 and topic/cpg-mssr-v6.
What is the failure you're seeing ?
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Toru Oishi <toru.oishi.zj@rvc.renesas.com>
Subject: Re: [PATCH v2 00/32] VSP: Add R-Car Gen3 support
Date: Sun, 13 Dec 2015 20:53:38 +0200 [thread overview]
Message-ID: <53707193.Qr7t8enSnR@avalon> (raw)
In-Reply-To: <566A8CAF.9080200@rvc.renesas.com>
Hello Khiem,
On Friday 11 December 2015 15:43:27 Khiem Nguyen wrote:
> On 12/6/2015 5:54 AM, Laurent Pinchart wrote:
> > On Saturday 05 December 2015 11:57:49 Geert Uytterhoeven wrote:
> >> On Sat, Dec 5, 2015 at 3:12 AM, Laurent Pinchart wrote:
> >>> This patch set adds support for the Renesas R-Car Gen3 SoC family to the
> >>> VSP1 driver. The large number of patches is caused by a change in the
> >>> display controller architecture that makes usage of the VSP mandatory as
> >>> the display controller has lost the ability to read data from memory.
> >>>
> >>> Patch 01/32 to 27/32 prepare for the implementation of an API exported
> >>> to the DRM driver in patch 28/32. Patches 31/32 enables support for the
> >>> R-Car Gen3 family, and patch 32/32 finally enhances perfomances by
> >>> implementing support for display lists.
> >>>
> >>> The major change compared to v1 is the usage of the IP version register
> >>> instead of DT properties to configure device parameters such as the
> >>> number of BRU inputs or the availability of the BRU.
> >>
> >> Thanks for your series!
> >>
> >> As http://git.linuxtv.org/pinchartl/media.git/tag/?id=vsp1-kms-20151112
> >> is getting old, and has lots of conflicts with recent -next, do you plan
> >> to publish this in a branch, and a separate branch for integration, to
> >> ease integration in renesas-drivers?
> >>
> >> Alternatively, I can just import the series you posted, but having the
> >> broken-out integration part would be nice.
> >
> > The issue I'm facing is that there's more than just two series. Beside the
> > base VSP patches from this series, I have a series of DRM patches that
> > depend on this one, a series of V4L2 core patches, another series of VSP
> > patches that I still need to finish and a bunch of integration patches.
> > As some of these have dependencies on H3 CCF support that hasn't landed
> > in Simon's tree yet, I have merged your topic/cpg-mssr-v6 and
> > topic/r8a7795-drivers-sh-v1 branches into my tree for development.
> >
> > I could keep all series in separate branches and merge the two topic
> > branches last, but that's not very handy during development when I have
> > to continuously rebase my patches. Is there a way I could handle this
> > that would make your life easier while not making mine more difficult ?
> >
> > In the meantime I've pushed vsp1-kms-20151206 to
> > git://linuxtv.org/pinchartl/media.git.
>
> I failed to confirm DU (VGA port) with above branch.
>
> To make DU (VGA port) work,
> it seems I need to merge more branches like topic/cpg-mssr-v6
> and topic/r8a7795-drivers-sh-v1 branches from renesas-drivers repo, is
> it correct ?
The
git://linuxtv.org/pinchartl/media.git vsp1-kms-20151206
branch already contains topic/r8a7795-drivers-sh-v1 and topic/cpg-mssr-v6.
What is the failure you're seeing ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-12-13 18:53 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 2:12 [PATCH v2 00/32] VSP: Add R-Car Gen3 support Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 01/32] v4l: vsp1: Change the type of the rwpf field in struct vsp1_video Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 02/32] v4l: vsp1: Store the memory format in struct vsp1_rwpf Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 03/32] v4l: vsp1: Move video operations to vsp1_rwpf Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 04/32] v4l: vsp1: Rename vsp1_video_buffer to vsp1_vb2_buffer Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 05/32] v4l: vsp1: Move video device out of struct vsp1_rwpf Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 06/32] v4l: vsp1: Make rwpf operations independent of video device Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 07/32] v4l: vsp1: Support VSP1 instances without any UDS Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 08/32] v4l: vsp1: Move vsp1_video pointer from vsp1_entity to vsp1_rwpf Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 09/32] v4l: vsp1: Remove struct vsp1_pipeline num_video field Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 10/32] v4l: vsp1: Decouple pipeline end of frame processing from vsp1_video Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 11/32] v4l: vsp1: Split pipeline management code from vsp1_video.c Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 12/32] v4l: vsp1: Rename video pipeline functions to use vsp1_video prefix Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 13/32] v4l: vsp1: Extract pipeline initialization code into a function Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 14/32] v4l: vsp1: Reuse local variable instead of recomputing it Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 15/32] v4l: vsp1: Extract link creation to separate function Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 16/32] v4l: vsp1: Document the vsp1_pipeline structure Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 17/32] v4l: vsp1: Fix typo in VI6_DISP_IRQ_STA_DST register name Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 21:47 ` Sergei Shtylyov
2015-12-05 21:47 ` Sergei Shtylyov
2015-12-05 22:20 ` Laurent Pinchart
2015-12-05 22:20 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 18/32] v4l: vsp1: Set the SRU CTRL0 register when starting the stream Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 19/32] v4l: vsp1: Remove unused module read functions Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 20/32] v4l: vsp1: Move entity route setup function to vsp1_entity.c Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 21/32] v4l: vsp1: Make number of BRU inputs configurable Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 22/32] v4l: vsp1: Make the BRU optional Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 23/32] v4l: vsp1: Move format info to vsp1_pipe.c Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 24/32] v4l: vsp1: Make the userspace API optional Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:12 ` [PATCH v2 25/32] v4l: vsp1: Make pipeline inputs array index by RPF index Laurent Pinchart
2015-12-05 2:12 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 26/32] v4l: vsp1: Set the alpha value manually in RPF and WPF s_stream handlers Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 27/32] v4l: vsp1: Don't validate links when the userspace API is disabled Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 28/32] v4l: vsp1: Add VSP+DU support Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 29/32] v4l: vsp1: Disconnect unused RPFs from the DRM pipeline Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 30/32] v4l: vsp1: Implement atomic update for the DRM driver Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 31/32] v4l: vsp1: Add support for the R-Car Gen3 VSP2 Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 2:13 ` [PATCH v2 32/32] v4l: vsp1: Add display list support Laurent Pinchart
2015-12-05 2:13 ` Laurent Pinchart
2015-12-05 10:57 ` [PATCH v2 00/32] VSP: Add R-Car Gen3 support Geert Uytterhoeven
2015-12-05 10:57 ` Geert Uytterhoeven
2015-12-05 22:54 ` Laurent Pinchart
2015-12-05 22:54 ` Laurent Pinchart
2015-12-11 8:43 ` Khiem Nguyen
2015-12-11 8:43 ` Khiem Nguyen
2015-12-13 18:53 ` Laurent Pinchart [this message]
2015-12-13 18:53 ` Laurent Pinchart
2015-12-14 1:58 ` Khiem Nguyen
2015-12-14 1:58 ` Khiem Nguyen
2015-12-16 8:39 ` Geert Uytterhoeven
2015-12-16 8:39 ` Geert Uytterhoeven
2015-12-16 10:37 ` Laurent Pinchart
2015-12-16 10:37 ` Laurent Pinchart
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=53707193.Qr7t8enSnR@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert@linux-m68k.org \
--cc=khiem.nguyen.xt@rvc.renesas.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=toru.oishi.zj@rvc.renesas.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.