Home
last modified time | relevance | path

Searched refs:its (Results 1 – 25 of 1682) sorted by relevance

12345678910>>...68

/Linux-v5.4/virt/kvm/arm/vgic/
Dvgic-its.c26 static int vgic_its_save_tables_v0(struct vgic_its *its);
27 static int vgic_its_restore_tables_v0(struct vgic_its *its);
28 static int vgic_its_commit_v0(struct vgic_its *its);
164 int (*save_tables)(struct vgic_its *its);
165 int (*restore_tables)(struct vgic_its *its);
166 int (*commit)(struct vgic_its *its);
185 inline const struct vgic_its_abi *vgic_its_get_abi(struct vgic_its *its) in vgic_its_get_abi() argument
187 return &its_table_abi_versions[its->abi_rev]; in vgic_its_get_abi()
190 static int vgic_its_set_abi(struct vgic_its *its, u32 rev) in vgic_its_set_abi() argument
194 its->abi_rev = rev; in vgic_its_set_abi()
[all …]
Dvgic-v4.c251 struct vgic_its *its; in kvm_vgic_v4_set_forwarding() local
263 its = vgic_get_its(kvm, irq_entry); in kvm_vgic_v4_set_forwarding()
264 if (IS_ERR(its)) in kvm_vgic_v4_set_forwarding()
267 mutex_lock(&its->its_lock); in kvm_vgic_v4_set_forwarding()
270 ret = vgic_its_resolve_lpi(kvm, its, irq_entry->msi.devid, in kvm_vgic_v4_set_forwarding()
299 mutex_unlock(&its->its_lock); in kvm_vgic_v4_set_forwarding()
306 struct vgic_its *its; in kvm_vgic_v4_unset_forwarding() local
317 its = vgic_get_its(kvm, irq_entry); in kvm_vgic_v4_unset_forwarding()
318 if (IS_ERR(its)) in kvm_vgic_v4_unset_forwarding()
321 mutex_lock(&its->its_lock); in kvm_vgic_v4_unset_forwarding()
[all …]
/Linux-v5.4/drivers/irqchip/
Dirq-gic-v3-its.c147 struct its_node *its; member
180 struct its_node *its; in get_its_list() local
183 list_for_each_entry(its, &its_nodes, entry) { in get_its_list()
184 if (!its->is_v4) in get_its_list()
187 if (vm->vlpi_count[its->list_nr]) in get_its_list()
188 __set_bit(its->list_nr, &its_list); in get_its_list()
197 struct its_node *its = its_dev->its; in dev_event_to_col() local
199 return its->collections + its_dev->event_map.col_map[event]; in dev_event_to_col()
210 static struct its_vpe *valid_vpe(struct its_node *its, struct its_vpe *vpe) in valid_vpe() argument
212 if (valid_col(its->collections + vpe->col_idx)) in valid_vpe()
[all …]
/Linux-v5.4/arch/um/os-Linux/
Dtime.c55 struct itimerspec its; in os_timer_set_interval() local
57 its.it_value.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval()
58 its.it_value.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval()
60 its.it_interval.tv_sec = nsecs / UM_NSEC_PER_SEC; in os_timer_set_interval()
61 its.it_interval.tv_nsec = nsecs % UM_NSEC_PER_SEC; in os_timer_set_interval()
63 if (timer_settime(event_high_res_timer, 0, &its, NULL) == -1) in os_timer_set_interval()
71 struct itimerspec its = { in os_timer_one_shot() local
79 timer_settime(event_high_res_timer, 0, &its, NULL); in os_timer_one_shot()
88 struct itimerspec its; in os_timer_disable() local
90 memset(&its, 0, sizeof(struct itimerspec)); in os_timer_disable()
[all …]
/Linux-v5.4/arch/mips/generic/
DPlatform16 its-y := vmlinux.its.S
17 its-$(CONFIG_FIT_IMAGE_FDT_BOSTON) += board-boston.its.S
18 its-$(CONFIG_FIT_IMAGE_FDT_NI169445) += board-ni169445.its.S
19 its-$(CONFIG_FIT_IMAGE_FDT_OCELOT) += board-ocelot.its.S
20 its-$(CONFIG_FIT_IMAGE_FDT_XILFPGA) += board-xilfpga.its.S
/Linux-v5.4/arch/mips/boot/
DMakefile115 targets += vmlinux.its.S
120 $(obj)/vmlinux.its.S: $(addprefix $(srctree)/arch/mips/$(PLATFORM)/,$(ITS_INPUTS)) FORCE
123 targets += vmlinux.its
124 targets += vmlinux.gz.its
125 targets += vmlinux.bz2.its
126 targets += vmlinux.lzmo.its
127 targets += vmlinux.lzo.its
139 $(obj)/vmlinux.its: $(obj)/vmlinux.its.S $(VMLINUX) FORCE
142 $(obj)/vmlinux.gz.its: $(obj)/vmlinux.its.S $(VMLINUX) FORCE
145 $(obj)/vmlinux.bz2.its: $(obj)/vmlinux.its.S $(VMLINUX) FORCE
[all …]
/Linux-v5.4/arch/arm64/boot/dts/arm/
Dfoundation-v8-gicv3.dtsi22 its: its@2f020000 { label
23 compatible = "arm,gic-v3-its";
/Linux-v5.4/arch/arm/mach-imx/
DKconfig93 configurations for the board and its peripherals.
108 configurations for the board and its peripherals.
128 configurations for the board and its peripherals.
143 Include support for Visstrim_m10 platform and its different variants.
144 This includes specific configurations for the board and its
164 includes specific configurations for the module and its peripherals.
188 configurations for the board and its peripherals.
210 specific configurations for the board and its peripherals.
226 configurations for the board and its peripherals.
243 specific configurations for the board and its peripherals.
[all …]
/Linux-v5.4/include/linux/
Dtime.h75 static inline bool itimerspec64_valid(const struct itimerspec64 *its) in itimerspec64_valid() argument
77 if (!timespec64_valid(&(its->it_interval)) || in itimerspec64_valid()
78 !timespec64_valid(&(its->it_value))) in itimerspec64_valid()
/Linux-v5.4/Documentation/hwmon/
Dibmpowernv.rst19 sensor type and its attribute data.
46 disable/enable all of its temperature sensors.
59 disable/enable all of its voltage sensors.
70 disable/enable all of its power sensors.
81 disable/enable all of its current sensors.
Dlm95234.rst30 or four (LM95234) remote diodes as well as its own temperature.
40 Each sensor has its own maximum limit, but the hysteresis is common to all
45 The lm95234 driver can change its update interval to a fixed set of values.
Dlm95245.rst29 the temperature of a remote diode as well as its own temperature.
38 Each sensor has its own critical limit. Additionally, there is a relative
45 The lm95245 driver can change its update interval to a fixed set of values.
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-devices-online11 successful) its 'offline' field is updated accordingly. In
14 for the device and (if successful) its 'offline' field is
19 it is removed (i.e. device_del() is called for it), or its bus
Dsysfs-bus-fsi7 on its links.
24 Sends an FSI terminate command from the master to its
27 addition the slave freezes its internal error register for
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Drockchip,iommu.txt5 its master device. Each slave device is bound to a single master device, and
6 shares its clocks, power domain and irq.
15 to associate with its master device. See:
/Linux-v5.4/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dpar_io.txt11 - reg : offset to the register set and its length.
27 via its own gpio-controller node:
33 - reg : offset to the register set and its length.
/Linux-v5.4/Documentation/power/
Druntime_pm.rst108 the helper functions described in Section 4 for the device until its status
113 mechanism allowing the device to request a change of its power state, such as
136 4 for the device, until its status is directly set to either 'active', or
148 idle callback with the device as its argument.
266 PM core as 'suspended', regardless of its real hardware status
319 then run pm_runtime_autosuspend(dev) and return its result
373 return its result
377 return its result
390 pm_request_idle(dev) and return its result
394 pm_request_autosuspend(dev) and return its result
[all …]
/Linux-v5.4/Documentation/filesystems/nfs/
Dfault_injection.txt8 observe how the client reacts and if it manages to recover its state correctly.
42 its files.
46 Clearing this list will force the client to reclaim its locks (files are
52 force the client to reacquire its delegation before accessing the file
57 access a file. This test will notify the client that its delegation has
/Linux-v5.4/drivers/acpi/arm64/
Diort.c601 struct acpi_iort_its_group *its; in iort_dev_find_its_id() local
613 its = (struct acpi_iort_its_group *)node->node_data; in iort_dev_find_its_id()
614 if (idx >= its->its_count) { in iort_dev_find_its_id()
616 idx, its->its_count); in iort_dev_find_its_id()
620 *its_id = its->identifiers[idx]; in iort_dev_find_its_id()
649 struct acpi_iort_its_group *its; in iort_set_device_domain() local
678 its = (struct acpi_iort_its_group *)msi_parent->node_data; in iort_set_device_domain()
680 iort_fwnode = iort_find_domain_token(its->identifiers[0]); in iort_set_device_domain()
700 struct acpi_iort_its_group *its; in iort_get_platform_device_domain() local
721 its = (struct acpi_iort_its_group *)msi_parent->node_data; in iort_get_platform_device_domain()
[all …]
/Linux-v5.4/Documentation/i2c/
Di2c-topology.rst27 an i2c transfer on one of its child adapters. The mux driver can
141 2. M1 locks muxes on its parent (the root adapter in this case).
143 4. M1 (presumably) does some i2c-transfers as part of its select.
146 5. M1 feeds the i2c-transfer from step 1 to its parent adapter as a
150 8. M1 unlocks muxes on its parent.
170 child mux that the root adapter is unused between its select op
172 and the parent mux issus i2c-transfers as part of its select).
201 2. M1 locks muxes on its parent (the root adapter in this case).
202 3. M1 locks its parent adapter.
205 its select, those transfers must be unlocked i2c-transfers so
[all …]
/Linux-v5.4/Documentation/powerpc/
Dvcpudispatch_stats.txt9 from its home node).
36 6. number of times this vcpu was dispatched in its home node (chip)
64 its last dispatch.
68 outside its home node, on a neighbouring chip.
/Linux-v5.4/Documentation/filesystems/caching/
Dobject.txt96 Within FS-Cache, each active object is managed by its own individual state
106 be created or accessed with respect to its parent object.
159 preparation states in which the object sets itself up and waits for its parent
160 object to transit to a state that allows access to its children:
205 There are some normal running states in which the object spends its time
243 The object comes here if it is dying due to an error, because its parent
248 can destroy themselves. This object waits for all its children to go away
253 The object comes to this state if it was waiting on its parent in
254 FSCACHE_OBJECT_INIT, but its parent died. The object will destroy itself
261 all its children, if it is dying because the netfs relinquished its
[all …]
/Linux-v5.4/Documentation/usb/
Dgadget_configfs.rst18 A gadget is seen by its host as a set of configurations, each of which contains
62 For each gadget to be created its corresponding directory must be created::
76 Each gadget needs to have its vendor id <VID> and product id <PID> specified::
81 A gadget also needs its serial number, manufacturer and product strings.
110 Each configuration also needs its strings, so a subdirectory must be created
126 The gadget will provide some functions, for each function its corresponding
140 Each function provides its specific set of attributes, with either read-only
354 a number of its default sub-groups created automatically.
361 1. A gadget has its config group, which has some attributes (idVendor,
381 4. Each USB function naturally has its own view of what it wants
/Linux-v5.4/Documentation/ABI/removed/
Draw13946 access to FireWire buses. Its major drawbacks were its inability
7 to implement sensible device security policies, and its low level
/Linux-v5.4/Documentation/security/
Dlsm-development.rst6 a new LSM is accepted into the kernel when its intent (a description of
9 This allows an LSM's code to be easily compared to its goals, and so

12345678910>>...68