summaryrefslogtreecommitdiff
path: root/arch/um/Kconfig.common
diff options
context:
space:
mode:
authorDaniel Scheller <d.scheller@gmx.net>2018-02-25 15:31:37 +0300
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2018-03-06 19:15:01 +0300
commite39b8e945eb749d3bef21b38309f84de8f7a3007 (patch)
treeacb371ae4e8b557737c15a5ea008b79c78387c41 /arch/um/Kconfig.common
parentee93340e98bc9026dedf6e7483f9f092d1765582 (diff)
downloadlinux-e39b8e945eb749d3bef21b38309f84de8f7a3007.tar.xz
media: ngene: check for CXD2099AR presence before attaching
Currently, if there's no CXD2099AR attached to any expansion connector of the ngene hardware, it will complain with this on every module load: cxd2099 1-0040: No CXD2099AR detected at 0x40 cxd2099: probe of 1-0040 failed with error -5 ngene 0000:02:00.0: CXD2099AR attach failed This happens due to the logic assuming such hardware is always there and blindly tries to attach the cxd2099 I2C driver. Rather add a probe function (in ngene-cards.c with a prototype in ngene.h) to check for the existence of such hardware before probing, and don't try further if no CXD2099 was found. Signed-off-by: Daniel Scheller <d.scheller@gmx.net> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'arch/um/Kconfig.common')
0 files changed, 0 insertions, 0 deletions