Home
last modified time | relevance | path

Searched refs:we (Results 1 – 25 of 510) sorted by relevance

12345678910>>...21

/f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/
H A Dsprd,pinctrl.txt12 to choose one function (like: UART0) for which system, since we
15 There are too much various configuration that we can not list all
16 of them, so we can not make every Spreadtrum-special configuration
18 global configuration in future. Then we add one "sprd,control" to
19 set these various global control configuration, and we need use
22 Moreover we recognise every fields comprising one bit or several
23 bits in one global control register as one pin, thus we should
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
52 kernel on SC9860 platform), then we can not select "sleep" state
53 when the PUBCP system goes into deep sleep mode. Thus we introduce
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/usb/
H A Dgeneric.txt4 - maximum-speed: tells USB controllers we want to work up to a certain
10 - dr_mode: tells Dual-Role USB controllers that we want to work on a
15 - phy_type: tells USB controllers that we want to configure the core to support
27 - hnp-disable: tells OTG controllers we want to disable OTG HNP, normally HNP
30 - srp-disable: tells OTG controllers we want to disable OTG SRP, SRP is
32 - adp-disable: tells OTG controllers we want to disable OTG ADP, ADP is
/f-stack/freebsd/contrib/device-tree/Bindings/i2c/
H A Di2c-arb-gpio-challenge.txt24 - OUR_CLAIM: output from us signaling to other hosts that we want the bus
31 Let's say we want to claim the bus. We:
35 3. Check THEIR_CLAIMS. If none are asserted then the we have the bus and we are
44 - our-claim-gpio: The GPIO that we use to claim the bus.
51 - wait-retry-us: we'll attempt another claim after this many microseconds.
53 - wait-free-us: we'll give up after this many microseconds. Default is 50000 us.
H A Di2c-cros-ec-tunnel.txt3 On some ChromeOS board designs we've got a connection to the EC (embedded
5 the EC (like a battery and PMIC). To get access to those devices we need
14 - google,remote-bus: The EC bus we'd like to talk to.
/f-stack/freebsd/contrib/openzfs/.github/
H A Dno-response.yml11 information that is currently in the issue, we don't have enough information
12 to take action. Please reach out if you have or find the answers we need so
13 that we can investigate further.
/f-stack/app/redis-5.0.5/
H A DMANIFESTO30 not an API that resembles the nature of fundamental data structures. If we
32 likely know, understand and recognize the same basic data structures we have
37 4 - We believe in code efficiency. Computers get faster and faster, yet we
51 5 - Code is like a poem; it's not just something we write to reach some
58 in a bigger story, we'll be happy to use beautiful self contained libraries
59 when needed. At the same time, when writing the Redis story we're trying to
72 7 - Threading is not a silver bullet. Instead of making Redis threaded we
81 approach more sounding. In the future we may explore parallelism only for
91 all cases. Instead we'll provide commands to quickly migrate keys from one
97 writing code, the best thing to do is stop. To prevent this, we'll avoid
[all …]
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/cli_user/misc/
H A Dmisc.cfg40 # these are a set of values we apply, for use when testing the
41 # zfs get/set subcommands - ordered as per the list above so we
65 # these are a set of values we apply, for use when testing the
66 # zfs get/set subcommands - ordered as per the list above so we
92 # these are a set of values we apply, for use when testing the
93 # zfs get/set subcommands - ordered as per the list above so we
/f-stack/freebsd/contrib/device-tree/src/arm/
H A Domap3430-sdp.dts71 gpmc,we-on-ns = <54>;
72 gpmc,we-off-ns = <168>;
121 gpmc,we-on-ns = <6>;
122 gpmc,we-off-ns = <30>;
167 gpmc,we-on-ns = <0>;
168 gpmc,we-off-ns = <42>;
/f-stack/freebsd/contrib/openzfs/rpm/generic/
H A Dzfs-dkms.spec.in75 # Are we doing an upgrade?
77 # Yes we are. Are we upgrading to a new ZFS version?
92 # If we're here then we're doing an uninstall (not upgrade).
/f-stack/freebsd/contrib/device-tree/src/powerpc/
H A Dps3.dts22 * so we'll put a null entry here.
34 * we'll put a null entries here. These will be initialized after
39 * here so we can bring up both of ours. See smp_setup_cpu_maps().
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dallwinner,sun4i-a10-mdio.yaml16 # Select every compatible, including the deprecated ones. This way, we
17 # will be able to report a warning when we have that compatible, since
18 # we will validate the node thanks to the select, but won't report it
/f-stack/dpdk/lib/librte_lpm/
H A Dmeson.build6 # since header files have different names, we can install all vector headers
7 # without worrying about which architecture we actually need
/f-stack/freebsd/netgraph/bluetooth/l2cap/
H A DTODO35 to get data from kernel to user space. For example if we need to pass
36 1K of information for every channel, then worst case is that we need
41 For now we destroy all channels when upstream hook is disconnected.
/f-stack/freebsd/contrib/device-tree/Bindings/spi/
H A Dspi-sprd-adi.txt11 we can configure them to allow other hardware components to use it independently,
12 which means we can just link one analog chip address to one hardware channel,
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
21 Since we have multi-subsystems will use unique ADI to access analog chip, when
26 Then we need one hardware spinlock to synchronize between the multiple subsystems.
/f-stack/dpdk/doc/guides/contributing/
H A Dabi_versioning.rst171 Assume we have a function as follows
213 application was linked to it. To see how this is done, we start with the
298 Immediately after the function, we add the VERSION_SYMBOL macro.
334 we add the BIND_DEFAULT_SYMBOL macro.
389 defined, we add this
410 Finally, we need to indicate to the :doc:`meson/ninja build system
413 versioning, in the ``meson.build`` file we add the following
437 Assume we have an experimental function ``rte_acl_create`` as follows:
472 When we promote the symbol to the stable ABI, we simply strip the
511 symbol as before, we now add the symbol to both the ``EXPERIMENTAL``
[all …]
/f-stack/dpdk/kernel/linux/
H A Dmeson.build6 # if we are cross-compiling we need kernel_dir specified
/f-stack/dpdk/doc/guides/howto/
H A Dvirtio_user_for_container_networking.rst39 Different virtio PCI devices we usually use as a para-virtualization I/O in the
43 in DPDK's ether layer. And to minimize the change, we reuse already-existing
56 Here we use Docker as container engine. It also applies to LXC, Rocket with
95 Note: If we run all above setup on the host, it's a shm-based IPC.
101 * Cannot work with --huge-unlink option. As we need to reopen the hugepage
/f-stack/freebsd/contrib/device-tree/Bindings/mtd/
H A Dgpmc-nor.txt19 - gpmc,we-on-ns Write-enable assertion time
20 - gpmc,we-off-ns: Write-enable de-assertion time
68 gpmc,we-on-ns = <54>;
69 gpmc,we-off-ns = <168>;
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dptpclient.rst104 And than we parse application specific arguments
158 As we saw above the ``main()`` function calls an application function on the
237 There are 3 types of packets on the RX path which we must parse to create a minimal
244 When we parse the *FOLLOW UP* packet we also create and send a *DELAY_REQUEST* packet.
245 Also when we parse the *DELAY RESPONSE* packet, and all conditions are met we adjust the PTP slave …
/f-stack/freebsd/contrib/device-tree/src/arm64/rockchip/
H A Drk3399-gru.dtsi31 * view, though, we won't create a full fixed regulator. We'll just
295 * When we go into S3 ARM Trusted Firmware will transition our PWM regulators
297 * voltage we get when we set the PWM pins to "input").
302 * To make extra certain that we don't hit this OVP at suspend time, we'll
304 * there will not be a big jump. Technically we only need to get within 200 mV
512 * hooked to ground. Because we specified "cd-gpios" below dw_mmc
653 * At the moment settings are identical for S0 and S3, but if we later
654 * need to configure things differently for S3 we'll adjust here.
724 * Since our pcie doesn't support ClockPM(CPM), we want
762 * the pull though so we don't burn needless power.
[all …]
/f-stack/app/redis-5.0.5/deps/
H A DREADME.md6 …ficial ecosystem but is developed externally from the Redis repository, so we just upgrade it as n…
31 However note that we change Jemalloc settings via the `configure` script of Jemalloc using the `--w…
58 4. Check manually that redis-cli and redis-benchmark behave as expecteed, since we have no tests fo…
73 We use Lua 5.1 and no upgrade is planned currently, since we don't want to break
76 and we definitely don't want to break old scripts.
81 Currently we have at least the following differences between official Lua 5.1
/f-stack/dpdk/doc/guides/prog_guide/
H A Dlpm_lib.rst59 we might need to continue the lookup process in the second level.
61 Since every entry of the tbl24 can potentially point to a tbl8, ideally, we would have 2^24 tbl8s,
140 Hence, in this case, we copy the exact same entry to every position indexed by one of these combina…
142 By doing this we ensure that during the lookup process, if a rule matching the IP address exists,
144 depending on whether we need to move to the next table or not.
186 If the entry is not in use, then it means we don't have a rule matching this IP.
190 then we use the tbl8 index to find out the tbl8 to be checked,
192 Similarly, if the entry is not in use, then we don't have a rule matching this IP address.
206 If we exhaust tbl8s, we won't be able to add any more rules.
209 A tbl8 is consumed whenever we have a new rule with depth bigger than 24,
[all …]
/f-stack/dpdk/lib/librte_acl/
H A Dmeson.build12 # a. we have AVX supported in minimum instruction set baseline
31 # we are building 64-bit binary AND binutils can generate proper code
36 # a. we have AVX512 supported in minimum instruction set
/f-stack/freebsd/contrib/device-tree/Bindings/
H A DABI.rst7 I. Regarding stable bindings/ABI, we quote from the 2013 ARM mini-summit
26 2) Use specific compatible strings so that if we need to add a feature (DMA)
27 in the future, we can create a new compatible string. See I.
/f-stack/freebsd/contrib/device-tree/Bindings/interrupt-controller/
H A Dcsky,mpintc.txt9 0-15 : software irq, and we use 15 as our IPI_IRQ.
10 16-31 : private irq, and we use 16 as the co-processor timer.

12345678910>>...21