Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
On 4/8/2013 6:26 PM, Mauro Carvalho Chehab wrote: > Em Mon, 8 Apr 2013 17:17:34 +0530 > Sekhar Nori escreveu: > >> Hi Maruo, >> >> On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: >>> Hi Sekhar, >>> >>> Em Mon, 8 Apr 2013 16:06:24 +0530 >>> Sekhar Nori escreveu: >>> On 4/8/2013 2:56 PM, Prabhakar lad wrote: > From: Lad, Prabhakar > > This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. >>> >>> Are you mean a branch at the media development tree for you to sent >>> pull requests for me? If so, just use the "master" branch at the media >> >> The pull request will be sent to my upstreams (ie the ARM SoC folks - >> Arnd and Olof). Since the platform data patches need driver patches to >> be applied first, I need a non-rebasing branch containing the driver >> stuff which I can use a dependency and apply platform patches on top. > > Hmm... I generally wait for arch patches to be applied first, before > sending driver patches. If you're willing to do that, I suggest that > Arnd/Olof should put those patches on a separate topic branch, and > sending an upstream pull request for them after mine. The patches can be put on a separate branch, but the branch wont build without the driver changes (eg need defintion of VPBE_ENC_DV_TIMINGS from include/media/davinci/vpbe_types.h). So this will need a immutable branch from you to depend on so Linus's tree won't have duplicate commits when Arnd/Olof send their pull request. > > If the patches are trivial, maybe the better would be to put both > media and arm patches at the same tree, with the other maintainers' > ack. This seems to be the easiest path at the moment. I will ack the platform parts and Prabhakar can issue a pull request for you. I have just checked that these patches won't cause a merge conflict with anything already queued through my tree. Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
On 4/8/2013 6:26 PM, Mauro Carvalho Chehab wrote: Em Mon, 8 Apr 2013 17:17:34 +0530 Sekhar Nori nsek...@ti.com escreveu: Hi Maruo, On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: Hi Sekhar, Em Mon, 8 Apr 2013 16:06:24 +0530 Sekhar Nori nsek...@ti.com escreveu: On 4/8/2013 2:56 PM, Prabhakar lad wrote: From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Are you mean a branch at the media development tree for you to sent pull requests for me? If so, just use the master branch at the media The pull request will be sent to my upstreams (ie the ARM SoC folks - Arnd and Olof). Since the platform data patches need driver patches to be applied first, I need a non-rebasing branch containing the driver stuff which I can use a dependency and apply platform patches on top. Hmm... I generally wait for arch patches to be applied first, before sending driver patches. If you're willing to do that, I suggest that Arnd/Olof should put those patches on a separate topic branch, and sending an upstream pull request for them after mine. The patches can be put on a separate branch, but the branch wont build without the driver changes (eg need defintion of VPBE_ENC_DV_TIMINGS from include/media/davinci/vpbe_types.h). So this will need a immutable branch from you to depend on so Linus's tree won't have duplicate commits when Arnd/Olof send their pull request. If the patches are trivial, maybe the better would be to put both media and arm patches at the same tree, with the other maintainers' ack. This seems to be the easiest path at the moment. I will ack the platform parts and Prabhakar can issue a pull request for you. I have just checked that these patches won't cause a merge conflict with anything already queued through my tree. Thanks, Sekhar -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Em Mon, 8 Apr 2013 17:17:34 +0530 Sekhar Nori escreveu: > Hi Maruo, > > On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: > > Hi Sekhar, > > > > Em Mon, 8 Apr 2013 16:06:24 +0530 > > Sekhar Nori escreveu: > > > >> On 4/8/2013 2:56 PM, Prabhakar lad wrote: > >>> From: Lad, Prabhakar > >>> > >>> This patch series enables VPBE display driver on DM355. > >> > >> These (this and the DM365 one) patches look good to me. I need to get an > >> immutable branch from Mauro where dependencies are queued and then I can > >> generate a pull request for these for ARM SoC. > > > > Are you mean a branch at the media development tree for you to sent > > pull requests for me? If so, just use the "master" branch at the media > > The pull request will be sent to my upstreams (ie the ARM SoC folks - > Arnd and Olof). Since the platform data patches need driver patches to > be applied first, I need a non-rebasing branch containing the driver > stuff which I can use a dependency and apply platform patches on top. Hmm... I generally wait for arch patches to be applied first, before sending driver patches. If you're willing to do that, I suggest that Arnd/Olof should put those patches on a separate topic branch, and sending an upstream pull request for them after mine. If the patches are trivial, maybe the better would be to put both media and arm patches at the same tree, with the other maintainers' ack. > > > tree: > > http://git.linuxtv.org/media_tree.git > > > > The master branch there is never rebased. I'll likely start to have > > topic branches on the next Kernel cycle, also at the same tree. > > Ideally I will use the immutable branch which you will also use to send > pull request to Linus so there are not unnecessary merge conflicts. When > will those branches be ready? I use a tree at Kernel.org for Linus submission. I only pull the patches there when I'm about to ask him to pull, and after being sure that those patches were already successfully merged at -next tree for some time. So, you should not base your tree there, as it will have there only the patches that I already submitted. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Hi Maruo, On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: > Hi Sekhar, > > Em Mon, 8 Apr 2013 16:06:24 +0530 > Sekhar Nori escreveu: > >> On 4/8/2013 2:56 PM, Prabhakar lad wrote: >>> From: Lad, Prabhakar >>> >>> This patch series enables VPBE display driver on DM355. >> >> These (this and the DM365 one) patches look good to me. I need to get an >> immutable branch from Mauro where dependencies are queued and then I can >> generate a pull request for these for ARM SoC. > > Are you mean a branch at the media development tree for you to sent > pull requests for me? If so, just use the "master" branch at the media The pull request will be sent to my upstreams (ie the ARM SoC folks - Arnd and Olof). Since the platform data patches need driver patches to be applied first, I need a non-rebasing branch containing the driver stuff which I can use a dependency and apply platform patches on top. > tree: > http://git.linuxtv.org/media_tree.git > > The master branch there is never rebased. I'll likely start to have > topic branches on the next Kernel cycle, also at the same tree. Ideally I will use the immutable branch which you will also use to send pull request to Linus so there are not unnecessary merge conflicts. When will those branches be ready? Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Hi Sekhar, Em Mon, 8 Apr 2013 16:06:24 +0530 Sekhar Nori escreveu: > On 4/8/2013 2:56 PM, Prabhakar lad wrote: > > From: Lad, Prabhakar > > > > This patch series enables VPBE display driver on DM355. > > These (this and the DM365 one) patches look good to me. I need to get an > immutable branch from Mauro where dependencies are queued and then I can > generate a pull request for these for ARM SoC. Are you mean a branch at the media development tree for you to sent pull requests for me? If so, just use the "master" branch at the media tree: http://git.linuxtv.org/media_tree.git The master branch there is never rebased. I'll likely start to have topic branches on the next Kernel cycle, also at the same tree. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
On 4/8/2013 2:56 PM, Prabhakar lad wrote: > From: Lad, Prabhakar > > This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
From: Lad, Prabhakar This patch series enables VPBE display driver on DM355. This patch series is dependent on VPSS clock cleanup patches (http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25613.html) posted. Changes for v8: 1: Removed extra line after break's and defines as pointed by Sekhar. 2: Included Ack from Sekhar for the second patch of the series. Changes for v7: 1: Fixed nits pointed by Sekhar for DM365 series. Changes for v6: 1: Fixed nits pointed by Sekhar. Changes for v5: 1: Rebased on 3.9, fix review comments pointed by Sekhar for DM365 series. Changes for v4: 1: pass different platform names to handle different ip's. Changes for v3: 1: Replaced obsolete preset API by timings API. Changes for v2: 1: Removed VPSS clock alias for master and slave which was sent for VPSS driver. since this patch was dependent on patch[1]. I will revist this patch once MC(captrure driver) goes into mainline. [1] http://www.spinics.net/lists/linux-media/msg50562.html Lad, Prabhakar (2): ARM: davinci: dm355: add support for v4l2 video display ARM: davinci: dm355 EVM: add support for VPBE display arch/arm/mach-davinci/board-dm355-evm.c | 71 +- arch/arm/mach-davinci/davinci.h |3 +- arch/arm/mach-davinci/dm355.c | 167 ++- 3 files changed, 233 insertions(+), 8 deletions(-) -- 1.7.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. This patch series is dependent on VPSS clock cleanup patches (http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg25613.html) posted. Changes for v8: 1: Removed extra line after break's and defines as pointed by Sekhar. 2: Included Ack from Sekhar for the second patch of the series. Changes for v7: 1: Fixed nits pointed by Sekhar for DM365 series. Changes for v6: 1: Fixed nits pointed by Sekhar. Changes for v5: 1: Rebased on 3.9, fix review comments pointed by Sekhar for DM365 series. Changes for v4: 1: pass different platform names to handle different ip's. Changes for v3: 1: Replaced obsolete preset API by timings API. Changes for v2: 1: Removed VPSS clock alias for master and slave which was sent for VPSS driver. since this patch was dependent on patch[1]. I will revist this patch once MC(captrure driver) goes into mainline. [1] http://www.spinics.net/lists/linux-media/msg50562.html Lad, Prabhakar (2): ARM: davinci: dm355: add support for v4l2 video display ARM: davinci: dm355 EVM: add support for VPBE display arch/arm/mach-davinci/board-dm355-evm.c | 71 +- arch/arm/mach-davinci/davinci.h |3 +- arch/arm/mach-davinci/dm355.c | 167 ++- 3 files changed, 233 insertions(+), 8 deletions(-) -- 1.7.4.1 -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
On 4/8/2013 2:56 PM, Prabhakar lad wrote: From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Thanks, Sekhar -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Hi Sekhar, Em Mon, 8 Apr 2013 16:06:24 +0530 Sekhar Nori nsek...@ti.com escreveu: On 4/8/2013 2:56 PM, Prabhakar lad wrote: From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Are you mean a branch at the media development tree for you to sent pull requests for me? If so, just use the master branch at the media tree: http://git.linuxtv.org/media_tree.git The master branch there is never rebased. I'll likely start to have topic branches on the next Kernel cycle, also at the same tree. Regards, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Hi Maruo, On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: Hi Sekhar, Em Mon, 8 Apr 2013 16:06:24 +0530 Sekhar Nori nsek...@ti.com escreveu: On 4/8/2013 2:56 PM, Prabhakar lad wrote: From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Are you mean a branch at the media development tree for you to sent pull requests for me? If so, just use the master branch at the media The pull request will be sent to my upstreams (ie the ARM SoC folks - Arnd and Olof). Since the platform data patches need driver patches to be applied first, I need a non-rebasing branch containing the driver stuff which I can use a dependency and apply platform patches on top. tree: http://git.linuxtv.org/media_tree.git The master branch there is never rebased. I'll likely start to have topic branches on the next Kernel cycle, also at the same tree. Ideally I will use the immutable branch which you will also use to send pull request to Linus so there are not unnecessary merge conflicts. When will those branches be ready? Thanks, Sekhar -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Em Mon, 8 Apr 2013 17:17:34 +0530 Sekhar Nori nsek...@ti.com escreveu: Hi Maruo, On 4/8/2013 4:26 PM, Mauro Carvalho Chehab wrote: Hi Sekhar, Em Mon, 8 Apr 2013 16:06:24 +0530 Sekhar Nori nsek...@ti.com escreveu: On 4/8/2013 2:56 PM, Prabhakar lad wrote: From: Lad, Prabhakar prabhakar.cse...@gmail.com This patch series enables VPBE display driver on DM355. These (this and the DM365 one) patches look good to me. I need to get an immutable branch from Mauro where dependencies are queued and then I can generate a pull request for these for ARM SoC. Are you mean a branch at the media development tree for you to sent pull requests for me? If so, just use the master branch at the media The pull request will be sent to my upstreams (ie the ARM SoC folks - Arnd and Olof). Since the platform data patches need driver patches to be applied first, I need a non-rebasing branch containing the driver stuff which I can use a dependency and apply platform patches on top. Hmm... I generally wait for arch patches to be applied first, before sending driver patches. If you're willing to do that, I suggest that Arnd/Olof should put those patches on a separate topic branch, and sending an upstream pull request for them after mine. If the patches are trivial, maybe the better would be to put both media and arm patches at the same tree, with the other maintainers' ack. tree: http://git.linuxtv.org/media_tree.git The master branch there is never rebased. I'll likely start to have topic branches on the next Kernel cycle, also at the same tree. Ideally I will use the immutable branch which you will also use to send pull request to Linus so there are not unnecessary merge conflicts. When will those branches be ready? I use a tree at Kernel.org for Linus submission. I only pull the patches there when I'm about to ask him to pull, and after being sure that those patches were already successfully merged at -next tree for some time. So, you should not base your tree there, as it will have there only the patches that I already submitted. Regards, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
