Searched refs:driver (Results 13051 – 13071 of 13071) sorted by relevance
1...<<521522523
/openbmc/linux/drivers/net/ethernet/hisilicon/hns3/ |
H A D | hns3_enet.c | 3305 .driver.pm = &hns3_pm_ops,
|
/openbmc/linux/drivers/net/ethernet/intel/igc/ |
H A D | igc_main.c | 7326 .driver.pm = &igc_pm_ops,
|
/openbmc/linux/drivers/s390/block/ |
H A D | dasd_eckd.c | 6894 .driver = {
|
/openbmc/linux/drivers/net/ethernet/intel/e1000e/ |
H A D | netdev.c | 7945 .driver = {
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | variables.rst | 5197 touchscreen driver is required for the machine to be usable. However, 5198 the driver can be built as a module or into the kernel depending on 5199 the kernel configuration. If the driver is built as a module, you 5200 want it to be installed. But, when the driver is built into the 5263 WiFi driver is built into the kernel, in which case you still want
|
/openbmc/linux/drivers/net/wireless/cisco/ |
H A D | airo.c | 89 .driver.pm = &airo_pci_pm_ops,
|
/openbmc/linux/drivers/scsi/qla2xxx/ |
H A D | qla_os.c | 8149 .driver = {
|
/openbmc/qemu/target/i386/ |
H A D | cpu.c | 5805 prop->driver = typename; in x86_cpu_parse_featurestr()
|
/openbmc/openbmc/meta-raspberrypi/recipes-multimedia/rpidistro-ffmpeg/files/ |
H A D | 0004-ffmpeg-4.3.4-rpi_14.patch | 18499 +/* MPEG-class control IDs specific to the Hantro driver as defined by V4L2 */ 44620 + // open a char device file used for communicating with kernel mbox driver 50110 - /* no need to queue more buffers to the driver */ 50242 + /* no need to queue more buffers to the driver */ 51798 - .count = 0, /* 0 -> unmaps buffers from the driver */ 51824 + .count = 0, /* 0 -> unmap all buffers from the driver */ 52108 + // than the driver 52336 * by the V4L2 kernel driver: once set the context has to be exited. 53371 + if (strcmp(cap.driver, "meson-vdec") == 0) 53429 * the proper values will be retrieved from the kernel driver. [all …]
|
/openbmc/openbmc/poky/documentation/profile-manual/ |
H A D | usage.rst | 911 driver in user space (notice the presence of ``PVR`` and some other
|
/openbmc/linux/drivers/scsi/ |
H A D | hpsa.c | 9135 .driver.pm = &hpsa_pm_ops,
|
/openbmc/linux/drivers/scsi/smartpqi/ |
H A D | smartpqi_init.c | 10273 .driver = {
|
/openbmc/qemu/ |
H A D | meson.build | 2177 error('Audio driver "@0@" not available.'.format(k))
|
/openbmc/linux/Documentation/RCU/Design/Requirements/ |
H A D | Requirements.rst | 2189 | But what if my driver has a hardware interrupt handler that can run |
|
/openbmc/linux/drivers/scsi/mpt3sas/ |
H A D | mpt3sas_scsih.c | 12757 .driver.pm = &scsih_pm_ops,
|
/openbmc/linux/drivers/gpu/drm/amd/display/amdgpu_dm/ |
H A D | amdgpu_dm.c | 1596 init_data.driver = adev; in amdgpu_dm_init()
|
/openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/ |
H A D | 0008-Use-libtool-2.4.patch | 16032 # We need awk for the "check" target (and possibly the TAP driver). The 16053 dnl The testsuite driver may need to know about EXEEXT, so add the 16252 # We need awk for the "check" target (and possibly the TAP driver). The 21026 # We need awk for the "check" target (and possibly the TAP driver). The 21047 dnl The testsuite driver may need to know about EXEEXT, so add the 21418 # We need awk for the "check" target (and possibly the TAP driver). The
|
/openbmc/linux/drivers/scsi/lpfc/ |
H A D | lpfc_init.c | 15697 .driver.pm = &lpfc_pci_pm_ops_one,
|
/openbmc/linux/drivers/net/ethernet/broadcom/bnx2x/ |
H A D | bnx2x_main.c | 14350 .driver.pm = &bnx2x_pm_ops,
|
/openbmc/linux/drivers/net/ethernet/broadcom/bnxt/ |
H A D | bnxt.c | 14129 .driver.pm = BNXT_PM_OPS,
|
/openbmc/linux/drivers/net/ethernet/intel/i40e/ |
H A D | i40e_main.c | 16753 .driver = {
|
1...<<521522523