Home
last modified time | relevance | path

Searched refs:side (Results 1 – 25 of 747) sorted by relevance

12345678910>>...30

/openbmc/u-boot/drivers/ram/aspeed/
H A DKconfig47 prompt "DDR4 PHY side ODT"
51 bool "DDR4 PHY side ODT 80 ohm"
54 select DDR4 PHY side ODT 80 ohm
57 bool "DDR4 PHY side ODT 60 ohm"
60 select DDR4 PHY side ODT 60 ohm
63 bool "DDR4 PHY side ODT 48 ohm"
66 select DDR4 PHY side ODT 48 ohm
69 bool "DDR4 PHY side ODT 40 ohm"
72 select DDR4 PHY side ODT 40 ohm
76 prompt "DDR4 DRAM side ODT"
[all …]
/openbmc/linux/Documentation/locking/
H A Dseqlock.rst15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
28 or interrupted by read side sections. Otherwise the reader will spin for
43 multiple writers. Write side critical sections must thus be serialized
48 write side section. If the read section can be invoked from hardirq or
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
95 As discussed at :ref:`seqcount_t`, sequence count write side critical
[all …]
/openbmc/linux/Documentation/usb/
H A Dgadget_serial.rst57 side driver. It runs on a Linux system that has USB device side
84 On the device-side Linux system, the gadget serial driver looks
87 On the host-side system, the gadget serial device looks like a
92 The host side driver can potentially be any ACM compliant driver
98 With the gadget serial driver and the host side ACM or generic
100 the host and the gadget side systems as if they were connected by a
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
128 side Linux system. You can add this to the start up scripts, if
149 either the Windows or Linux ACM driver on the host side. If gadget
151 Linux generic serial driver on the host side. Follow the appropriate
[all …]
/openbmc/linux/drivers/char/hw_random/
H A DKconfig28 This driver provides kernel-side support for a generic Random
43 This driver provides kernel-side support for the Random Number
57 This driver provides kernel-side support for the Random Number
70 This driver provides kernel-side support for the Random Number
82 This driver provides kernel-side support for the Random Number
94 This driver provides kernel-side support for the Random Number
107 This driver provides kernel-side support for the RNG200
121 This driver provides kernel-side support for the Random Number
134 This driver provides kernel-side support for the Random Number
147 This driver provides kernel-side support for the Random Number
[all …]
/openbmc/openbmc/meta-phosphor/recipes-phosphor/flash/
H A Dphosphor-software-manager_git.bb34 ${PN}-side-switch \
48 SYSTEMD_SERVICE:${PN}-side-switch += "${@bb.utils.contains('PACKAGECONFIG', 'side_switch_on_boot', …
94 FILES:${PN}-side-switch += "\
95 ${bindir}/phosphor-bmc-side-switch \
113 pkg_postinst:${PN}-side-switch() {
116 …LINK="$D$systemd_system_unitdir/obmc-host-startmin@0.target.wants/phosphor-bmc-side-switch.service"
117 TARGET="../phosphor-bmc-side-switch.service"
121 pkg_prerm:${PN}-side-switch() {
123 …LINK="$D$systemd_system_unitdir/obmc-host-startmin@0.target.wants/phosphor-bmc-side-switch.service"
/openbmc/openbmc-test-automation/pldm/
H A Dtest_firmware_boot_side.robot3 Documentation Test firmware boot side switch using pldmtool.
7 # 2. Check the firmware boot side ( login to BMC and execute )
12 # 3. Set the firmware boot side to Temp or Perm accordingly
19 # 7. Verify the boot side is still same which was set.
33 # By default 2, to ensure, it performs both Perm and Temp side switch and boot.
42 [Documentation] Power off the host , set the firmware boot side via pldmtool,
55 [Documentation] Number of iteration, test should perform switch side and boot.
92 … Print Timen Current: ${cur_boot_side["CurrentValue"]} and set side: ${next_boot_side} are same.
/openbmc/qemu/docs/devel/
H A Drcu.rst6 on the read side (it is wait-free), and thus can make the read paths
10 thus it is not used alone. Typically, the write-side will use a lock to
17 RCU is fundamentally a "wait-to-finish" mechanism. The read side marks
18 sections of code with "critical sections", and the update side will wait
67 entering an RCU read-side critical section.
71 exiting an RCU read-side critical section. Note that RCU
72 read-side critical sections may be nested and/or overlapping.
75 Blocks until all pre-existing RCU read-side critical sections
87 read-side critical sections on all threads have completed. This
135 case when using RCU, because read-side critical sections typically
[all …]
/openbmc/linux/Documentation/RCU/
H A Dlockdep.rst8 aware of when each task enters and leaves any flavor of RCU read-side
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
83 1. An RCU read-side critical section (implicit), or
88 RCU read-side critical sections, in case (2) the ->file_lock prevents
99 complain even if this was used in an RCU read-side critical section unless
107 traversal primitives check for being called from within an RCU read-side
111 false and they are called from outside any RCU read-side critical section.
[all …]
H A Dchecklist.rst18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
28 read-side primitives is critically important.
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
68 rcu_read_lock_sched(), or by the appropriate update-side lock.
77 Letting RCU-protected pointers "leak" out of an RCU read-side
81 *before* letting them out of the RCU read-side critical section.
158 perfectly legal (if redundant) for update-side code to
163 of an RCU read-side critical section. See lockdep.rst
[all …]
H A DwhatisRCU.rst103 b. Wait for all previous readers to complete their RCU read-side
166 reclaimer that the reader is entering an RCU read-side critical
167 section. It is illegal to block while in an RCU read-side
169 can preempt RCU read-side critical sections. Any RCU-protected
170 data structure accessed during an RCU read-side critical section
180 reclaimer that the reader is exiting an RCU read-side critical
181 section. Note that RCU read-side critical sections may be nested
190 all pre-existing RCU read-side critical sections on all CPUs
192 necessarily wait for any subsequent RCU read-side critical
206 read-side critical sections to complete, not necessarily for
[all …]
H A Dlockdep-splat.rst15 RCU read-side critical section or (2) holding the right update-side lock.
72 This form says that it must be in a plain vanilla RCU read-side critical
84 code was invoked either from within an RCU read-side critical section
89 On the other hand, perhaps we really do need an RCU read-side critical
104 read-side critical section, which again would have suppressed the
/openbmc/u-boot/board/BuS/eb_cpu5282/
H A Deb_cpu5282.c230 ulong side; in do_brightness() local
235 side = simple_strtoul(argv[1], NULL, 10); in do_brightness()
237 if ((side >= 0) && (side <= 3) && in do_brightness()
239 vcxk_setbrightness(side, bright); in do_brightness()
/openbmc/linux/drivers/block/rnbd/
H A DREADME12 on the client side as local block devices.
26 Server side:
29 Client side:
39 mapped from the server side. After the session to the server machine is
40 established, the mapped device will appear on the client side under
51 to the block device on the server side by concatenating dev_search_path
73 information: side, max_hw_sectors, etc.
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-frequency-admv101318 side.
24 Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side.
31 side.
38 side.
/openbmc/openbmc-test-automation/lib/
H A Dbios_attr_utils.robot87 [Documentation] Switch BIOS attribute firmware boot side value to Perm/Temp
88 ... at host power off state and verify firmware boot side
93 # set_fw_boot_side Firmware boot side optional value Perm/Temp.
106 Log To Console Current firmware boot side :: ${cur_boot_side["fw_boot_side"]}
107 Log To Console Given firmware boot side :: ${set_fw_boot_side}
112 # Set the given firmware boot side value.
128 # Verify firmware boot side values after BMC reboot.
/openbmc/linux/Documentation/litmus-tests/rcu/
H A DRCU+sync+read.litmus7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
11 * other things) that an RCU read-side critical section cannot span a grace period.
/openbmc/openbmc-test-automation/redfish/extended/
H A Dtest_bmc_file_mirroring.robot3 ... alternate flash chip side.
15 [Documentation] Verify the modified file is synced to alt flash side.
49 # Wait time for syncing to ALT side.
56 ... msg=hostname primary file is not synced to the alt flash chip side.
/openbmc/u-boot/drivers/video/
H A Dbus_vcxk.c98 void vcxk_setbrightness(unsigned int side, short brightness);
271 void vcxk_setbrightness(unsigned int side, short brightness) in vcxk_setbrightness() argument
274 if ((side == 0) || (side & 0x1)) in vcxk_setbrightness()
276 if ((side == 0) || (side & 0x2)) in vcxk_setbrightness()
/openbmc/u-boot/doc/
H A DREADME.i2c5 The implementation on the master side in software is quite complex.
16 reboots by either side without difficulty.
32 sure that the other side doesn't want it also. A detailed explanation is best
38 2. Waits a little bit for the other side to notice (slew time)
46 7. Panic. The other side is hung with the CLAIM line set.
60 wait for access to the bus assuming that the other side isn't using it.
/openbmc/linux/Documentation/RCU/Design/Requirements/
H A DRequirements.rst20 updaters do not block readers, which means that RCU's read-side
74 of all pre-existing RCU read-side critical sections. An RCU read-side
77 RCU treats a nested set as one big RCU read-side critical section.
131 | Second, even when using synchronize_rcu(), the other update-side |
173 The RCU read-side critical section in do_something_dlm() works with
190 In order to avoid fatal problems such as deadlocks, an RCU read-side
192 Similarly, an RCU read-side critical section must not contain anything
198 be good to be able to use RCU to coordinate read-side access to linked
370 outermost RCU read-side critical section containing that
387 #. Wait for all pre-existing RCU read-side critical sections to complete
[all …]
/openbmc/linux/drivers/char/ipmi/
H A DKconfig118 The driver implements the BMC side of the KCS contorller, it
119 provides the access of KCS IO space for BMC side.
130 The driver implements the BMC side of the KCS contorller, it
131 provides the access of KCS IO space for BMC side.
140 Provides a BMC-side character device implementing IPMI
167 Provides a BMC-side character device directly exposing the
188 implements the BMC side of the BT interface.
195 management (BMC) side.
197 The driver implements the BMC side of the SMBus system
/openbmc/linux/Documentation/driver-api/
H A Dio-mapping.rst49 io_mapping_map_local_wc() has a side effect on X86 32bit as it disables
50 migration to make the mapping code work. No caller can rely on this side
53 io_mapping_map_atomic_wc() has the side effect of disabling preemption and
72 undoes the side effects of the mapping functions.
80 This works like io_mapping_map_atomic/local_wc() except it has no side
/openbmc/phosphor-bmc-code-mgmt/bmc/side-switch/
H A Dmeson.build4 'phosphor-bmc-side-switch',
18 'phosphor-bmc-side-switch.service',
/openbmc/linux/include/uapi/linux/netfilter/
H A Dxt_recent.h34 __u8 side; member
43 __u8 side; member
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/
H A Dlibxau_1.0.12.bb5 both client-side and server-side."

12345678910>>...30