Home
last modified time | relevance | path

Searched refs:wants (Results 1 – 25 of 357) sorted by relevance

12345678910>>...15

/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvstreams/
H A Dgcc-6.patch14 - si.wants.readable = readcb;
15 - si.wants.writable = writecb;
16 - si.wants.isexception = exceptcb;
17 + si.wants.readable = static_cast<bool>(readcb);
18 + si.wants.writable = static_cast<bool>(writecb);
19 + si.wants.isexception = static_cast<bool>(exceptcb);
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-platform-chipidea-usb-otg7 the application running on the A-device wants to use the bus,
8 and to be 0 when the application no longer wants to use
9 the bus(or wants to work as peripheral). a_bus_req can also
24 application running on the A-device wants to power down
39 that the application running on the B-device wants to use the
40 bus as host, and is 0 when the application no longer wants to
H A Dsysfs-driver-w1_therm13 Users: any user space application which wants to communicate with
29 Users: any user space application which wants to communicate with
43 Users: any user space application which wants to communicate with
65 Users: any user space application which wants to communicate with
86 Users: any user space application which wants to communicate with
107 Users: any user space application which wants to communicate with
135 Users: any user space application which wants to communicate with
H A Dsysfs-driver-jz4780-efuse19 Users: any user space application which wants to read the Chip
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/clock/
H A Dux500.txt15 clock in the prcmu-clock node the consumer wants to use.
19 wants to use, possible values are 1, 2, 3, 5, 6. The second
20 cell indicates which clock inside the PRCC block it wants,
25 wants to use, possible values are 1, 2, 3, 5, 6. The second
26 cell indicates which clock inside the PRCC block it wants,
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/dbus/
H A Ddbus_1.14.6.bb95 ${systemd_system_unitdir}/sockets.target.wants \
97 ${systemd_user_unitdir}/sockets.target.wants \
140 for i in dbus.target.wants sockets.target.wants multi-user.target.wants; do \
143 ln -fs ../dbus.socket ${D}${systemd_system_unitdir}/dbus.target.wants/dbus.socket
144 ln -fs ../dbus.socket ${D}${systemd_system_unitdir}/sockets.target.wants/dbus.socket
145 ln -fs ../dbus.service ${D}${systemd_system_unitdir}/multi-user.target.wants/dbus.service
/OK3568_Linux_fs/yocto/poky/meta/recipes-graphics/waffle/
H A Dwaffle_1.7.0.bb33 # I say virtual/libgl, actually wants gl.pc
36 # wants wayland-egl.pc, egl.pc, and the wayland
40 # wants gbm.pc egl.pc
43 # wants egl.pc
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/systemd/
H A Dsystemd-serialgetty.bb23 install -d ${D}${sysconfdir}/systemd/system/getty.target.wants/
35 ${D}${sysconfdir}/systemd/system/getty.target.wants/serial-getty@$ttydev.service
42 ${D}${sysconfdir}/systemd/system/getty.target.wants/serial-getty$baudrate@$ttydev.service
H A Dsystemd_250.5.bb285 install -d ${D}${systemd_system_unitdir}/graphical.target.wants
286 install -d ${D}${systemd_system_unitdir}/multi-user.target.wants
287 install -d ${D}${systemd_system_unitdir}/poweroff.target.wants
288 install -d ${D}${systemd_system_unitdir}/reboot.target.wants
289 install -d ${D}${systemd_system_unitdir}/rescue.target.wants
293 …date-utmp-runlevel.service ${D}${systemd_system_unitdir}/graphical.target.wants/systemd-update-utm…
294 …ate-utmp-runlevel.service ${D}${systemd_system_unitdir}/multi-user.target.wants/systemd-update-utm…
295 …pdate-utmp-runlevel.service ${D}${systemd_system_unitdir}/poweroff.target.wants/systemd-update-utm…
296 …ln -sf ../systemd-update-utmp-runlevel.service ${D}${systemd_system_unitdir}/reboot.target.wants/s…
297 …ln -sf ../systemd-update-utmp-runlevel.service ${D}${systemd_system_unitdir}/rescue.target.wants/s…
[all …]
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.i2c28 - AP_CLAIM: output from AP, signalling to the EC that the AP wants the bus
29 - EC_CLAIM: output from EC, signalling to the AP that the EC wants the bus
35 Let's say the AP wants to claim the bus. It:
57 In general the traffic is fairly light, and in particular the EC wants access
/OK3568_Linux_fs/kernel/Documentation/ABI/stable/
H A Dsysfs-driver-w1_ds28e046 Users: any user space application which wants to communicate with DS28E04-100
15 Users: any user space application which wants to communicate with DS28E04-100
H A Dsysfs-driver-w1_ds28ea006 Users: any user space application which wants to communicate with DS28EA00
H A Dsysfs-bus-w111 Users: any user space application which wants to know bus scanning
/OK3568_Linux_fs/buildroot/package/restorecond/
H A Drestorecond.mk38 mkdir -p $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants
40 $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants/restorecond.service
/OK3568_Linux_fs/yocto/poky/meta/recipes-connectivity/nfs-utils/nfs-utils/
H A Dbugfix-adjust-statd-service-name.patch35 - systemctl add-wants --runtime remote-fs.target rpc-statd.service
36 + systemctl add-wants --runtime remote-fs.target nfs-statd.service
/OK3568_Linux_fs/kernel/drivers/gpu/vga/
H A Dvgaarb.c245 unsigned int wants, legacy_wants, match; in __vga_tryget() local
264 wants = rsrc & ~vgadev->owns; in __vga_tryget()
267 if (wants == 0) in __vga_tryget()
273 legacy_wants = wants & VGA_RSRC_LEGACY_MASK; in __vga_tryget()
363 if (wants & (VGA_RSRC_LEGACY_MEM|VGA_RSRC_NORMAL_MEM)) in __vga_tryget()
365 if (wants & (VGA_RSRC_LEGACY_IO|VGA_RSRC_NORMAL_IO)) in __vga_tryget()
368 if (wants & VGA_RSRC_LEGACY_MASK) in __vga_tryget()
376 vgadev->owns |= wants; in __vga_tryget()
/OK3568_Linux_fs/kernel/Documentation/arm/samsung-s3c24xx/
H A Dcpufreq.rst28 and anything else associated with it. Any board that wants to use this
61 Each board that wants to use the cpufreq code must register some basic
/OK3568_Linux_fs/yocto/poky/meta/recipes-core/systemd/systemd/
H A D0001-binfmt-Don-t-install-dependency-links-at-install-tim.patch37 - 'sysinit.target.wants/'],
47 - 'sysinit.target.wants/'],
/OK3568_Linux_fs/kernel/Documentation/block/
H A Dinline-encryption.rst61 knowledge of keyslots - it simply wants to specify an encryption context to
67 upper layers. The generic mode of operation is: each device driver that wants
153 the block layer wants en/decrypted via inline encryption (or the
162 wants to use an algorithm that may not supported by hardware - this function
196 (e.g. when it wants to program a crypto key into the IE hardware, the device
215 functionality they choose. When a layered device wants to pass a clone of that
241 when a WRITE bio wants to use inline encryption on a device that supports both
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/syslog-ng/
H A Dsyslog-ng_3.36.1.bb106 install -d ${D}${systemd_unitdir}/system/multi-user.target.wants
107 …ln -sf ../${BPN}@.service ${D}${systemd_unitdir}/system/multi-user.target.wants/${BPN}@default.ser…
115 …}/include/scl/ ${datadir}/xsd ${datadir}/tools ${systemd_unitdir}/system/multi-user.target.wants/*"
/OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/recipes-multimedia/packagegroups/
H A Dpackagegroup-xfce-multimedia.bb9 # that wants mpd which does
/OK3568_Linux_fs/kernel/drivers/staging/fieldbus/Documentation/
H A Dfieldbus_dev.txt35 They are typically used when a Linux device wants to expose itself as an
45 Any driver that wants to register as a Fieldbus Device should allocate and
/OK3568_Linux_fs/kernel/Documentation/staging/
H A Drpmsg.rst74 The caller should specify the channel, the data it wants to send,
95 The caller should specify the channel, the data it wants to send,
120 The caller should specify the channel, the data it wants to send,
140 The caller should specify the channel, the data it wants to send,
159 The user should specify the channel, the data it wants to send,
181 The user should specify the channel, the data it wants to send,
/OK3568_Linux_fs/kernel/drivers/staging/fieldbus/
H A DKconfig10 They are typically used when a Linux device wants to expose itself
/OK3568_Linux_fs/device/rockchip/common/post-hooks/
H A D06-async-commit.sh10 etc/systemd/system/multi-user.target.wants/async.service \

12345678910>>...15