Home
last modified time | relevance | path

Searched +full:cs +full:- +full:out (Results 1 – 25 of 32) sorted by relevance

12

/Documentation/devicetree/bindings/spi/
Domap-spi.txt4 - compatible :
5 - "ti,am654-mcspi" for AM654.
6 - "ti,omap2-mcspi" for OMAP2 & OMAP3.
7 - "ti,omap4-mcspi" for OMAP4+.
8 - ti,spi-num-cs : Number of chipselect supported by the instance.
9 - ti,hwmods: Name of the hwmod associated to the McSPI
10 - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as
15 - dmas: List of DMA specifiers with the controller specific format
18 - dma-names: List of DMA request names. These strings correspond
28 #address-cells = <1>;
[all …]
/Documentation/devicetree/bindings/arm/
Dcoresight-cti.yaml1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
38 indicate this feature (arm,coresight-cti-v8-arch).
53 constants defined in <dt-bindings/arm/coresight-cti-dt.h>
60 Note that some hardware trigger signals can be connected to non-CoreSight
64 - Mike Leach <mike.leach@linaro.org>
67 - $ref: /schemas/arm/primecell.yaml#
75 - arm,coresight-cti
[all …]
/Documentation/devicetree/bindings/bus/
Dqcom,ebi2.txt4 external memory (such as NAND or other memory-mapped peripherals) whereas
14 and the bus can only come out on these pins, however if some of the pins are
18 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me.
24 CS0 GPIO134 0x1a800000-0x1b000000 (8MB)
25 CS1 GPIO39 (A) / GPIO123 (B) 0x1b000000-0x1b800000 (8MB)
26 CS2 GPIO40 (A) / GPIO124 (B) 0x1b800000-0x1c000000 (8MB)
27 CS3 GPIO133 0x1d000000-0x25000000 (128 MB)
28 CS4 GPIO132 0x1c800000-0x1d000000 (8MB)
29 CS5 GPIO131 0x1c000000-0x1c800000 (8MB)
31 The APQ8060 Qualcomm Application Processor User Guide, 80-N7150-14 Rev. A,
[all …]
/Documentation/devicetree/bindings/rtc/
Dmaxim-ds1302.txt1 * Maxim/Dallas Semiconductor DS-1302 RTC
5 The device uses the standard MicroWire half-duplex transfer timing.
12 - compatible : Should be "maxim,ds1302"
16 - reg : Should be address of the device chip select within
19 - spi-max-frequency : DS-1302 has 500 kHz if powered at 2.2V,
22 - spi-3wire : The device has a shared signal IN/OUT line.
24 - spi-lsb-first : DS-1302 requires least significant bit first
27 - spi-cs-high: DS-1302 has active high chip select line. This is
33 #address-cells = <1>;
34 #size-cells = <0>;
[all …]
/Documentation/scsi/
Dsym53c500_cs.rst1 .. SPDX-License-Identifier: GPL-2.0
7 The sym53c500_cs driver originated as an add-on to David Hinds' pcmcia-cs
14 All the USE_BIOS code has been ripped out. It was never used, and could
25 Through the years, there have been a number of downloads of the pcmcia-cs
Daha152x.rst1 .. SPDX-License-Identifier: GPL-2.0
5 Adaptec AHA-1520/1522 SCSI driver for Linux (aha152x)
8 Copyright |copy| 1993-1999 Jürgen Fischer <fischer@norbit.de>
14 bottom-half handler complete()).
27 IRQ interrupt level (9-12; default 11)
28 SCSI_ID scsi id of controller (0-7; default 7)
42 - DAUTOCONF
43 use configuration the controller reports (AHA-152x only)
45 - DSKIP_BIOSTEST
46 Don't test for BIOS signature (AHA-1510 or disabled BIOS)
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,kirkwood-pinctrl.txt3 Please refer to marvell,mvebu-pinctrl.txt in this directory for common binding
7 - compatible: "marvell,88f6180-pinctrl",
8 "marvell,88f6190-pinctrl", "marvell,88f6192-pinctrl",
9 "marvell,88f6281-pinctrl", "marvell,88f6282-pinctrl",
10 "marvell,98dx4122-pinctrl", "marvell,98dx1135-pinctrl"
11 - reg: register specifier of MPP registers
14 It also support the 88f6281-based variant in the 98dx412x Bobcat SoCs.
24 mpp0 0 gpio, nand(io2), spi(cs)
30 mpp6 6 sysrst(out), spi(mosi), ptp(trig)
31 mpp7 7 gpo, pex(rsto), spi(cs), ptp(trig)
[all …]
/Documentation/devicetree/bindings/mtd/
Dfsl-upm-nand.txt4 - compatible : "fsl,upm-nand".
5 - reg : should specify localbus chip select and size used for the chip.
6 - fsl,upm-addr-offset : UPM pattern offset for the address latch.
7 - fsl,upm-cmd-offset : UPM pattern offset for the command latch.
10 - fsl,upm-addr-line-cs-offsets : address offsets for multi-chip support.
12 - gpios : may specify optional GPIOs connected to the Ready-Not-Busy pins
13 (R/B#). For multi-chip devices, "n" GPIO definitions are required
17 - fsl,upm-wait-flags : add chip-dependent short delays after running the
19 writing out a buffer (0x4).
20 - chip-delay : chip dependent delay for transferring data from array to
[all …]
/Documentation/devicetree/bindings/net/nfc/
Dst95hf.txt11 - reg: Address of SPI slave "ST95HF transceiver" on SPI master bus.
13 - compatible: should be "st,st95hf" for ST95HF NFC transceiver
15 - spi-max-frequency: Max. operating SPI frequency for ST95HF
18 - enable-gpio: GPIO line to enable ST95HF transceiver.
20 - interrupts : Standard way to define ST95HF transceiver's out
25 - st95hfvin-supply : This is an optional property. It contains a
32 #address-cells = <1>;
33 #size-cells = <0>;
34 cs-gpios = <&pio0 4>;
39 spi-max-frequency = <1000000>;
[all …]
/Documentation/devicetree/bindings/leds/backlight/
Dqcom-wled.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/qcom-wled.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
11 - Kiran Gunda <kgunda@codeaurora.org>
21 - qcom,pm8941-wled
22 - qcom,pmi8998-wled
23 - qcom,pm660l-wled
24 - qcom,pm8150l-wled
[all …]
/Documentation/usb/
DCREDITS7 Georg Acher <acher@informatik.tu-muenchen.de>
15 Greg Kroah-Hartman <greg@kroah.com>
17 Paul Mackerras <paulus@cs.anu.edu.au>
24 Linus Torvalds <torvalds@linux-foundation.org>
44 - 3Com GmbH for donating a ISDN Pro TA and supporting me
48 - USAR Systems provided us with one of their excellent USB
49 Evaluation Kits. It allows us to test the Linux-USB driver
51 Systems recognized the importance of an up-to-date open
55 - Thanks to Intel Corporation for their precious help.
57 - We teamed up with Cherry to make Linux the first OS with
[all …]
/Documentation/networking/device_drivers/wifi/
Dray_cs.rst1 .. SPDX-License-Identifier: GPL-2.0
27 The kernel driver is based on ray_cs-1.62.tgz
33 This will change after the method of sorting out parameters for all
41 http://pcmcia-cs.sourceforge.net/
45 pcmcia-cs-3.1.1 or greater is required for the kernel version of
83 beacon_period integer beacon period in Kilo-microseconds,
99 essid string ESS ID - network name to join
104 hop_dwell integer hop dwell time in Kilo-microseconds
125 pc_debug integer (0-5) larger values for more verbose
/Documentation/devicetree/bindings/pci/
Dnvidia,tegra20-pcie.txt4 - compatible: Must be:
5 - "nvidia,tegra20-pcie": for Tegra20
6 - "nvidia,tegra30-pcie": for Tegra30
7 - "nvidia,tegra124-pcie": for Tegra124 and Tegra132
8 - "nvidia,tegra210-pcie": for Tegra210
9 - "nvidia,tegra186-pcie": for Tegra186
10 - power-domains: To ungate power partition by BPMP powergate driver. Must
13 - device_type: Must be "pci"
14 - reg: A list of physical base address and length for each set of controller
15 registers. Must contain an entry for each entry in the reg-names property.
[all …]
/Documentation/filesystems/
Dcoda.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
14 http://www.coda.cs.cmu.edu
18 ftp://ftp.coda.cs.cmu.edu
35 level filesystem code needed for the operation of the Coda file sys-
124 leads to an almost natural environment for implementing a kernel-level
153 pre-processing, the VFS starts invoking exported routines in the FS
208 up processes. The Coda FS driver processes VFS- and pioctl-requests
220 memory for the request. Since the data buffer is re-used to hold the
[all …]
Dubifs-authentication.rst1 .. SPDX-License-Identifier: GPL-2.0
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
44 ----------------
50 addition, it deals with flash-specific wear-leveling and transparent I/O error
60 +------------+ +*******+ +-----------+ +-----+
61 | | * UBIFS * | UBI-BLOCK | | ... |
[all …]
/Documentation/kbuild/
Dkconfig-language.rst6 ------------
11 +- Code maturity level options
12 | +- Prompt for development and/or incomplete code/drivers
13 +- General setup
14 | +- Networking support
15 | +- System V IPC
16 | +- BSD Process Accounting
17 | +- Sysctl support
18 +- Loadable module support
19 | +- Enable loadable module support
[all …]
/Documentation/process/
Dkernel-docs.rst6 Juan-Mariano de Goyeneche <jmseyas@dit.upm.es>
9 linux-kernel mailing list as the same questions, asking for pointers
18 start. And, even if they exist, there was no "well-known" place which
24 send me an e-mail, and I'll include a reference to it here. Any
41 -----------------------------
55 On-line docs
56 ------------
63 :Keywords: glossary, terms, linux-kernel.
79 Having obtained a trace-log a kernel hacker can read and understand
83 Finally this trace-log is used as base for more a exact conceptual
[all …]
Dmaintainer-pgp-guide.rst12 Linux Foundation. Please read that document for more in-depth discussion
15 .. _`Protecting Code Integrity`: https://github.com/lfit/itpol/blob/master/protecting-code-integrit…
22 communication channels between developers via PGP-signed email exchange.
26 - Distributed source repositories (git)
27 - Periodic release snapshots (tarballs)
35 - git repositories provide PGP signatures on all tags
36 - tarballs provide detached PGP signatures with all downloads
41 -------------------------------------------
64 ------------
68 release -- many distributions still package both, with the default
[all …]
/Documentation/RCU/
DRTFP.txt4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]
/Documentation/arm/sa1100/
Dassabet.rst2 The Intel Assabet (SA-1110 evaluation) board
9 http://www.cs.cmu.edu/~wearable/software/assabet.html
13 -------------------
25 -----------------------
39 John Dorsey has produced add-on patches to add support for Assabet and
55 - ftp://ftp.netwinder.org/users/n/nico/
56 - ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/
57 - ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
59 Look for redboot-assabet*.tgz. Some installation infos are provided in
60 redboot-assabet*.txt.
[all …]
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst13 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier
14 third RCU-bh flavor having been implemented in terms of the other two.
38 RCU-preempt Expedited Grace Periods
41 ``CONFIG_PREEMPT=y`` kernels implement RCU-preempt.
42 The overall flow of the handling of a given CPU by an RCU-preempt
45 .. kernel-figure:: ExpRCUFlow.svg
59 can check to see if the CPU is currently running in an RCU read-side
63 invocation will provide the needed quiescent-state report.
64 This flag-setting avoids the previous forced preemption of all
65 CPUs that might have RCU read-side critical sections.
[all …]
/Documentation/timers/
Dhighres.rst8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
41 - independent of ticks (the processing is based on nanoseconds)
[all …]
/Documentation/staging/
Dstatic-keys.rst30 performance-sensitive fast-path kernel code, via a GCC feature and a code
74 https://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html
77 by default, without the need to check memory. Then, at run-time, we can patch
86 consist of a single atomic 'no-op' instruction (5 bytes on x86), in the
87 straight-line code path. When the branch is 'flipped', we will patch the
88 'no-op' in the straight-line codepath with a 'jump' instruction to the
89 out-of-line true branch. Thus, changing branch direction is expensive but
110 allocated at run-time.
186 struct jump_entry table must be at least 4-byte aligned because the
187 static_key->entry field makes use of the two least significant bits.
[all …]
/Documentation/admin-guide/
Dsvga.rst7 :Copyright: |copy| 1995--1999 Martin Mares, <mj@ucw.cz>
22 remember its mode ID (the four-digit hexadecimal number) and then
31 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
33 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
35 ASK_VGA - Display a video mode menu upon startup (see below).
37 0..35 - Menu item number (when you have used the menu to view the list of
41 modes are listed in a "first detected -- first displayed" manner. It's
44 0x.... - Hexadecimal video mode ID (also displayed on the menu, see below
46 hexadecimal numbers -- you have to convert it to decimal manually.
59 Video adapter: <name-of-detected-video-adapter>
[all …]
/Documentation/spi/
Dspi-summary.rst5 02-Feb-2012
8 ------------
15 and parallel data lines with "Master Out, Slave In" (MOSI) or "Master In,
16 Slave Out" (MISO) signals. (Other names are also used.) There are four
17 clocking modes through which data is exchanged; mode-0 and mode-3 are most
18 commonly used. Each clock cycle shifts data out and data in; the clock
32 - SPI may be used for request/response style device protocols, as with
35 - It may also be used to stream data in either direction (half duplex),
38 - Some devices may use eight bit words. Others may use different word
39 lengths, such as streams of 12-bit or 20-bit digital samples.
[all …]

12