Marek Szyprowski wrote:
>
> Hello,
>
> This patch series perform an update on interrupts support for
> S5PC210/S5PV310/EXYNOS4 platform. Two optional features have been added.
> The first one is GPIO interrupts handler, a second is support for board
> specific interrupts. The patches have been pr
Abhilash Kesavan wrote:
>
> Adds the device definitions, platform specific initialization and
> clocks for SATA on ARMLEX4210.
>
> Signed-off-by: Abhilash Kesavan
> ---
> arch/arm/mach-exynos4/Kconfig |1 +
> arch/arm/mach-exynos4/Makefile|1 +
> arch/arm
Jeongtae Park wrote:
>
> This patch adds clock support for MFC v5.1.
>
> Reviewed-by: Peter Oh
> Signed-off-by: Jeongtae Park
> Cc: Marek Szyprowski
> Cc: Kamil Debski
> ---
> arch/arm/mach-s5pv310/clock.c | 68
> +++
> arch/arm/mach-s5pv310/include/ma
Kamil Debski wrote:
>
> This patch adds platform support for Multi Format Codec 5.1.
> MFC 5.1 is capable of handling a range of video codecs and this driver
> provides V4L2 interface for video decoding.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> arch/arm/mach-s5pv3
Marek Szyprowski wrote:
>
> From: Sylwester Nawrocki
>
> Add support for fourth FIMC platform device definition and define
> resources for FIMC modules on S5PV310 machines.
>
> Signed-off-by: Sylwester Nawrocki
> Signed-off-by: Kyungmin Park
> Signed-off-by: Marek Szyprowski
> ---
> arch/ar
Sangbeom Kim wrote:
>
> The Following patches support high resolution timer for s5p series.
> In this version, I had modified smdkv210 clockevent source.
> Because, PWM timer3 is used as pwm backlight driver in the smdkv210.
> and In previous version(v3), I had made a mistake for making patches.
On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > does not support IOMMUs, but that could be changed by wrapping it
> > > > using the include/asm-generic/dma-mapping-common.h infrastructure.
> > >
> > > ARM dma-mapping framework also requires some additional research for
> > > better DMA
>
Hello,
On Friday, March 11, 2011 4:15 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> > On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
> >
> > > On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > > The iommu API is not really meant to be KVM specific, it
On Friday 11 March 2011, Marek Szyprowski wrote:
> On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
>
> > On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > The iommu API is not really meant to be KVM specific, it's just that the
> > > > in-tree users are basically limited to KVM at th
Hello,
On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> > > The iommu API is not really meant to be KVM specific, it's just that the
> > > in-tree users are basically limited to KVM at the moment. Another user
> > > that
> > > is coming
On Friday 11 March 2011, Marek Szyprowski wrote:
> > The iommu API is not really meant to be KVM specific, it's just that the
> > in-tree users are basically limited to KVM at the moment. Another user that
> > is coming up soon is the vmio device driver that can be used to
> > transparently
> > pa
Hello,
On Friday, March 11, 2011 12:51 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> >
> > We followed the style of iommu API for other mainline ARM platforms (both
> > OMAP and MSM
> > also have custom API for their iommu modules). I've briefly checked
> > includ
On Friday 11 March 2011, Marek Szyprowski wrote:
>
> We followed the style of iommu API for other mainline ARM platforms (both
> OMAP and MSM
> also have custom API for their iommu modules). I've briefly checked
> include/linux/iommu.h
> API and I've noticed that it has been designed mainly for
Hello,
On Thursday, March 10, 2011 3:52 PM Arnd Bergmann wrote:
> On Friday 04 March 2011, Marek Szyprowski wrote:
> > From: Andrzej Pietrasiewicz
> >
> > This patch performs a complete rewrite of sysmmu driver for Samsung
> > platform:
> > - the new version introduces an api to construct devic
Mark Brown wrote:
>
> The cpufreq init function is referenced from the driver structure and
> we don't appear to have annotations which allow us to mark that it'll
> never be called after system init, causing the linker consistency
> infrastructure to complain. Just remove the __init annotation to
15 matches
Mail list logo
