On Wednesday 18 March 2015, Mark Brown wrote:
> On Sun, Mar 08, 2015 at 10:42:59PM +0100, Arnd Bergmann wrote:
> > diff --git a/arch/arm/mach-s3c64xx/mach-crag6410.c
> > b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > index f395a5617142..cbe353a5450e 100644
> > --- a/arch/arm/mach-s3c64xx/mach-crag64
On Sat, Mar 21, 2015 at 04:38:21PM +, Charles Keepax wrote:
> So adding a bit of an offset into the PMIC with the fixed IRQ
> base fixes the problem. Although I am not sure if it would be
> better to move both PMICs onto a fixed IRQ base so there is no
> chance of the clashing. Any thoughts?
On Mon, Mar 02, 2015 at 01:36:03PM +0100, Arnd Bergmann wrote:
> Most of the code for the s3c64xx platform is only used when booting
> with ATAGS based board files, but not when using device-tree.
>
> This tries to identify all the s3c64xx specific code that is
> unneeded when CONFIG_ATAGS is not
On Wed, Mar 18, 2015 at 12:02:34AM +, Mark Brown wrote:
> On Sun, Mar 08, 2015 at 10:42:59PM +0100, Arnd Bergmann wrote:
> > On Friday 06 March 2015 17:43:16 Charles Keepax wrote:
> > diff --git a/arch/arm/mach-s3c64xx/mach-crag6410.c
> > b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > index f395a
Tobias Jakobi wrote:
> Hello,
>
> this series exposes async execution of G2D command buffers to userspace. Also
> includes is a small performance analysis test, which can also be used to
> stress test the engine. The async operation is of course also tested.
>
> Please review and let me know wh
