1# SPDX-License-Identifier: GPL-2.0-only 2config VIDEO_IVTV 3 tristate "Conexant cx23416/cx23415 MPEG encoder/decoder support" 4 depends on VIDEO_DEV && PCI && I2C 5 select I2C_ALGOBIT 6 depends on RC_CORE 7 select VIDEO_TUNER 8 select VIDEO_TVEEPROM 9 select VIDEO_CX2341X 10 select VIDEO_CX25840 11 select VIDEO_MSP3400 12 select VIDEO_SAA711X 13 select VIDEO_SAA717X 14 select VIDEO_SAA7127 15 select VIDEO_CS53L32A 16 select VIDEO_M52790 17 select VIDEO_WM8775 18 select VIDEO_WM8739 19 select VIDEO_VP27SMPX 20 select VIDEO_UPD64031A 21 select VIDEO_UPD64083 22 help 23 This is a video4linux driver for Conexant cx23416 or cx23415 based 24 PCI personal video recorder devices. 25 26 This is used in devices such as the Hauppauge PVR-150/250/350/500 27 cards. 28 29 To compile this driver as a module, choose M here: the 30 module will be called ivtv. 31 32config VIDEO_IVTV_ALSA 33 tristate "Conexant cx23415/cx23416 ALSA interface for PCM audio capture" 34 depends on VIDEO_IVTV && SND 35 select SND_PCM 36 help 37 This driver provides an ALSA interface as another method for user 38 applications to obtain PCM audio data from Conexant cx23415/cx23416 39 based PCI TV cards supported by the ivtv driver. 40 41 The ALSA interface has much wider use in user applications performing 42 PCM audio capture, than the V4L2 "/dev/video24" PCM audio interface 43 provided by the main ivtv driver. 44 45 To compile this driver as a module, choose M here: the 46 module will be called ivtv-alsa. 47 48config VIDEO_FB_IVTV 49 tristate "Conexant cx23415 framebuffer support" 50 depends on VIDEO_IVTV && FB 51 select FB_IOMEM_HELPERS 52 help 53 This is a framebuffer driver for the Conexant cx23415 MPEG 54 encoder/decoder. 55 56 This is used in the Hauppauge PVR-350 card. 57 58 To compile this driver as a module, choose M here: the 59 module will be called ivtvfb. 60 61config VIDEO_FB_IVTV_FORCE_PAT 62 bool "force cx23415 framebuffer init with x86 PAT enabled" 63 depends on VIDEO_FB_IVTV && X86_PAT 64 help 65 With PAT enabled, the cx23415 framebuffer driver does not 66 utilize write-combined caching on the framebuffer memory. 67 For this reason, the driver will by default disable itself 68 when initializied on a kernel with PAT enabled (i.e. not 69 using the nopat kernel parameter). 70 71 The driver is not easily upgradable to the PAT-aware 72 ioremap_wc() API since the firmware hides the address 73 ranges that should be marked write-combined from the driver. 74 75 With this setting enabled, the framebuffer will initialize on 76 PAT-enabled systems but the framebuffer memory will be uncached. 77 78 If unsure, say N. 79