linux-kernel - Re: [PATCHv2 2/3] misc: add support for bmp18x chips to the bmp085 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Mar 2012 21:27:44 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Eric Andersson <eric.andersson@...xphere.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
	alan@...rguk.ukuu.org.uk, zhengguang.guo@...ch-sensortec.com,
	peter.moeller@...bosch.com
Subject: Re: [PATCHv2 2/3] misc: add support for bmp18x chips to the bmp085 driver

On Tuesday 06 March 2012, Eric Andersson wrote:
> The bmp18x chip family comes in an I2C respectively SPI variant.
> Hence, the bmp085 driver was split to support both buses.
> 
> Tested-by: Zhengguang Guo <zhengguang.guo@...ch-sensortec.com>
> Reviewed-by: Stefan Nilsson <stefan.nilsson@...xphere.com>
> Signed-off-by: Eric Andersson <eric.andersson@...xphere.com>

(adding Mark Brown to Cc)

I don't know much about regmap, but your description sounds like you
should be using it here, to simplify the differences between i2c and
spi in your driver instead of implementing your own abstraction
layer.

>  config BMP085
>  	tristate "BMP085 digital pressure sensor"
> -	depends on I2C && SYSFS
> +	depends on (I2C || SPI_MASTER) && SYSFS
>  	help
> -	  If you say yes here you get support for the Bosch Sensortec
> -	  BMP085 digital pressure sensor.
> +	  Say Y here if you want support for Bosch Sensortec's digital
> +	  pressure sensors BMP085 and BMP18x.
>  
>  	  To compile this driver as a module, choose M here: the
>  	  module will be called bmp085.
>  
> +config BMP085_I2C
> +	tristate "support I2C bus connection"
> +	depends on BMP085 && I2C
> +	help
> +	  Say Y here if you want to support Bosch Sensortec's digital pressure
> +	  sensor hooked to an I2C bus.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called bmp085-i2c.
> +
> +config BMP085_SPI
> +	tristate "support SPI bus connection"
> +	depends on BMP085 && SPI_MASTER
> +	help
> +	  Say Y here if you want to support Bosch Sensortec's digital pressure
> +	  sensor hooked to an SPI bus.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called bmp085-spi.
> +

IMHO this would be better expressed if you make CONFIG_BMP085 a hidden
option that is selected when either BMP085_I2C or BMP085_SPI are enabled.
Otherwise you make it possible to build just the base driver but neither
of the front-ends, which is a bit pointless.

>  }
> +EXPORT_SYMBOL(bmp085_probe);
>  

When you add internal symbols inside of your driver, best always use
EXPORT_SYMBOL_GPL. There is little practical difference here, but it
helps to get used to just always pick that as a default.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/