From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail168c2.megamailservers.com (mail168c2.megamailservers.com [69.49.111.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 84FB5B7D22 for ; Thu, 28 Jan 2010 01:08:13 +1100 (EST) Message-ID: <4B60333C.9040806@gaisler.com> Date: Wed, 27 Jan 2010 13:36:12 +0100 From: Jan Andersson MIME-Version: 1.0 To: Anatolij Gustschin Subject: Re: [PATCH 5/8 v2] powerpc/mpc5121: add USB host support References: <1264594052-20317-1-git-send-email-agust@denx.de> <1264594052-20317-6-git-send-email-agust@denx.de> In-Reply-To: <1264594052-20317-6-git-send-email-agust@denx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: wd@denx.de, dzu@denx.de, linux-usb@vger.kernel.org, linuxppc-dev@ozlabs.org, Bruce Schmid List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Anatolij Gustschin wrote: > @@ -259,6 +305,11 @@ static int ehci_fsl_setup(struct usb_hcd *hcd) > { > struct ehci_hcd *ehci = hcd_to_ehci(hcd); > int retval; > + struct fsl_usb2_platform_data *pdata; > + > + pdata = hcd->self.controller->platform_data; > + ehci->big_endian_desc = pdata->big_endian_desc; > + ehci->big_endian_mmio = pdata->big_endian_mmio; I recently posted some questions to linux-usb@vger about big_endian_mmio and the definition of the HC_LENGTH and HC_VERSION macros. The thread can be found here: http://marc.info/?l=linux-usb&m=126441448626924&w=2 The EHCI specification defines the CAPLENGTH register as an 8-bit register at byte offset 0 and HCIVERSION as a 16-bit register at byte offset 2. Performing a 32-bit read on a big endian system should therefore results in the following organisation (MSB .. LSB): CAPLENGTH : RESERVED : HCIVERSION The macros for reading CAPLENGTH and HCIVERSION (defined in include/linux/usb/ehci-def.h) look like: #define HC_LENGTH(p) (((p)>>00)&0x00ff) /* bits 7:0 */ #define HC_VERSION(p) (((p)>>16)&0xffff) /* bits 31:16 */ That is, they select the registers as they were organized within the word according to little endian. Is this not a problem for your controller/driver? Best regards, Jan