Home
last modified time | relevance | path

Searched full:physical (Results 1 – 25 of 4748) sorted by relevance

12345678910>>...190

/openbmc/openpower-hw-diags/test/
H A Dpdbg-test.dts5 ATTR_PHYS_DEV_PATH = "physical:sys-0";
13 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/bmc-0";
25 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0";
39 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/nx-0";
47 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/occ-0";
57 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/perv-1";
67 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/perv-12";
76 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/mc-0";
85 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/mc-0/mi-0";
94 ATTR_PHYS_DEV_PATH = "physical:sys-0/node-0/proc-0/mc-0/mi-0/mcc-0";
[all …]
/openbmc/phosphor-led-sysfs/
H A Dphysical.hpp7 #include <xyz/openbmc_project/Led/Physical/server.hpp>
22 sdbusplus::xyz::openbmc_project::Led::server::Physical>;
24 /** @class Physical
25 * @brief Responsible for applying actions on a particular physical LED
27 class Physical : public PhysicalIfaces class
30 Physical() = delete;
31 ~Physical() override = default;
32 Physical(const Physical&) = delete;
33 Physical& operator=(const Physical&) = delete;
34 Physical(Physical&&) = delete;
[all …]
H A DREADME.md3 This project exposes physical LEDs on dbus.
33 `- /xyz/openbmc_project/led/physical
34 `- /xyz/openbmc_project/led/physical/identify
36 busctl introspect xyz.openbmc_project.LED.Controller /xyz/openbmc_project/led/physical/identify
39 xyz.openbmc_project.Led.Physical interface - - -
40 .Color property s "xyz.openbmc_project.Led.Physical.Pal... e…
43 .State property s "xyz.openbmc_project.Led.Physical.Act... e…
55 /xyz/openbmc_project/led/physical/identify \
56 xyz.openbmc_project.Led.Physical State \
57 s "xyz.openbmc_project.Led.Physical.Action.Off"
[all …]
H A Dphysical.cpp17 #include "physical.hpp"
29 void Physical::setInitialState() in setInitialState()
41 sdbusplus::xyz::openbmc_project::Led::server::Physical::state( in setInitialState()
50 sdbusplus::xyz::openbmc_project::Led::server::Physical::state( in setInitialState()
55 sdbusplus::xyz::openbmc_project::Led::server::Physical::state( in setInitialState()
61 auto Physical::state() const -> Action in state()
63 return sdbusplus::xyz::openbmc_project::Led::server::Physical::state(); in state()
66 auto Physical::state(Action value) -> Action in state()
69 sdbusplus::xyz::openbmc_project::Led::server::Physical::state(); in state()
72 sdbusplus::xyz::openbmc_project::Led::server::Physical::state(value); in state()
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Led/
H A DREADME.md1 # Managing LED groups and physical LEDs through BMC
11 While it is entirely possible to act directly on a physical LED, it makes hard
59 This says that the group `bmc_booted` consists of 2 physical LEDs in it. When
105 ## Understanding Physical LEDs
108 Describing the Physical LED here just for documenting it and strictly NOT to be
111 ## Dbus interfaces for physical LEDs
116 …m/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Led/Physical.interface.yaml
120 **Path: `/xyz/openbmc_project/led/physical/<name>`** **Interface:
121 `xyz.openbmc_Project.Led.Physical`**
125 and `id_rear` physical LEDs.
[all …]
/openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/sensors/phosphor-nvme/
H A Dnvme_config.json9 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_0_locate",
19 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_1_locate",
29 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_2_locate",
39 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_3_locate",
49 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_4_locate",
59 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_5_locate",
69 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_6_locate",
79 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_7_locate",
89 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_8_locate",
99 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_9_locate",
[all …]
H A Dnvme_json_rewrite.sh46 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_0_locate",
56 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_1_locate",
66 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_2_locate",
76 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_3_locate",
86 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_4_locate",
96 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_5_locate",
106 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_6_locate",
116 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_7_locate",
126 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_8_locate",
136 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_9_locate",
[all …]
/openbmc/linux/Documentation/userspace-api/media/cec/
H A Dcec-ioc-adap-g-phys-addr.rst15 CEC_ADAP_G_PHYS_ADDR, CEC_ADAP_S_PHYS_ADDR - Get or set the physical address
40 To query the current physical address applications call
42 driver stores the physical address.
44 To set a new physical address applications store the physical address in
52 To clear an existing physical address use ``CEC_PHYS_ADDR_INVALID``.
60 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the physical address
63 The physical address is a 16-bit number where each group of 4 bits
64 represent a digit of the physical address a.b.c.d where the most
69 is supported. The physical address a device shall use is stored in the
73 different physical address of the form a.0.0.0 that the sources will
[all …]
/openbmc/phosphor-led-sysfs/test/
H A Dphysical.cpp1 #include "physical.hpp"
12 using Action = sdbusplus::xyz::openbmc_project::Led::server::Physical::Action;
75 TEST(Physical, ctor_none_trigger) in TEST() argument
81 phosphor::led::Physical phy(bus, ledObj, std::move(led)); in TEST()
85 TEST(Physical, ctor_maxbrightness_and_brightness_read_127) in TEST() argument
93 phosphor::led::Physical phy(bus, ledObj, std::move(led)); in TEST()
97 TEST(Physical, ctor_maxbrightness_and_brightness_read_0) in TEST() argument
105 phosphor::led::Physical phy(bus, ledObj, std::move(led)); in TEST()
109 TEST(Physical, ctor_only_maxbrightness_read_127) in TEST() argument
117 phosphor::led::Physical phy(bus, ledObj, std::move(led)); in TEST()
[all …]
/openbmc/linux/Documentation/admin-guide/mm/
H A Dconcepts.rst12 address to a physical address.
19 The physical memory in a computer system is a limited resource and
21 the amount of memory that can be installed. The physical memory is not
27 All this makes dealing directly with physical memory quite complex and
30 The virtual memory abstracts the details of physical memory from the
32 physical memory (demand paging) and provides a mechanism for the
38 address encoded in that instruction to a `physical` address that the
41 The physical system memory is divided into page frames, or pages. The
47 Each physical memory page can be mapped as one or more virtual
49 translation from a virtual address used by programs to the physical
[all …]
/openbmc/bmcweb/test/redfish-core/include/
H A Dfilter_expr_parser_test.cpp39 "SystemType ne 'Physical'", in TEST()
40 R"(unquoted_string("SystemType") Not Equal quoted_string("Physical"))"); in TEST()
54 "Status/State eq 'Enabled' and Status/Health eq 'OK' or SystemType eq 'Physical'", in TEST()
55 …quals quoted_string("OK")) or (unquoted_string("SystemType") Equals quoted_string("Physical"))))"); in TEST()
57 "(Status/State eq 'Enabled' and Status/Health eq 'OK') or SystemType eq 'Physical'", in TEST()
58 …quals quoted_string("OK"))) or (unquoted_string("SystemType") Equals quoted_string("Physical")))"); in TEST()
101 EXPECT_TRUE(parseFilter("ProcessorSummary/Count lt 'Physical'")); in TEST()
102 EXPECT_TRUE(parseFilter("ProcessorSummary/Count le 'Physical'")); in TEST()
103 EXPECT_TRUE(parseFilter("ProcessorSummary/Count gt 'Physical'")); in TEST()
104 EXPECT_TRUE(parseFilter("ProcessorSummary/Count ge 'Physical'")); in TEST()
[all …]
/openbmc/linux/include/linux/
H A Dpsp-sev.h88 * @tmr_address: system physical address used for SEV-ES
103 * @tmr_address: system physical address used for SEV-ES
105 * @nv_address: system physical address used for PSP NV storage
150 * @address: physical address of firmware image
161 * @address: physical address of region to place unique CPU ID(s)
233 * @dh_cert_address: physical address of DH certificate blob
235 * @session_address: physical address of session parameters
253 * @address: physical address of memory region to encrypt
266 * @address: physical address of memory region to encrypt
280 * @address: physical address containing the measurement blob
[all …]
/openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/
H A Dcounters.rst78 Physical port counters
82 additional counters like flow control, FEC and more. Physical port counters
86 A set of the physical port counters, per priority per port.
469 software counters. These packets are counted by physical port and vPort
491 physical port and vPort counters. You may open more rx queues and spread
507 counted by physical port and vPort counters.
517 are counted by physical port and vPort counters.
856 Physical Port Counters
858 The physical port counters are the counters on the external port connecting the
863 .. flat-table:: Physical Port Counter Table
[all …]
/openbmc/linux/Documentation/i2c/
H A Di2c-sysfs.rst13 is a gap of knowledge to map from the I2C bus physical number and MUX topology
16 the concept of logical I2C buses in the kernel, by knowing the physical I2C
41 start with ``i2c-`` are I2C buses, which may be either physical or logical. The
59 (Physical) I2C Bus Controller
63 physical I2C bus controllers. The controllers are hardware and physical, and the
70 I2C Bus Physical Number
73 For each physical I2C bus controller, the system vendor may assign a physical
82 written upon virtual memory space, instead of physical memory space.
84 Each logical I2C bus may be an abstraction of a physical I2C bus controller, or
90 Physical I2C Bus
[all …]
/openbmc/linux/drivers/gpu/drm/msm/disp/dpu1/
H A Ddpu_encoder_phys.h29 * enum dpu_enc_split_role - Role this physical encoder will play in a
43 * enum dpu_enc_enable_state - current enabled state of the physical encoder
64 * struct dpu_encoder_phys_ops - Interface the physical encoders provide to
85 * @trigger_start: Process start event on physical encoder
144 * struct dpu_encoder_phys - physical encoder that drives a single INTF block
163 * @vsync_cnt: Vsync count for the physical encoder
164 * @underrun_cnt: Underrun count for the physical encoder
208 * @base: Baseclass physical encoder structure
229 * @base: Baseclass physical encoder structure
279 * dpu_encoder_phys_vid_init - Construct a new video mode physical encoder
[all …]
/openbmc/linux/Documentation/mm/
H A Dmemory-model.rst4 Physical Memory Model
7 Physical memory in a system may be addressed in different ways. The
8 simplest case is when the physical memory starts at address 0 and
20 All the memory models track the status of physical page frames using
24 mapping between the physical page frame number (PFN) and the
35 non-NUMA systems with contiguous, or mostly contiguous, physical
39 maps the entire physical memory. For most architectures, the holes
49 actual physical pages. In such case, the architecture specific
58 systems with physical memory starting at address different from 0.
65 as hot-plug and hot-remove of the physical memory, alternative memory
[all …]
/openbmc/linux/include/linux/firmware/intel/
H A Dstratix10-smc.h24 * EL1 and EL3 communicates pointer as physical address rather than the
106 * a1: 64bit physical address of the configuration data memory block
113 * a1: 64bit physical address of 1st completed memory block if any completed
115 * a2: 64bit physical address of 2nd completed memory block if any completed
117 * a3: 64bit physical address of 3rd completed memory block if any completed
138 * a1: 64bit physical address of 1st completed memory block.
139 * a2: 64bit physical address of 2nd completed memory block if
141 * a3: 64bit physical address of 3rd completed memory block if
171 * Sync call used by service driver at EL1 to query the physical address of
180 * a1: start of physical address of reserved memory block.
[all …]
/openbmc/u-boot/drivers/mtd/ubi/
H A Dubi-media.h55 * initialization UBI finds out that there are available physical eraseblocks
57 * (the physical eraseblocks reserved for bad eraseblocks handling and other
58 * reserved physical eraseblocks are not taken). So, if there is a volume with
70 * of good physical eraseblocks the NAND chip on the device will have, but this
76 * Note, first UBI reserves some amount of physical eraseblocks for bad
78 * means that the pool of reserved physical eraseblocks will always be present.
91 * physical eraseblocks, don't allow the wear-leveling
133 * physical eraseblock. These values have to be the same for all physical
162 * @copy_flag: if this logical eraseblock was copied from another physical
171 * @data_pad: how many bytes at the end of this physical eraseblock are not
[all …]
H A Dwl.c12 * physical eraseblocks and erase counters and knows nothing about logical
13 * eraseblocks, volumes, etc. From this sub-system's perspective all physical
14 * eraseblocks are of two types - used and free. Used physical eraseblocks are
15 * those that were "get" by the 'ubi_wl_get_peb()' function, and free physical
18 * Physical eraseblocks returned by 'ubi_wl_get_peb()' have only erase counter
19 * header. The rest of the physical eraseblock contains only %0xFF bytes.
21 * When physical eraseblocks are returned to the WL sub-system by means of the
27 * physical eraseblocks with low erase counter to free physical eraseblocks
30 * If the WL sub-system fails to erase a physical eraseblock, it marks it as
34 * in a physical eraseblock, it has to be moved. Technically this is the same
[all …]
/openbmc/linux/drivers/mtd/ubi/
H A Dubi-media.h57 * initialization UBI finds out that there are available physical eraseblocks
59 * (the physical eraseblocks reserved for bad eraseblocks handling and other
60 * reserved physical eraseblocks are not taken). So, if there is a volume with
72 * of good physical eraseblocks the NAND chip on the device will have, but this
78 * Note, first UBI reserves some amount of physical eraseblocks for bad
80 * means that the pool of reserved physical eraseblocks will always be present.
94 * physical eraseblocks, don't allow the wear-leveling
136 * physical eraseblock. These values have to be the same for all physical
165 * @copy_flag: if this logical eraseblock was copied from another physical
174 * @data_pad: how many bytes at the end of this physical eraseblock are not
[all …]
/openbmc/linux/include/xen/interface/hvm/
H A Dstart_info.h12 * NOTE: nothing will be loaded at physical address 0, so a 0 value in any
26 * | modlist_paddr | Physical address of an array of modules
29 * | cmdline_paddr | Physical address of the command line,
32 * | rsdp_paddr | Physical address of the RSDP ACPI data structure.
34 * | memmap_paddr | Physical address of the (optional) memory map. Only
47 * | paddr | Physical address of the module.
51 * | cmdline_paddr | Physical address of the command line,
114 uint64_t modlist_paddr; /* Physical address of an array of */
116 uint64_t cmdline_paddr; /* Physical address of the command line. */
117 uint64_t rsdp_paddr; /* Physical address of the RSDP ACPI data */
[all …]
/openbmc/u-boot/include/asm-generic/
H A Dio.h20 * phys_to_virt() - Return a virtual address mapped to a given physical address
21 * @paddr: the physical address
23 * Returns a virtual address which the CPU can access that maps to the physical
37 * virt_to_phys() - Return the physical address that a virtual address maps to
40 * Returns the physical address which the CPU-accessible virtual address @vaddr
43 * Returns: the physical address which @vaddr maps to
72 * map_physmem() - Return a virtual address mapped to a given physical address
73 * @paddr: the physical address
78 * physical address @paddr. The mapping will be valid for at least @len bytes,
/openbmc/linux/include/net/caif/
H A Dcfcnfg.h17 * enum cfcnfg_phy_preference - Physical preference HW Abstraction
19 * @CFPHYPREF_UNSPECIFIED: Default physical interface
21 * @CFPHYPREF_LOW_LAT: Default physical interface for low-latency
23 * @CFPHYPREF_HIGH_BW: Default physical interface for high-bandwidth
54 * cfcnfg_add_phy_layer() - Adds a physical layer to the CAIF stack.
58 * @phy_layer: Specify the physical layer. The transmit function
82 * cfcnfg_set_phy_state() - Set the state of the physical interface device.
84 * @phy_layer: Physical Layer representation
/openbmc/qemu/target/mips/sysemu/
H A Dphysaddr.c78 static int get_seg_physical_address(CPUMIPSState *env, hwaddr *physical, in get_seg_physical_address() argument
92 return env->tlb->map_address(env, physical, prot, real_address, in get_seg_physical_address()
96 *physical = physical_base | (real_address & segmask); in get_seg_physical_address()
102 static int get_segctl_physical_address(CPUMIPSState *env, hwaddr *physical, in get_segctl_physical_address() argument
111 return get_seg_physical_address(env, physical, prot, real_address, in get_segctl_physical_address()
116 int get_physical_address(CPUMIPSState *env, hwaddr *physical, in get_physical_address() argument
142 ret = get_segctl_physical_address(env, physical, prot, in get_physical_address()
149 ret = env->tlb->map_address(env, physical, prot, in get_physical_address()
158 ret = env->tlb->map_address(env, physical, prot, in get_physical_address()
185 ret = get_seg_physical_address(env, physical, prot, in get_physical_address()
[all …]
/openbmc/openbmc/meta-ibm/meta-sbp1/recipes-phosphor/leds/phosphor-led-manager/
H A Dbmc_booted.conf4 After=mapper-wait@-xyz-openbmc_project-led-physical-led_bmc_ready.service
5 After=mapper-wait@-xyz-openbmc_project-led-physical-led_id_dwr_back_p.service
6 After=mapper-wait@-xyz-openbmc_project-led-physical-led_id_dwr_frnt_p.service
11 Wants=mapper-wait@-xyz-openbmc_project-led-physical-led_bmc_ready.service
12 Wants=mapper-wait@-xyz-openbmc_project-led-physical-led_id_dwr_back_p.service
13 Wants=mapper-wait@-xyz-openbmc_project-led-physical-led_id_dwr_frnt_p.service

12345678910>>...190