summaryrefslogtreecommitdiffstats
path: root/drivers/input/mouse
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>2015-05-21 16:07:37 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2015-05-21 16:58:02 -0700
commit3a38958d2477b718d1011fb88c24c4f264ee9700 (patch)
tree832cafd790b27d0b8c170ba411560d439b054d51 /drivers/input/mouse
parente465bf6fc55d5ce21fb45a75c3fa613505e6be20 (diff)
downloadop-kernel-dev-3a38958d2477b718d1011fb88c24c4f264ee9700.zip
op-kernel-dev-3a38958d2477b718d1011fb88c24c4f264ee9700.tar.gz
Input: adxl34x - add OF match support
The I2C subsystem can match devices without explicit OF support based on the part of their compatible property after the comma. However, this mechanism uses the first compatible value only. For adxl34x OF device nodes the compatible property will contain the more specific "adi,adxl345" or "adi,adxl346" value first. This prevents the device node from being matched with the adxl34x driver. Fix this by adding an OF match table with an "adi,adxl345" compatible entry. There's no need to add the "adi,adxl346" entry as the ADXL346 is backward-compatible with the ADXL345 with differences handled by runtime detection of the device model. Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/mouse')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud