Searched +full:xmem +full:- +full:adv +full:- +full:to +full:- +full:oe +full:- +full:recovery +full:- +full:cycles (Results 1 – 2 of 2) sorted by relevance
| /freebsd/sys/contrib/device-tree/Bindings/bus/ |
| H A D | qcom,ebi2.txt | 3 The EBI2 contains two peripheral blocks: XMEM and LCDC. The XMEM handles any
4 external memory (such as NAND or other memory-mapped peripherals) whereas
7 As it says it connects devices to an external bus interface, meaning address
8 lines (up to 9 address lines so can only address 1KiB external memory space),
9 data lines (16 bits), OE (output enable), ADV (address valid, used on some
15 unused they can be left unconnected or remuxed to be used as GPIO or in some
18 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me.
21 memory is referred to as "Chip Peripheral SS FPB0" and is 168MB big.
24 CS0 GPIO134 0x1a800000-0x1b000000 (8MB)
25 CS1 GPIO39 (A) / GPIO123 (B) 0x1b000000-0x1b800000 (8MB)
[all …]
|
| H A D | qcom,ebi2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The EBI2 contains two peripheral blocks: XMEM and LCDC. The XMEM handles any
11 external memory (such as NAND or other memory-mapped peripherals) whereas
14 As it says it connects devices to an external bus interface, meaning address
15 lines (up to 9 address lines so can only address 1KiB external memory space),
16 data lines (16 bits), OE (output enable), ADV (address valid, used on some
22 unused they can be left unconnected or remuxed to be used as GPIO or in some
25 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me.
[all …]
|