| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | fsl,mu-msi.yaml | 16 for one processor (A side) to signal the other processor (B side) using
23 registers (Processor A-side, Processor B-side).
45 - const: processor-a-side
46 - const: processor-b-side
49 description: a side interrupt number.
57 - description: a side power domain
58 - description: b side power domain
62 - const: processor-a-side
63 - const: processor-b-side
94 reg-names = "processor-a-side", "processor-b-side";
[all …]
|
| /openbmc/u-boot/drivers/ram/aspeed/ |
| H A D | Kconfig | 47 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"
69 bool "DDR4 PHY side ODT 40 ohm"
76 prompt "DDR4 DRAM side ODT"
80 bool "DDR4 DRAM side ODT 80 ohm"
86 bool "DDR4 DRAM side ODT 60 ohm"
[all …]
|
| /openbmc/linux/Documentation/locking/ |
| H A D | seqlock.rst | 15 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
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
99 side critical sections are properly serialized.
108 protection is enforced in the write side function.
154 side can be invoked from NMI handlers.
189 /* ... [[write-side critical section]] ... */
202 /* ... [[read-side critical section]] ... */
213 /* ... [[read-side critical section]] ... */
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/flash/ |
| H A D | phosphor-software-manager_git.bb | 33 ${PN}-side-switch \
47 SYSTEMD_SERVICE:${PN}-side-switch += "${@bb.utils.contains('PACKAGECONFIG', 'side_switch_on_boot', …
93 FILES:${PN}-side-switch += "\
94 ${bindir}/phosphor-bmc-side-switch \
111 pkg_postinst:${PN}-side-switch() {
114 …LINK="$D$systemd_system_unitdir/obmc-host-startmin@0.target.wants/phosphor-bmc-side-switch.service"
115 TARGET="../phosphor-bmc-side-switch.service"
119 pkg_prerm:${PN}-side-switch() {
121 …LINK="$D$systemd_system_unitdir/obmc-host-startmin@0.target.wants/phosphor-bmc-side-switch.service"
|
| /openbmc/linux/Documentation/usb/ |
| H A D | gadget_serial.rst | 57 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
111 side kernel for "Support for USB Gadgets", for a "USB Peripheral
152 instructions below to install the host side driver.
220 Linux host side kernel for "Support for Host-side USB", for "USB
263 On the gadget side run "minicom -s" to configure a new minicom
287 side and host side systems. Anything you type on the terminal
[all …]
|
| /openbmc/openbmc-test-automation/pldm/ |
| H A D | test_firmware_boot_side.robot | 3 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.
91 … Print Timen Current: ${cur_boot_side["CurrentValue"]} and set side: ${next_boot_side} are same.
|
| /openbmc/linux/drivers/char/hw_random/ |
| H A D | Kconfig | 28 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/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | rockchip,rk3399-dmc.yaml | 132 the ODT on the DRAM side and controller side are both disabled.
138 When the DRAM type is DDR3, this parameter defines the DRAM side drive
146 When the DRAM type is DDR3, this parameter defines the DRAM side ODT
154 When the DRAM type is DDR3, this parameter defines the phy side CA line
162 When the DRAM type is DDR3, this parameter defines the PHY side DQ line
170 When the DRAM type is DDR3, this parameter defines the PHY side ODT
180 ODT on the DRAM side and controller side are both disabled.
194 When the DRAM type is LPDDR3, this parameter defines the DRAM side ODT
218 When dram type is LPDDR3, this parameter define the phy side odt
227 the ODT on the DRAM side and controller side are both disabled.
[all …]
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | lockdep.rst | 8 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 D | checklist.rst | 18 tool for the job. Yes, RCU does reduce read-side overhead by
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
158 perfectly legal (if redundant) for update-side code to
163 of an RCU read-side critical section. See lockdep.rst
194 be traversed by an RCU read-side critical section.
338 locks. RCU read-side critical sections are delimited by
431 requiring SRCU's read-side deadlock immunity or low read-side
465 RCU update-side primitives to deal with this.
[all …]
|
| /openbmc/u-boot/board/BuS/eb_cpu5282/ |
| H A D | eb_cpu5282.c | 230 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/qemu/docs/devel/ |
| H A D | rcu.txt | 6 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
68 entering an RCU read-side critical section.
73 exiting an RCU read-side critical section. Note that RCU
255 read-side critical section in progress, the RCU read-side primitives
286 The write side can be like this:
306 last reference may be dropped on the read side. Hence you can
338 out of the write-side critical section.
376 read side:
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-frequency-admv1013 | 18 side.
24 Read/write value for the Local Oscillatior Feedthrough Offset Calibration Q Positive side.
31 side.
38 side.
|
| /openbmc/linux/drivers/block/rnbd/ |
| H A D | README | 12 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/litmus-tests/rcu/ |
| H A D | RCU+sync+read.litmus | 7 * 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/lib/ |
| H A D | bios_attr_utils.robot | 87 [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/openbmc-test-automation/redfish/extended/ |
| H A D | test_bmc_file_mirroring.robot | 3 ... 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 D | bus_vcxk.c | 98 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 D | README.i2c | 5 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/phosphor-bmc-code-mgmt/side-switch/ |
| H A D | meson.build | 7 'phosphor-bmc-side-switch',
22 'phosphor-bmc-side-switch.service',
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 20 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
370 outermost RCU read-side critical section containing that
429 update-side lock.
698 Reader-side markers such as rcu_read_lock() and
1077 b. Wait-free read-side primitives for real-time use.
1194 unsurprising. For example, in keeping with RCU's read-side
1564 small read-side delays can occur when using
1590 critical section. Update-side code can use
1749 set up. The read-side primitives (rcu_read_lock(),
[all …]
|
| /openbmc/linux/include/uapi/linux/netfilter/ |
| H A D | xt_recent.h | 34 __u8 side; member
43 __u8 side; member
|
| /openbmc/linux/drivers/char/ipmi/ |
| H A D | Kconfig | 118 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/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
| H A D | libxau_1.0.11.bb | 5 both client-side and server-side."
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | io-mapping.rst | 49 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
|