/openbmc/linux/arch/arm/boot/dts/ti/omap/ |
H A D | am335x-wega-rdk.dts | 4 * Author: Teresa Remmet <t.remmet@phytec.de>
|
/openbmc/openbmc/poky/meta/recipes-support/boost/ |
H A D | boost_1.86.0.bb | 5 file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \
|
/openbmc/linux/drivers/net/ethernet/mellanox/mlx4/ |
H A D | alloc.c | 580 dma_addr_t t; in mlx4_buf_direct_alloc() local 586 dma_alloc_coherent(&dev->persist->pdev->dev, size, &t, in mlx4_buf_direct_alloc() 591 buf->direct.map = t; in mlx4_buf_direct_alloc() 593 while (t & ((1 << buf->page_shift) - 1)) { in mlx4_buf_direct_alloc() 612 dma_addr_t t; in mlx4_buf_alloc() local 627 PAGE_SIZE, &t, GFP_KERNEL); in mlx4_buf_alloc() 631 buf->page_list[i].map = t; in mlx4_buf_alloc()
|
/openbmc/linux/Documentation/i2c/ |
H A D | instantiating-devices.rst | 113 main chip by the means of an I2C bus. You won't know the number of the I2C 114 bus in advance, so the method 1 described above can't be used. Instead, 138 A variant of this is when you don't know for sure if an I2C device is 254 can't be done, there is a variety of cases where it can be helpful: 257 segment your device lives on doesn't have the proper class bit set and 258 thus detection doesn't trigger. 272 available, and you don't need to know what driver the device needs.
|
/openbmc/linux/net/ceph/crush/ |
H A D | mapper.c | 116 unsigned int t = work->perm[p + i]; in bucket_perm_choose() local 118 work->perm[p] = t; in bucket_perm_choose() 201 __u64 t; in bucket_tree_choose() local 210 t = (__u64)crush_hash32_4(bucket->h.hash, x, n, r, in bucket_tree_choose() 212 t = t >> 32; in bucket_tree_choose() 216 if (t < bucket->node_weights[l]) in bucket_tree_choose()
|
/openbmc/linux/arch/powerpc/boot/dts/fsl/ |
H A D | p1020mbg-pc.dtsi | 142 by default. We can't put 'status = "disabled";' here 143 since U-Boot doesn't clear the status property when 145 when there isn't any. So, just comment it out.
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | hisilicon-hns-dsaf.txt | 38 - phy-handle: phy handle of physical port. It is not required if there isn't 42 not required if there isn't cpld device. 51 0 stands for this bit will be fuzzy matched, TCAM won't care about this bit
|
/openbmc/qemu/docs/interop/ |
H A D | dbus.rst | 36 D-Bus, the protocol and standard, doesn't have mechanisms to enforce 60 - Improved reliability - crash of one part doesn't take 93 wouldn't be allowed to send a message to ``virtiofs_t``.
|
/openbmc/linux/Documentation/userspace-api/media/cec/ |
H A D | cec-ioc-adap-g-caps.rst | 81 this capability isn't set, then setting the physical address is 90 this capability isn't set, then the kernel will have configured 100 capability isn't set, then the kernel will handle all CEC
|
/openbmc/linux/tools/perf/jvmti/ |
H A D | jvmti_agent.c | 135 time_t t; in create_jit_cache_dir() local 138 time(&t); in create_jit_cache_dir() 139 localtime_r(&t, &tm); in create_jit_cache_dir()
|
/openbmc/openbmc/meta-raspberrypi/recipes-multimedia/omxplayer/ |
H A D | omxplayer_git.bb | 19 # system's ffmpeg library. This isn't ideal but it's ok for now. We do however 34 file://0005-Don-t-require-internet-connection-during-build.patch \ 58 # This isn't used directly by omxplayer, but applied to Makefile.ffmpeg which
|
/openbmc/qemu/scripts/coverity-scan/ |
H A D | coverity-scan.docker | 8 # set of options) so that random changes don't result in our accidentally 11 # We don't build on top of the fedora.docker file because we don't
|
/openbmc/openbmc/poky/meta/recipes-kernel/kmod/kmod/ |
H A D | 0001-Use-portable-implementation-for-basename-API.patch | 93 "\t%s [options] <test>\n" 118 "\t-V, --version show version\n" 119 "\t-h, --help show this help\n\n"
|
/openbmc/linux/Documentation/devicetree/bindings/arm/ |
H A D | pmu.yaml | 73 # Don't know how many CPUs, so no constraints to specify 90 the interrupt-affinity property shouldn't be present). 98 Indicates that this PMU doesn't support the 0xc and 0xd events.
|
/openbmc/linux/arch/um/include/shared/ |
H A D | os.h | 70 unsigned int t : 1; /* O_TRUNC */ member 77 .t = 0, .a = 0, .e = 0, .cl = 0 }) 117 flags.t = 1; in of_trunc()
|
/openbmc/linux/drivers/iio/dac/ |
H A D | ad5764.c | 144 struct spi_transfer t[] = { in ad5764_read() local 159 ret = spi_sync_transfer(st->spi, t, ARRAY_SIZE(t)); in ad5764_read()
|
/openbmc/linux/arch/arm/boot/dts/nxp/imx/ |
H A D | imx6qdl-udoo.dtsi | 43 * in reality it is a -20t (parallel) model, 45 * so it is equivalent to -19t model in drive 48 compatible = "urt,umsh-8596md-19t";
|
/openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/trusted-firmware-m/ |
H A D | trusted-firmware-m.inc | 13 # Note to future readers of this recipe: until the CMakeLists don't abuse 64 # Don't let FetchContent download more sources during do_configure 99 # can't use the usual install prefix variables.
|
/openbmc/openbmc/poky/meta/recipes-connectivity/bind/ |
H A D | bind_9.18.27.bb | 29 # Issue only affects dhcpd with recent bind versions. We don't ship dhcpd anymore 30 # so the issue doesn't affect us. 31 …icable-config: Issue only affects dhcpd with recent bind versions and we don't ship dhcpd anymore."
|
/openbmc/openbmc/meta-asrock/meta-e3c246d4i/recipes-x86/chassis/x86-power-control/ |
H A D | power-config-host0.json | 36 * The e3c246d4i doesn't have a PS_PWROK signal as far as
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 012.out | 2 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
|
/openbmc/qemu/tests/qemu-iotests/tests/ |
H A D | detect-zeroes-registered-buf.out | 2 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=134217728
|
/openbmc/linux/Documentation/power/ |
H A D | swsusp.rst | 29 they won't be accessible after resume and you may lose data, as though 32 power states like "standby", which normally don't turn USB off.) 99 time shouldn't need to be written interruptible. 147 Maybe I'm missing something, but why don't the regular I/O paths work? 245 There don't seem to be any generally useful behavioral 283 suspend(PMSG_FREEZE): devices are frozen so that they don't interfere 308 suspend(PMSG_FREEZE): devices are frozen so that they don't interfere 332 for suspend. If you don't need swap after resume these data can remain 342 inaccessible so they can't be stolen later on. The only thing that 457 modes like "suspend-to-RAM" or "standby". (Don't write "disk" to the [all …]
|
/openbmc/linux/drivers/media/pci/saa7164/ |
H A D | saa7164-api.c | 922 struct tmComResDescrHeader *hdr, *t; in saa7164_api_dump_subdevs() local 1062 t = (struct tmComResDescrHeader *) in saa7164_api_dump_subdevs() 1064 switch (t->subtype) { in saa7164_api_dump_subdevs() 1067 (struct tmComResTSFormatDescrHeader *)t; in saa7164_api_dump_subdevs() 1079 (struct tmComResPSFormatDescrHeader *)t; in saa7164_api_dump_subdevs() 1118 t->subtype); in saa7164_api_dump_subdevs() 1120 next_offset += t->len; in saa7164_api_dump_subdevs() 1481 struct tmComResGPIO t; in saa7164_api_modify_gpio() local 1489 t.pin = pin; in saa7164_api_modify_gpio() 1490 t.state = state; in saa7164_api_modify_gpio() [all …]
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | consumer.rst | 13 Drivers that can't work without standard GPIO calls should have Kconfig entries 191 checked, since the get/set calls don't return errors and since misconfiguration 213 don't need to sleep, and can safely be done from inside hard (non-threaded) IRQ 223 won't always match the specified output value, because of issues including 228 can read the value of output pins; those that can't should always return zero. 238 sleeping, which can't be done from inside IRQ handlers. 255 that can't be accessed from hardIRQ handlers, these calls act the same as the 286 gpiod_set_raw_value(desc, 0); don't care low 287 gpiod_set_raw_value(desc, 1); don't care high 421 unchecked error to use a GPIO that wasn't set up as an input using [all …]
|