From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Olech Subject: Re: [PATCH] mmc: USB SDIO/SD/MMC Host Controller (VUB300) driver Resubmission Date: Mon, 24 Jan 2011 16:17:17 +0000 Message-ID: <1295885837.1677.28.camel@apple-mac> References: <20B0EAA71DD7413A9A29D0493C6C1D87@AN00536> <20101116150022.GA27726@void.printf.net> <27884BED0E3C489C8849EE12A803F536@AN00536> <4CE41BE3.1060806@elandigitalsystems.com> <4CEA86D4.9050109@elandigitalsystems.com> <1295607004.1816.6.camel@apple-mac> <20110122142112.GC15620@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.17.8]:64614 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752824Ab1AXQRb (ORCPT ); Mon, 24 Jan 2011 11:17:31 -0500 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Nicolas Pitre Cc: Wolfram Sang , Chris Ball , linux-mmc@vger.kernel.org, David Vrabel On Sat, 2011-01-22 at 14:07 -0500, Nicolas Pitre wrote: > On Sat, 22 Jan 2011, Wolfram Sang wrote: > > On Fri, Jan 21, 2011 at 04:14:46PM -0500, Nicolas Pitre wrote: > > > On Fri, 21 Jan 2011, Tony Olech wrote: > > > > Add a driver for Elan Digital System's VUB300 chip > > > > which is a USB connected SDIO/SDmem/MMC host controller. > > > > A VUB300 chip enables a USB 2.0 or USB 1.1 connected host > > > > computer to use SDIO/SD/MMC cards without the need for > > > > a directly connected, for example via PCI, SDIO host > > > > controller. > > > > There are 5 "do not initialise statics" errors reported by scripts/checkpatch.pl > > > you probably should fix those. They are due to lines such as: > > > static int pad_input_to_usb_pkt = 0; > > > static int disable_offload_processing = 0; > > > static int force_1_bit_data_xfers = 0; > > > static int force_polling_for_irqs = 0; > > Should those be static anyhow? Being USB, you could probably hook up two of > > those and want to operate one of them in this and the other one in another > > mode? > You could. Whether or not you would is another question. Until then I > don't think it is worth bothering with such corner cases for the initial > merging of this driver. > Nicolas Some of the module parameters are indeed per device, but how could that be implemented? Tony Olech