From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH] drivers: mmc: msm: update to new arm pfn_to_dma API Date: Tue, 18 Jan 2011 22:41:04 +0000 Message-ID: <20110118224104.GN16980@n2100.arm.linux.org.uk> References: <1295373844-27713-1-git-send-email-dwalker@codeaurora.org> <20110118182826.GI16980@n2100.arm.linux.org.uk> <1295382134.26904.7.camel@c-dwalke-linux.qualcomm.com> <20110118204446.GL16980@n2100.arm.linux.org.uk> <1295384420.26904.56.camel@c-dwalke-linux.qualcomm.com> <20110118211606.GM16980@n2100.arm.linux.org.uk> <1295386138.26904.70.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:33988 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752134Ab1ARWlU (ORCPT ); Tue, 18 Jan 2011 17:41:20 -0500 Content-Disposition: inline In-Reply-To: <1295386138.26904.70.camel@c-dwalke-linux.qualcomm.com> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Daniel Walker Cc: davidb@quicinc.com, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linus Torvalds On Tue, Jan 18, 2011 at 01:28:58PM -0800, Daniel Walker wrote: > On Tue, 2011-01-18 at 21:16 +0000, Russell King - ARM Linux wrote: > > On Tue, Jan 18, 2011 at 01:00:20PM -0800, Daniel Walker wrote: > > > Just greping the driver I found at least one writel() .. I'm not really > > > concerned with that tho. I use this driver, I need this driver to work. > > > You broke the driver, and your NAK'ing the fix .. > > > > If drivers use documented internal APIs, they _will_ break, and that's > > tough luck. The advertised API (DMA-mapping) is what we guarantee to > > support and fixup drivers for. > > I don't think that's a good policy. There could be reasons why a driver > might use an internal API .. Breaking the build is worse, to me, than > using an internal API. If things use the wrong APIs they get broken, plain and simple. It happens, and we cope with it and fix it properly when it happens, rather than subsituting the wrong way for another wrong way. > Did you give us a fix for this issue? That's what I was asking in the > last email cause it didn't appear like you touched that area. I gave you an example of how to fix the problem you reported - what more do you want?