Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756322AbZFXIv4 (ORCPT ); Wed, 24 Jun 2009 04:51:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753080AbZFXIvp (ORCPT ); Wed, 24 Jun 2009 04:51:45 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:34087 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751893AbZFXIvo (ORCPT ); Wed, 24 Jun 2009 04:51:44 -0400 X-Auth-Info: MWyy1wSFublyVE9DsCRgTVNHi0eFXh2BuE9JgI2AIdg= Message-ID: <4A41E91F.1020509@grandegger.com> Date: Wed, 24 Jun 2009 10:51:43 +0200 From: Wolfgang Grandegger User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Oliver Hartkopp CC: David Miller , heiko.carstens@de.ibm.com, schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH] can: let SJA1000 driver depend on HAS_IOMEM References: <20090623073120.GA5955@osiris.boeblingen.de.ibm.com> <4A412C53.8050607@grandegger.com> <4A41CD36.8030202@hartkopp.net> <20090624.000109.49664041.davem@davemloft.net> <4A41E31B.1030703@grandegger.com> <4A41E56F.6030302@hartkopp.net> In-Reply-To: <4A41E56F.6030302@hartkopp.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1665 Lines: 41 Oliver Hartkopp wrote: > Wolfgang Grandegger wrote: >> David Miller wrote: >>> From: Oliver Hartkopp > >>>> the question is, if we should add HAS_IOMEM to almost every SJA1000 depended >>>> driver like SJA1000_PLATFORM, SJA1000_OF_PLATFORM, EMS_PCI and KVASER_PCI ??? >>>> >>>> Is it possible to have a support for the SJA1000 that does *not* depend on >>>> HAS_IOMEM? >> In principle yes by using an appropriate driver accessing the SJA1000 >> with other methods. But I might be wrong because it does not make sense >> hardware-wise. >> >>> This was my initial impression when I saw Wolfgang's suggested patch, >>> and I still feel this way, and thus Heiko's patch seems the best for >>> now until there is an exception. >>> >>> And in fact Heiko's patch has been in my tree for a while already :) >> OK, that's fine for the moment. We may even consider making CONFIG_CAN >> depend on HAS_IOMEM like for SPI, USB, Serial, etc. > > Why CONFIG_CAN ?? > > CONFIG_CAN provides a network protocol family that can be used e.g. with the > vcan driver without any hardware. So HAS_IOMEM only has to take care of some > drivers, that fiddle on CAN controller registers themselves. E.g. for SPI, USB > and Serial these 'underlying' interfaces bring their own requirements. When we > depend on SPI, it should bring HAS_IOMEM as a dependency of SPI. OK, then s/CONFIG_CAN/CONFIG_CAN_DEV/ Wolfgang. -- 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/