Re: [PATCH v3] input/misc: new ADXL345/346 driver
From: Chris Verges <hidden>
Date: 2009-10-20 18:46:08
Possibly related (same subject, not in this thread)
- 2010-08-06 · Re: [PATCH v3] input/misc: new ADXL345/346 driver · Dmitry Torokhov <dmitry.torokhov@gmail.com>
- 2010-08-05 · RE: [PATCH v3] input/misc: new ADXL345/346 driver · "Hennerich, Michael" <Michael.Hennerich@analog.com>
- 2010-07-01 · Re: [PATCH v3] input/misc: new ADXL345/346 driver · Dmitry Torokhov <dmitry.torokhov@gmail.com>
- 2010-07-01 · RE: [PATCH v3] input/misc: new ADXL345/346 driver · "Hennerich, Michael" <Michael.Hennerich@analog.com>
- 2010-07-01 · Re: [PATCH v3] input/misc: new ADXL345/346 driver · Dmitry Torokhov <dmitry.torokhov@gmail.com>
Hi Mike and Michael,
+config INPUT_ADXL34X +config INPUT_ADXL34X_I2C +config INPUT_ADXL34X_SPI
Should the INPUT_ADXL34X option be auto-selected when the _I2C or _SPI counterparts are selected? Something like: config HAVE_INPUT_ADXL34X config INPUT_ADXL34X depends on HAVE_INPUT_ADXL34X config INPUT_ADXL34X_I2C bool "..." depends on I2C select HAVE_INPUT_ADXL34X config INPUT_ADXL34X_SPI bool "..." depends on SPI_MASTER select HAVE_INPUT_ADXL34X The end user would only see the INPUT_ADXL34X_SPI and INPUT_ADXL34X_I2C options, with the common INPUT_ADXL34X option being automagically selected due to the reverse dependencies. Chris