Return-Path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:35309 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755662Ab0FNRI1 (ORCPT ); Mon, 14 Jun 2010 13:08:27 -0400 Date: Mon, 14 Jun 2010 17:08:23 +0000 From: David Brown Subject: Re: MSM NAND - Subpage size reading Message-ID: <20100614170823.GA14641@huya.qualcomm.com> References: <201005301843.03629.david.lanzendoerfer@o2s.ch> <20100601165758.GB610@huya.qualcomm.com> <201006012205.47125.david.lanzendoerfer@o2s.ch> <201006141758.36089.david.lanzendoerfer@o2s.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201006141758.36089.david.lanzendoerfer@o2s.ch> Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: David =?iso-8859-1?Q?Lanzend=F6rfer?= Cc: linux-arm-msm@vger.kernel.org On Mon, Jun 14, 2010 at 05:58:32PM +0200, David Lanzendörfer wrote: > This was the solution for our kind of problem. But our driver > seems to be deplaced and in consquence of this, it does not > draw benefit of the full NAND framework power. Please correct > me if I'm wrong. But I do not have ANY clou, how I could > propagate the disablement of subpage size capability for this > driver. Write a patch, and send it to this list. Keep in mind that the MSM code is under a lot of flux right now. David