Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752605Ab2JODTt (ORCPT ); Sun, 14 Oct 2012 23:19:49 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:59385 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751937Ab2JODTs (ORCPT ); Sun, 14 Oct 2012 23:19:48 -0400 MIME-Version: 1.0 In-Reply-To: <507A6FA5.1000800@yahoo.es> References: <507A6FA5.1000800@yahoo.es> Date: Mon, 15 Oct 2012 08:49:47 +0530 X-Google-Sender-Auth: t9RgsQ2ciUpSxksIRkGLI58i_-0 Message-ID: Subject: Re: [PATCH REGRESSION FIX] dw_dmac: make driver's endianness configurable From: viresh kumar To: Hein Tibosch Cc: Andrew Morton , Andy Shevchenko , spear-devel , Hans-Christian Egtvedt , Arnd Bergmann , Linux Kernel Mailing List , "ludovic.desroches" , Havard Skinnemoen , Nicolas Ferre Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1171 Lines: 29 On Sun, Oct 14, 2012 at 1:24 PM, Hein Tibosch wrote: > From: Hein Tibosch > > The dw_dmac was originally developed for avr32 to be used with the Synopsys > DesignWare AHB DMA controller. Starting from 2.6.38, access to the device's i/o > memory was done with the little-endian readl/writel functions(1) > > This broke the driver for the avr32 platform, because it needs big (native) > endian accessors. > This patch makes the endianness configurable using 'DW_DMAC_BIG_ENDIAN_IO', > which will default be true for AVR32 > > I submitted this patch before(2) but then waited for Andy to finish other > changes to the same module(3). > > (1) https://patchwork.kernel.org/patch/608211 > (2) https://lkml.org/lkml/2012/8/26/148 > (3) https://lkml.org/lkml/2012/9/21/173 > > Signed-off-by: Hein Tibosch Good. Acked-by: Viresh Kumar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/