Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965983Ab3DQRVA (ORCPT ); Wed, 17 Apr 2013 13:21:00 -0400 Received: from mail-ea0-f181.google.com ([209.85.215.181]:64623 "EHLO mail-ea0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965409Ab3DQRUo (ORCPT ); Wed, 17 Apr 2013 13:20:44 -0400 MIME-Version: 1.0 In-Reply-To: <20130417.131156.13653463501819067.davem@davemloft.net> References: <516E88A9.9070200@ti.com> <20130417.131156.13653463501819067.davem@davemloft.net> Date: Wed, 17 Apr 2013 10:20:43 -0700 X-Google-Sender-Auth: 26VFKeQWCAnt3bdZI35Q1E2hfG8 Message-ID: Subject: Re: Device driver memory 'mmap()' function helper cleanup From: Linus Torvalds To: David Miller Cc: Tomi Valkeinen , Linux Kernel Mailing List , Clemens Ladisch , Arnd Bergmann , Takashi Iwai , Mauro Carvalho Chehab , Ralf Baechle Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 24 On Wed, Apr 17, 2013 at 10:11 AM, David Miller wrote: > > Yeah, the only thing special we do on sparc is interpret the PFN > specially. We munge it into the real physical address and then > pass it all down to remap_pfn_range() to do the real work. So the main thing I want to check is that *if* it's given a regular RAM physical address, it still works? Some drivers basically allocate DMA memory and then pass on the resulting physical address to this. Others pass in the PCI BAR addresses etc. And some try to use "remap_pfn_range()", and others try to use "io_remap_pfn_range()", and quite frankly, from what I can tell we can just always use the "io_" version because it ends up being a proper superset. I'm pretty sure it works fine the way I read it, but I'm just verifying.. Linus -- 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/