Home
last modified time | relevance | path

Searched refs:in (Results 251 – 275 of 16239) sorted by relevance

1...<<11121314151617181920>>...650

/openbmc/linux/tools/virtio/virtio-trace/
H A DREADME41 1) Make FIFO in a host
49 trace-path-cpu{0,1,2}.{in.out}
51 agent-ctl-path.{in,out}.
53 2) Set up of virtio-serial pipe in a host
87 You can find some chardev in /dev/virtio-ports/ in the guest.
93 0) Build trace agent in a guest
96 1) Enable ftrace in the guest
100 2) Run trace agent in the guest
106 3) Open FIFO in a host
110 be solved in the future.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/
H A Dsecure.txt5 kernel) are not TrustZone aware and run entirely in either the Normal
8 visible only in the Secure address space, only in the Normal address
9 space, or visible in both. (One example of that situation would be a
14 is that any property that needs a different value in the Secure world
24 Defining the bindings in this way means that a device tree which has
26 still be processed unmodified by existing Non-secure software (and in
30 world consumers (like kernels that run entirely in Secure) to simply
33 world views need to be described in a single device tree.
39 in the secure world. The combination of this with "status" allows
46 /* Neither specified: default to visible in both S and NS */
[all …]
/openbmc/linux/Documentation/admin-guide/pm/
H A Dstrategies.rst15 One of them is based on using global low-power states of the whole system in
19 and the system stays in it until a special signal is received from one of
20 designated devices, triggering a transition to the ``working state`` in which
27 components of the system, as needed, in the working state. In consequence, if
28 this strategy is in use, the working state of the system usually does not
30 a metastate covering a range of different power states of the system in which
31 the individual components of it can be either ``active`` (in use) or
32 ``inactive`` (idle). If they are active, they have to be in power states
34 are inactive, ideally, they should be in low-power states in which they may not
43 for the same system in a sleep state. However, transitions from sleep states
[all …]
/openbmc/sdbusplus/tools/sdbusplus/templates/
H A Dinterface.server.hpp.mako9 % for h in interface.cpp_includes():
38 * @param[in] bus - Bus to attach to.
39 * @param[in] path - Path to attach at.
50 * @param[in] bus - Bus to attach to.
66 % for m in interface.methods:
70 % for s in interface.signals:
74 % for p in interface.properties:
123 % for m in interface.methods:
127 % for p in interface.properties:
132 % if 'const' not in p.flags and 'readonly' not in p.flags:
[all …]
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Dbq25890.yaml36 description: maximum charging voltage (in uV)
40 description: maximum charging current (in uA)
45 charge will be terminated when current in constant-voltage phase
46 drops below this value (in uA)
50 description: maximum charge current during precharge phase (in uA)
56 the system will be regulated above minimum-sys-voltage setting (in uV)
60 description: VBUS voltage level in boost mode (in uV)
64 description: maximum allowed current draw in boost mode (in uA)
80 (in degrees Celsius). If omitted, the default setting will be used (120 degrees)
83 description: value of a resistor in series with the battery (in Micro Ohms)
[all …]
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/autofs/autofs/
H A Dremove-bashism.patch4 Subject: [PATCH] autofs.init.in: remove bashism
14 redhat/autofs.init.in | 12 ++++++------
15 samples/rc.autofs.in | 10 +++++-----
18 diff --git a/redhat/autofs.init.in b/redhat/autofs.init.in
20 --- a/redhat/autofs.init.in
21 +++ b/redhat/autofs.init.in
73 diff --git a/samples/rc.autofs.in b/samples/rc.autofs.in
75 --- a/samples/rc.autofs.in
76 +++ b/samples/rc.autofs.in
/openbmc/linux/drivers/vdpa/mlx5/net/
H A Dmlx5_vnet.c406 void *in; in qp_create() local
422 if (!in) { in qp_create()
437 kfree(in); in qp_create()
545 void *in; in cq_create() local
703 void *in; in create_umem() local
866 void *in; in create_virtqueue() local
1071 void *in; in modify_qp() local
1187 if (!in) in modify_virtqueue()
1419 if (!in) in create_rqt()
1454 if (!in) in modify_rqt()
[all …]
/openbmc/openbmc/poky/meta/recipes-devtools/automake/automake/
H A Dnew_rt_path_for_test-driver.patch4 Subject: [PATCH] Set relative to top_builddir path in Makefile to access
12 bin/automake.in | 9 ++++++++-
15 diff --git a/bin/automake.in b/bin/automake.in
17 --- a/bin/automake.in
18 +++ b/bin/automake.in
21 # in Makefiles.
28 # in configure.ac.
/openbmc/openbmc/poky/meta/recipes-devtools/expect/expect/
H A D0001-expect-install-scripts-without-using-the-fixline1-tc.patch6 complaining that 'GLIBC_2.14' is not found in /lib64/libc.so.6 but is required
10 libtcl8.6.so.0 in sysroot. However, all commands in SCRIPTS already have got
16 Makefile.in | 2 +-
19 diff --git a/Makefile.in b/Makefile.in
21 --- a/Makefile.in
22 +++ b/Makefile.in
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/rp-pppoe/rp-pppoe/
H A Dtop-autoconf.patch6 The autoconf stuff is all in a subdirectory, which is rather annoying
7 as OE expects patches to be applied and autoconf stuff to be done in
9 called there - all it does is run a sub autoconf stuff in the src
16 configure.in | 4 ++++
19 create mode 100644 configure.in
32 diff --git a/configure.in b/configure.in
36 +++ b/configure.in
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-m2crypto/
H A Dcross-compile-platform.patch1 Do not compute platform, this does not work in cross compile environment
17 - if mach in ('i386', 'i486', 'i586', 'i686'):
19 - elif mach in ('ppc64', 'powerpc64', 'ppc64le', 'ppc64el'):
21 - elif mach in ('ppc', 'powerpc'):
26 - if mach in ('ppc64le', 'ppc64el'):
28 - if mach in ('arm64_be'):
31 self.swig_opts.extend(['-I%s' % i for i in self.include_dirs])
33 # Some Linux distributor has added the following line in
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/linux-atm/linux-atm/
H A Dlink-with-ldflags.patch7 diff -Nurp linux-atm-2.5.2.orig/configure.in linux-atm-2.5.2/configure.in
8 --- linux-atm-2.5.2.orig/configure.in 2010-12-28 23:36:07.000000000 +0800
9 +++ linux-atm-2.5.2/configure.in 2014-12-22 10:25:23.830510932 +0800
30 diff -Nurp linux-atm-2.5.2.orig/src/qgen/Makefile.in linux-atm-2.5.2/src/qgen/Makefile.in
31 --- linux-atm-2.5.2.orig/src/qgen/Makefile.in 2010-12-29 00:06:11.000000000 +0800
32 +++ linux-atm-2.5.2/src/qgen/Makefile.in 2014-12-22 10:23:51.914508318 +0800
/openbmc/qemu/tests/qemu-iotests/
H A D219.out10 Pause/resume in RUNNING
39 {"error": {"class": "GenericError", "desc": "Job 'job0' in state 'running' cannot accept command ve…
41 {"error": {"class": "GenericError", "desc": "Job 'job0' in state 'running' cannot accept command ve…
44 {"error": {"class": "GenericError", "desc": "Job 'job0' in state 'running' cannot accept command ve…
51 Pause/resume in READY
81 {"error": {"class": "GenericError", "desc": "Job 'job0' in state 'ready' cannot accept command verb…
83 {"error": {"class": "GenericError", "desc": "Job 'job0' in state 'ready' cannot accept command verb…
100 Pause/resume in RUNNING
153 Pause/resume in RUNNING
214 Pause/resume in RUNNING
[all …]
/openbmc/u-boot/cmd/aspeed/nettest/
H A Dncsi.c32 void ncsi_reqdump(MAC_ENGINE *eng, NCSI_Command_Packet *in) in ncsi_reqdump() argument
35 … : %02x %02x %02x %02x %02x %02x\n", in->DA[ 0 ], in->DA[ 1 ], in->DA[ 2 ], in->DA[ 3 ], in->… in ncsi_reqdump()
36 … : %02x %02x %02x %02x %02x %02x\n", in->SA[ 0 ], in->SA[ 1 ], in->SA[ 2 ], in->SA[ 3 ], in->… in ncsi_reqdump()
51 for ( i = 0; i < SWAP_2B_BEDN( in->Payload_Length ); i++ ) { in ncsi_reqdump()
54 case 3 : PRINTF( FP_LOG, " %02x\n", in->Payload_Data[ i ]); break; in ncsi_reqdump()
55 default : PRINTF( FP_LOG, " %02x", in->Payload_Data[ i ]); break; in ncsi_reqdump()
61 void ncsi_respdump (MAC_ENGINE *eng, NCSI_Response_Packet *in) { in ncsi_respdump() argument
65 … : %02x %02x %02x %02x %02x %02x\n", in->DA[ 0 ], in->DA[ 1 ], in->DA[ 2 ], in->DA[ 3 ], in->… in ncsi_respdump()
66 … : %02x %02x %02x %02x %02x %02x\n", in->SA[ 0 ], in->SA[ 1 ], in->SA[ 2 ], in->SA[ 3 ], in->… in ncsi_respdump()
81 for ( i = 0; i < SWAP_2B_BEDN( in->Payload_Length ); i++ ) { in ncsi_respdump()
[all …]
/openbmc/linux/Documentation/arch/arm/
H A Dkernel_mode_neon.rst9 * Isolate your NEON code in a separate compilation unit, and compile it with
13 * Don't sleep in your NEON code, and be aware that it will be executed with
19 It is possible to use NEON instructions (and in some cases, VFP instructions) in
24 may call schedule()], as NEON or VFP instructions will be executed in a
35 every context switch, resulting in a trap when subsequently a NEON/VFP
49 Interruptions in kernel mode
55 following rules and restrictions apply in the kernel:
56 * NEON/VFP code is not allowed in interrupt context;
61 kernel_neon_end() and kernel_neon_begin() in places in your code where none of
63 reasonably cheap if no context switch occurred in the meantime)
[all …]
/openbmc/phosphor-dbus-monitor/src/test/templates/
H A Dpropertygentest.mako.hpp2 % for m in meta:
8 % for i in interfaces:
14 % for p in propertynames:
20 % for g in propertygroups:
23 % for p in g.members:
31 % for g in propertygroups:
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/openhpi/files/
H A Dopenhpi-linkfix.patch4 in compilation since it does not compile
13 plugins/ipmi/Makefile.in | 4 +++-
16 diff --git a/plugins/ipmi/Makefile.in b/plugins/ipmi/Makefile.in
18 --- a/plugins/ipmi/Makefile.in
19 +++ b/plugins/ipmi/Makefile.in
21 MAINTAINERCLEANFILES = Makefile.in
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/nspr/nspr/
H A D0001-config-nspr-config.in-don-t-pass-LDFLAGS.patch4 Subject: [PATCH] config/nspr-config.in: don't pass LDFLAGS
12 config/nspr-config.in | 2 +-
15 diff --git a/config/nspr-config.in b/config/nspr-config.in
17 --- a/config/nspr-config.in
18 +++ b/config/nspr-config.in
25 for i in $os_ldflags ; do
/openbmc/openbmc/poky/meta/recipes-devtools/autoconf/autoconf/
H A Dno-man.patch7 otherwise pull in a dependency on help2man.
13 Makefile.in | 10 ----------
16 diff --git a/Makefile.in b/Makefile.in
18 --- a/Makefile.in
19 +++ b/Makefile.in
35 # - its .w and .x files and its source script in bin/
/openbmc/openbmc/poky/meta/recipes-devtools/libtool/libtool/
H A D0001-ltmain.in-Parse-additional-clang-options.patch1 ltmain.in: Parse additional clang options
4 runtime in some cases. Therefore pass these options to linker when found in
7 * build-aux/ltmain.in: Handle clang linker options
13 build-aux/ltmain.in | 4 +++-
16 diff --git a/build-aux/ltmain.in b/build-aux/ltmain.in
18 --- a/build-aux/ltmain.in
19 +++ b/build-aux/ltmain.in
/openbmc/linux/drivers/firmware/efi/
H A Dmemattr.c56 static bool entry_is_valid(const efi_memory_desc_t *in, efi_memory_desc_t *out) in entry_is_valid() argument
58 u64 in_paddr = in->phys_addr; in entry_is_valid()
59 u64 in_size = in->num_pages << EFI_PAGE_SHIFT; in entry_is_valid()
62 *out = *in; in entry_is_valid()
64 if (in->type != EFI_RUNTIME_SERVICES_CODE && in entry_is_valid()
65 in->type != EFI_RUNTIME_SERVICES_DATA) { in entry_is_valid()
71 (!PAGE_ALIGNED(in->phys_addr) || in entry_is_valid()
72 !PAGE_ALIGNED(in->num_pages << EFI_PAGE_SHIFT))) { in entry_is_valid()
107 if (md->type != in->type) { in entry_is_valid()
/openbmc/linux/arch/arm64/boot/dts/arm/
H A Djuno-cs-r1r2.dtsi17 in-ports {
33 in-ports {
64 in-ports {
97 arm,trig-in-sigs = <0 1>;
98 arm,trig-in-types = <SNK_FULL SNK_ACQCOMP>;
106 arm,trig-in-sigs = <2 3 4>;
107 arm,trig-in-types = <ELA_DBGREQ ELA_TSTART ELA_TSTOP>;
113 arm,trig-in-sigs = <5 6 7>;
114 arm,trig-in-types = <ELA_DBGREQ ELA_TSTART ELA_TSTOP>;
/openbmc/u-boot/doc/driver-model/
H A DMIGRATION.txt4 U-Boot has been migrating to a new driver model since its introduction in
15 switching over to using CONFIG_DM_MMC and other base driver model options in
16 time for inclusion in the 2019.04 rerelease.
26 other base driver model options in time for inclusion in the 2019.07 rerelease.
36 other base driver model options in time for inclusion in the 2019.07 rerelease.
47 subsystems. At this point we will be able to audit and correct the logic in
56 to move the migration with in the deadline.
97 model options in time for inclusion in the 2019.07 release.
106 driver model options in time for inclusion in the 2019.07 release.
/openbmc/openbmc/meta-nuvoton/recipes-bsp/images/npcm7xx-igps/
H A D0001-Adjust-paths-for-use-with-Bitbake.patch22 <offset>0</offset> <!-- offset in the header -->
24 + <size format='FileSize'>Poleg_bootblock.bin.full</size> <!-- size in the header -->
34 - <size format='FileSize'>output_binaries/UbootAndHeader.bin</size> <!-- size in the…
36 + <size format='FileSize'>u-boot.bin.full</size> <!-- size in the header -->
98 <offset>0x144</offset> <!-- offset in the header -->
99 <size>0x4</size> <!-- size in the header -->
109 <offset>0x200</offset> <!-- offset in the header -->
111 + <size format='FileSize'>u-boot.bin</size> <!-- size in the header calculated by…
123 <offset>0x144</offset> <!-- offset in the header -->
124 <size>0x4</size> <!-- size in the header -->
[all …]
/openbmc/linux/Documentation/firmware-guide/acpi/
H A DDSD-properties-rules.rst10 The _DSD (Device Specific Data) configuration object, introduced in ACPI 5.1,
15 the ACPI subsystem in the Linux kernel which automatically processes the data
23 generic Device Properties UUID in the _DSD return package as specified in the
25 "Device Properties UUID" in _DSD (Device Specific Data) Implementation Guide
29 that can be returned by _DSD in the Device Properties UUID sub-package for a
34 can be returned in the Device Properties UUID sub-package for the device in
40 representation of property subsets is via the mechanism specified in the
42 "Hierarchical Data Extension UUID" in _DSD (Device Specific Data)
65 There are cases in which, even if the general rule given above is followed in
70 possibly leading to a conflict with AML methods in the ACPI namespace. In
[all …]

1...<<11121314151617181920>>...650