* Tony Lindgren t...@atomide.com [121030 09:31]:
OK so are people happy with the patches in this series?
Please everybody ack if no more comments so we can move on
towards getting CONFIG_MULTIPLATFORM to work for omaps.
Looks like Joerg has a new email address, I'll send this
series out
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same standard for omap-iommu.h.
This is needed because we are removing plat and mach includes
for ARM
* Tony Lindgren t...@atomide.com [121026 11:02]:
* Ohad Ben-Cohen o...@wizery.com [121026 02:56]:
Hi Laurent,
On Fri, Oct 26, 2012 at 11:35 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
That's on my to-do list, as well as porting the OMAP3 ISP driver to
videobuf2,
Hi Ohad,
On Friday 26 October 2012 07:50:56 Ohad Ben-Cohen wrote:
On Thu, Oct 25, 2012 at 11:39 PM, Tony Lindgren t...@atomide.com wrote:
Joerg and Ohad, do you have any opinions on this?
I agree that there's some merit in having a separate header file for
IOVMM, since it's a different
* Ohad Ben-Cohen o...@wizery.com [121026 02:56]:
Hi Laurent,
On Fri, Oct 26, 2012 at 11:35 AM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
That's on my to-do list, as well as porting the OMAP3 ISP driver to
videobuf2,
adding DT support, moving to the common clock
Hi Tony,
Thanks for the patch.
On Wednesday 24 October 2012 17:20:56 Tony Lindgren wrote:
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121025 01:39]:
I still think you should split this in two files, omap-iommu.h and omap-
iovmm.h. The later would just be arch/arm/plat-omap/include/plat/iovmm.h
moved
to include/linux.h.
Can you please explain a bit more why you're
Hi Tony,
On Thursday 25 October 2012 09:56:44 Tony Lindgren wrote:
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121025 01:39]:
I still think you should split this in two files, omap-iommu.h and omap-
iovmm.h. The later would just be arch/arm/plat-omap/include/plat/iovmm.h
moved to
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121025 13:23]:
Hi Tony,
On Thursday 25 October 2012 09:56:44 Tony Lindgren wrote:
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121025 01:39]:
I still think you should split this in two files, omap-iommu.h and omap-
iovmm.h.
On Thu, Oct 25, 2012 at 11:39 PM, Tony Lindgren t...@atomide.com wrote:
Joerg and Ohad, do you have any opinions on this?
I agree that there's some merit in having a separate header file for
IOVMM, since it's a different layer from the IOMMU API.
But in reality it's tightly coupled with OMAP's
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121019 02:41]:
On Thursday 18 October 2012 13:28:42 Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/iommu2.c
+++ b/arch/arm/mach-omap2/iommu2.c
@@ -17,6 +17,7 @@
#include linux/module.h
#include linux/slab.h
#include
Hi Tony,
On Wednesday 24 October 2012 15:34:12 Tony Lindgren wrote:
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121019 02:41]:
On Thursday 18 October 2012 13:28:42 Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/iommu2.c
+++ b/arch/arm/mach-omap2/iommu2.c
@@ -17,6 +17,7 @@
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same standard for omap-iommu.h.
This is needed because we are removing plat and mach includes
for ARM
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121024 16:54]:
On Wednesday 24 October 2012 15:34:12 Tony Lindgren wrote:
BTW, doing a test compile on v3.7-rc2, I'm seeing the following warnings
for omap3isp for isp_video_ioctl_ops:
Hi Tony,
Thanks for the patch.
On Thursday 18 October 2012 13:28:42 Tony Lindgren wrote:
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same
* Laurent Pinchart laurent.pinch...@ideasonboard.com [121019 02:41]:
Nitpicking, please keep the headers sorted alphabetically, here and in all
locations below (especially the OMAP3 ISP driver).
(OK, there's already one misplaced #include, but let's not make it worse :-))
Sure I'll check
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same standard for omap-iommu.h.
This is needed because we are removing plat and mach includes
for ARM
Tony,
Em Thu, 18 Oct 2012 13:28:42 -0700
Tony Lindgren t...@atomide.com escreveu:
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in files like intel-iommu.h and amd-iommu.h. Follow
the same standard
* Mauro Carvalho Chehab mche...@redhat.com [121018 13:58]:
Tony,
Em Thu, 18 Oct 2012 13:28:42 -0700
Tony Lindgren t...@atomide.com escreveu:
Looks like the iommu framework does not have generic functions
exported for all the needs yet. The hardware specific functions
are defined in
19 matches
Mail list logo