Searched refs:coarse (Results 1 – 6 of 6) sorted by relevance
/linux-4.4.14/drivers/media/usb/gspca/stv06xx/ |
D | stv06xx_vv6410.c | 255 unsigned int fine, coarse; in vv6410_set_exposure() local 260 coarse = min(512, val / VV6410_CIF_LINELENGTH); in vv6410_set_exposure() 263 coarse, fine); in vv6410_set_exposure() 273 err = stv06xx_write_sensor(sd, VV6410_COARSEH, coarse >> 8); in vv6410_set_exposure() 277 err = stv06xx_write_sensor(sd, VV6410_COARSEL, coarse & 0xff); in vv6410_set_exposure()
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | fake-numa-for-cpusets | 5 in conjunction with cpusets for coarse memory management. Using this feature, 64 This allows for coarse memory management for the tasks you assign to particular
|
/linux-4.4.14/drivers/net/ethernet/intel/e1000/ |
D | e1000_hw.c | 204 u16 fused, fine, coarse; in e1000_phy_init_script() local 217 coarse = in e1000_phy_init_script() 220 if (coarse > in e1000_phy_init_script() 222 coarse -= in e1000_phy_init_script() 225 } else if (coarse == in e1000_phy_init_script() 232 (coarse & in e1000_phy_init_script()
|
/linux-4.4.14/Documentation/trace/ |
D | tracepoint-analysis.txt | 231 very coarse as a result.
|
/linux-4.4.14/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 146 ioctl restartable relative timeouts tend to be too coarse and can
|
/linux-4.4.14/Documentation/hwmon/ |
D | w83781d | 402 found out the following values do work as a form of coarse pwm:
|