Home
last modified time | relevance | path

Searched refs:registration (Results 1 – 25 of 165) sorted by relevance

1234567

/openbmc/linux/drivers/misc/sgi-xp/
H A Dxp_main.c153 if (registration->func != NULL) { in xpc_connect()
163 registration->key = key; in xpc_connect()
164 registration->func = func; in xpc_connect()
202 mutex_lock(&registration->mutex); in xpc_disconnect()
205 if (registration->func == NULL) { in xpc_disconnect()
211 registration->func = NULL; in xpc_disconnect()
212 registration->key = NULL; in xpc_disconnect()
213 registration->nentries = 0; in xpc_disconnect()
214 registration->entry_size = 0; in xpc_disconnect()
215 registration->assigned_limit = 0; in xpc_disconnect()
[all …]
H A Dxpc_channel.c470 if (mutex_trylock(&registration->mutex) == 0) in xpc_connect_channel()
474 mutex_unlock(&registration->mutex); in xpc_connect_channel()
485 mutex_unlock(&registration->mutex); in xpc_connect_channel()
497 ch->func = registration->func; in xpc_connect_channel()
498 DBUG_ON(registration->func == NULL); in xpc_connect_channel()
499 ch->key = registration->key; in xpc_connect_channel()
501 ch->local_nentries = registration->nentries; in xpc_connect_channel()
504 if (registration->entry_size != ch->entry_size) { in xpc_connect_channel()
516 mutex_unlock(&registration->mutex); in xpc_connect_channel()
523 ch->entry_size = registration->entry_size; in xpc_connect_channel()
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sblim-sfcb/sblim-sfcb/
H A Dsblim-sfcb-1.3.16-maxMsgLen.patch15 ## Location of the registration directory, where providerRegister can be found
16 ## Default is @localstatedir@/lib/sfcb/registration
H A Dsblim-sfcb-1.3.9-sfcbrepos-schema-location.patch14 Path to sfcb staging area containing class MOFs and registration files
23 \fI@localstatedir@/lib/sfcb/registration/providerRegister\fR
30 echo -e "\t-r specify repository directory [@localstatedir@/lib/sfcb/registration]"
H A Dsblim-sfcb-1.4.5-service.patch19 …test -d $(DESTDIR)$(sfcbstatedir)/registration/repository || $(mkdir_p) $(DESTDIR)$(sfcbstatedir)/…
/openbmc/qemu/docs/devel/
H A Dci-runners.rst.inc64 gitlab-runner setup and registration
69 happens with a registration token. To find the registration token for
77 "And this registration token:"
89 Following the registration, it's necessary to configure the runner tags,
/openbmc/linux/drivers/md/bcache/
H A DKconfig32 bool "Asynchronous device registration"
37 registration work is handled in kernel work queue in asynchronous
/openbmc/linux/Documentation/driver-api/thermal/
H A Dcpu-cooling-api.rst14 The generic cpu cooling(freq clipping) provides registration/unregistration APIs
16 the user. The registration APIs returns the cooling device pointer.
21 1.1 cpufreq registration/unregistration APIs
61 The power API registration functions provide a simple power model for
/openbmc/linux/Documentation/infiniband/
H A Duser_mad.rst18 descriptor for the appropriate device file. If the registration
34 a new registration ioctl is now provided which allows additional
35 fields to be provided during registration.
36 Users of this registration call are implicitly setting the use of
100 mad->hdr.id = my_agent; /* req.id from agent registration */
/openbmc/qemu/scripts/ci/setup/
H A Dgitlab-runner.yml18 msg: 'Checking for a valid GitLab registration token'
77 …ner register --non-interactive --url {{ gitlab_runner_server_url }} --registration-token {{ gitlab…
81 …ner register --non-interactive --url {{ gitlab_runner_server_url }} --registration-token {{ gitlab…
/openbmc/openbmc/meta-google/recipes-phosphor/ipmi/
H A Dphosphor-ipmi-ethstats_%.bbappend1 # Enable registration via Google OEM Number in addition to OpenBMC.
/openbmc/qemu/docs/
H A Drdma.txt61 Experimental: Next, decide if you want dynamic page registration.
117 EFFECTS of memory registration on bulk phase round:
156 1. registration of the memory that will be transmitted
212 7. Compress page (zap zero page and skip registration)
213 8. Register request (dynamic chunk registration)
273 be sent with RDMA, the registration commands are used to ask the
275 with the result (rkey) of the registration.
280 using chunk registration (or not checked at all and unconditionally
281 written if chunk registration is disabled. This is accomplished using
313 (like dynamic page registration).
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dconfigfs-usb-gadget-phonet8 network device registration.
/openbmc/linux/Documentation/networking/
H A Dnetdevices.rst38 In that case the struct net_device registration is done using
77 registration.
158 netdev state after allocating it and before registration.
167 or when register_netdevice() fails. Parts of netdev (de)registration process
178 registration and de-registration, under ``rtnl_lock``. Drivers can use
/openbmc/linux/Documentation/driver-api/80211/
H A Dcfg80211.rst8 Device registration
12 :doc: Device registration
/openbmc/linux/Documentation/driver-api/surface_aggregator/clients/
H A Dsan.rst22 registration and notifier-block registration.
/openbmc/linux/Documentation/driver-api/usb/
H A Dtypec.rst15 class. In a normal case the registration will be done by a USB Type-C or PD PHY
81 registration. The class offers the following API for registering/unregistering
87 The class will provide a handle to struct typec_partner if the registration was
111 followed by registration of the cable plugs. The cable will be the parent device
114 the details during registration. The class offers the following API for
121 the registration is successful, or NULL if it isn't.
172 own functions, but the registration will always return a handle to struct
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/
H A Dparselogs-ignores-qemuarm64.txt4 dmi: Firmware registration failed.
/openbmc/linux/Documentation/crypto/
H A Ddevel-algos.rst7 There are three distinct types of registration functions in the Crypto
17 The generic registration functions can be found in
38 The registration functions return 0 on success, or a negative errno
60 The registration of [CIPHER] algorithm is specific in that struct
111 The registration of multi-block cipher algorithms is one of the most
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-pydbus/
H A D0003-Support-transformation-between-D-Bus-errors-and-exce.patch19 pydbus/registration.py | 16 ++++--
187 +# Default error registration.
233 diff --git a/pydbus/registration.py b/pydbus/registration.py
235 --- a/pydbus/registration.py
236 +++ b/pydbus/registration.py
353 +logger = logging.getLogger('pydbus.registration')
/openbmc/openbmc/poky/meta/recipes-kernel/systemtap/systemtap/
H A D0001-prerelease-datestamp-fixes.patch19 - Performance improvements in uprobe registration and module startup.
/openbmc/linux/Documentation/i2c/muxes/
H A Di2c-mux-gpio.rst69 If you don't know the absolute GPIO pin numbers at registration time,
85 GPIO pin numbers at registration time, this is even the only option.
/openbmc/openbmc/poky/meta/classes-recipe/
H A Dgconf.bbclass13 # registration (disabled below) nor the postinst script (as they don't happen).
17 # Disable install-time schema registration as we're a packaging system so this
/openbmc/linux/Documentation/driver-api/tty/
H A Dtty_driver.rst78 The registration routines are documented as follows:
92 tty_register_device() and tty_register_device_attr() at the registration time.
96 index *before* the actual registration by tty_port_link_device(). If it still
/openbmc/linux/Documentation/trace/
H A Duser_events.rst18 tools that can read trace_events (such as ftrace and perf). The registration
20 enabled the event and data should be written. The registration will give back
83 Upon successful registration the following is set.
87 descriptor that was used for the registration. See writing data for details.
141 to request deletes than the one used for registration due to this.

1234567