Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263815AbUFTTrm (ORCPT ); Sun, 20 Jun 2004 15:47:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263770AbUFTTrm (ORCPT ); Sun, 20 Jun 2004 15:47:42 -0400 Received: from caramon.arm.linux.org.uk ([212.18.232.186]:17926 "EHLO caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP id S263815AbUFTTrj (ORCPT ); Sun, 20 Jun 2004 15:47:39 -0400 Date: Sun, 20 Jun 2004 20:47:23 +0100 From: Russell King To: Krzysztof Halasa Cc: James Bottomley , Linux Kernel , SCSI Mailing List Subject: Re: Proposal for new generic device API: dma_get_required_mask() Message-ID: <20040620204723.B641@flint.arm.linux.org.uk> Mail-Followup-To: Krzysztof Halasa , James Bottomley , Linux Kernel , SCSI Mailing List References: <1087481331.2210.27.camel@mulgrave> <20040618102120.A29213@flint.arm.linux.org.uk> <20040619212246.B8063@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from khc@pm.waw.pl on Sun, Jun 20, 2004 at 02:00:42AM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1737 Lines: 40 > Wouldn't it be better to not touch the masks (which are device > capabilities rather than platform limitations) and let alloc/map > functions always use the correct half of RAM? They are device limitations - the SA1111 device (which is a bus master device in its own right) itself is the cause of the problem, so the devices integrated inside it need to know. Eg: +------------------------+ +---------------------------+ | | | | | SSP CPU--bus i/f-|-----+-----|-bus i/f OHCI SSP SAC | | | | | | | | | | | | | +----------------+ | | | +-------+-----+----+ | | SA11x0 | +-------+ | SA1111 | +------------------------+ | SDRAM | +---------------------------+ +-------+ The SDRAM bus is shared between the SA11x0 and SA1111 devices, and there is an arbitration protocol to hand off the SDRAM bus between the two devices. The SSP and CPU itself inside the SA11x0 can access all SDRAM memory, but the OHCI, SSP and SAC devices within the SA1111 are affected by the problem. So it's quite correct for this to be a device thing not a platform thing. It _is_ the SA1111 device itself which has the problem. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core - 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/