| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
20 supplying power to the system (unless some non-Linux
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/staging/media/atomisp/ |
| H A D | TODO | 5 V4L2 driver, there are still some issues preventing it to
7 Didn't test yet with some custom-made app for this driver).
16 There are some hacks added there for it to wait for sensors to be
64 cause some breakages.
66 6. There is some issues at the frame receive logic, causing the
72 two using several runtime macros, plus some ifdef ISP2401 to select the
73 CHT version. Yet, there are some ISP-specific headers that change the
81 10. The AtomISP driver includes some special IOCTLS (ATOMISP_IOC_XXXX_XXXX)
82 and controls that require some cleanup. Some of those code may have
89 11. The ISP code has some dependencies of the exact FW version.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| H A D | ChangeLog.ncr53c8xx | 55 that supply SCSI_DATA_NONE direction (this avoids some BUG()
74 * And some other ...
91 * And some other ...
131 some minor changes. The driver can now attach any number of
150 - Add support of some 'resource handling' for linux-2.3.13.
153 - Remove some deprecated code.
162 - Some additions to the README.ncr53c8xx file.
187 - Fix some oooold bug that hangs the bus if a device rejects a
188 negotiation. Btw, the corresponding stuff also needed some cleanup
190 - Still some typo that made compilation fail for 64 bit (trivial fix).
[all …]
|
| H A D | ChangeLog.sym53c8xx | 133 that supply SCSI_DATA_NONE direction (this avoids some BUG()
160 chips will check parity in some special circumstances.
203 - Some fix for Sparc from DSM that went directly to kernel tree.
213 - Some fixes in the MODIFY_DP/IGN_RESIDUE code and residual
241 - Backport some minor improvements of SCRIPTS from the sym_hipd
255 - Work-around PCI chips being reported twice on some platforms.
256 - Add some redundant PCI reads in order to deal with common
258 - Add some other conditionnal code for people who have to deal
270 - Fix some bug in the fully untested MDP handling:) and share
271 some code between MDP handling and residual calculation.
[all …]
|
| /OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/haswell/ |
| H A D | uncore.json | 7 "BriefDescription": "An external snoop misses in some processor core.",
8 "PublicDescription": "An external snoop misses in some processor core.",
19 … initiated by this Cbox due to processor core memory request which misses in some processor core.",
20 … initiated by this Cbox due to processor core memory request which misses in some processor core.",
31 …"BriefDescription": "A cross-core snoop resulted from L3 Eviction which misses in some processor c…
32 …"PublicDescription": "A cross-core snoop resulted from L3 Eviction which misses in some processor …
43 "BriefDescription": "An external snoop hits a non-modified line in some processor core.",
44 "PublicDescription": "An external snoop hits a non-modified line in some processor core.",
55 … Cbox due to processor core memory request which hits a non-modified line in some processor core.",
56 … Cbox due to processor core memory request which hits a non-modified line in some processor core.",
[all …]
|
| /OK3568_Linux_fs/kernel/include/linux/clk/ |
| H A D | at91_pmc.h | 53 #define AT91_CKGR_UCKR 0x1C /* UTMI Clock Register [some SAM9] */
69 #define AT91_PMC_MOSCRCEN (1 << 3) /* Main On-Chip RC Oscillator Enable [some SAM9] */
73 #define AT91_PMC_MOSCSEL (1 << 24) /* Main Oscillator Selection [some SAM9] */
74 #define AT91_PMC_CFDEN (1 << 25) /* Clock Failure Detector Enable [some SAM9] */
103 #define AT91_PMC_CSS_UPLL (3 << 0) /* [some SAM9 only] */
130 #define AT91SAM9_PMC_MDIV_6 (3 << 8) /* [some SAM9 only] */
131 #define AT91SAM9_PMC_MDIV_3 (3 << 8) /* [some SAM9 only] */
132 #define AT91_PMC_PDIV (1 << 12) /* Processor Clock Division [some SAM9 only] */
135 #define AT91_PMC_PLLADIV2 (1 << 12) /* PLLA divisor by 2 [some SAM9 only] */
142 #define AT91_PMC_USB 0x38 /* USB Clock Register [some SAM9 only] */
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/index/ |
| H A D | distance_predicates.hpp | 60 \tparam T Type of wrapped object. This may be a Point for PointRelation or some CoordinateType for
83 \tparam T Type of wrapped object. This may be a Point for PointRelation or some CoordinateType for
125 Indexable are greater or equal to some min_distance passed in MinRelation. Check for closest Value …
126 defined by PointRelation. So it is possible e.g. to return Values with centroids closest to some
127 Point but only if nearest points are further than some distance.
151 Indexable are lesser or equal to some max_distance passed in MaxRelation. Check for closest Value is
152 defined by PointRelation. So it is possible e.g. to return Values with centroids closest to some
153 Point but only if nearest points are closer than some distance.
177 Indexable are greater or equal to some min_distance passed in MinRelation and lesser or equal to
178 some max_distance passed in MaxRelation. Check for closest Value is defined by PointRelation.
[all …]
|
| /OK3568_Linux_fs/kernel/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | floating-point.json | 16 …omputational scalar double precision floating-point instructions retired; some instructions will c…
23 …omputational scalar double precision floating-point instructions retired; some instructions will c…
27 …omputational scalar single precision floating-point instructions retired; some instructions will c…
34 …omputational scalar single precision floating-point instructions retired; some instructions will c…
38 …onal 128-bit packed double precision floating-point instructions retired; some instructions will c…
45 …onal 128-bit packed double precision floating-point instructions retired; some instructions will c…
49 …onal 128-bit packed single precision floating-point instructions retired; some instructions will c…
56 …onal 128-bit packed single precision floating-point instructions retired; some instructions will c…
60 …onal 256-bit packed double precision floating-point instructions retired; some instructions will c…
67 …onal 256-bit packed double precision floating-point instructions retired; some instructions will c…
[all …]
|
| /OK3568_Linux_fs/u-boot/lib/lzma/ |
| H A D | history.txt | 12 if more than 10 threads were used (or more than 20 threads in some modes).
25 - Some bugs were fixed
30 - Some changes in ANSI-C 7z Decoder interfaces.
41 - Some minor fixes
46 - Some minor fixes
54 - Some changes in ANSI-C 7z Decoder interfaces.
60 - Some minor fixes.
67 allocated range in some rare cases.
80 - Small changes for more compatibility with some C/C++ compilers.
95 - Small changes for more compatibility with some C/C++ compilers.
[all …]
|
| /OK3568_Linux_fs/kernel/include/linux/mfd/ |
| H A D | tmio.h | 40 * Some controllers can support a 2-byte block size when the bus width
45 * Some controllers can support SDIO IRQ signalling.
49 /* Some features are only available or tested on R-Car Gen2 or later */
53 * Some controllers require waiting for the SD bus to become
54 * idle before writing to some registers.
61 * Some controllers have CMD12 automatically
66 /* Controller has some SDIO status bits which must be 1 */
70 * Some controllers have a 32-bit wide data port register
75 * Some controllers allows to set SDx actual clock
79 /* Some controllers have a CBSY bit */
|
| /OK3568_Linux_fs/buildroot/support/download/ |
| H A D | helpers | 15 # - some temporary files are created in CWD, and removed at the end
20 # /path/to/temp/dir/some-file
21 # /path/to/temp/dir/some-dir/
22 # /path/to/temp/dir/some-dir/some-other-file
24 # $ mk_tar_gz /path/to/some/dir \
31 # foo_bar-1.2.3/some-file
32 # foo_bar-1.2.3/some-dir/some-other-file
|
| /OK3568_Linux_fs/kernel/drivers/scsi/ufs/ |
| H A D | ufs_quirks.h | 42 * Some vendor's UFS device sends back to back NACs for the DL data frames
60 * If DL NAC error is seen multiple times with some vendor's UFS devices then
76 * It seems some UFS devices may keep drawing more than sleep current
84 * Some UFS devices require host PA_TACTIVATE to be lower than device
91 * some vendors.
100 * Some UFS devices require VS_DebugSaveConfigTime is 0x10,
106 * Some pre-3.1 UFS devices can support extended features by upgrading
113 * Some UFS devices require delay after VCC power rail is turned-off.
120 * Some UFS devices require L2P entry should be swapped before being sent to the
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/laptops/ |
| H A D | sonypi.rst | 13 can be found in many Sony Vaio laptops. Some newer Sony laptops (seems to be
17 It will give access (through a user space utility) to some events those laptops
35 This driver supports also some ioctl commands for setting the LCD screen
36 brightness and querying the batteries charge information (some more
64 fnkeyinit: on some Vaios (C1VE, C1VR etc), the Fn key events don't
67 some Vaio models don't deal well with this option.
78 compat: uses some compatibility code for enabling the sonypi
85 some Vaio models where the hardware reuses values
139 - some users reported that the laptop speed is lower (dhrystone
148 events on some models.
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/media/ |
| H A D | faq.rst | 13 2. The LinuxTV community maintains some Wiki pages with contain
21 Some very frequently asked questions about Linux Digital TV support
35 some simple utilities which are mainly intended for testing
53 There are some other applications like ``w_scan`` [#]_ that do a
59 Also, some applications like ``kaffeine`` have their own code
74 Kaffeine has some blind scan support for some terrestrial standards.
84 scanning tool to identify the other channels. On some places,
107 Some of the most popular ones are linked below:
156 cabling. Yet, it could also be some hardware or driver issue.
162 Please see the FAQ page at linuxtv.org, as it could contain some
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/vm/ |
| H A D | numa.rst | 20 of the system--although some components necessary for a stand-alone SMP system
22 connected together with some sort of system interconnect--e.g., a crossbar or
50 of the hardware platform, abstracting away some of the details for some
57 For some architectures, such as x86, Linux will "hide" any node representing a
63 In addition, for some architectures, again x86 is an example, Linux supports
81 Because some nodes contain multiple zones containing different types of
84 type on the same node. This is an important consideration because some zones,
99 as long as the task on whose behalf the kernel allocated some memory does not
129 Some kernel allocations do not want or cannot tolerate this allocation fallback
145 or some subsystems would fail to initialize if they attempted to allocated
|
| /OK3568_Linux_fs/external/security/rk_tee_user/v2/host/openssl/include/openssl/ |
| H A D | symhacks.h | 139 /* Hack some long X509 names */
151 /* Hack some long CRYPTO names */
169 /* Hack some long SSL/TLS names */
235 /* Hack some RSA long names */
239 /* Hack some ENGINE long names */
262 /* Hack some long OCSP names */
270 /* Hack some long DES names */
276 /* Hack some long EVP names */
286 /* Hack some long EC names */
429 /* Hack some long TS names */
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | svga.rst | 27 option of LILO (or some other boot loader you use) or by the "xrandr" utility
83 The mode list usually contains a few basic modes and some VESA modes. In
84 case your chipset has been detected, some chipset-specific modes are shown as
85 well (some of these might be missing or unusable on your machine as different
97 what happens then. The screen will be probably flashing wildly for some time and
99 all consistent video modes supported by your BIOS will appear (plus maybe some
156 eliminate some annoying bugs of certain VGA BIOSes (usually those used for
177 the machine hangs instead of displaying the menu), try to switch off some of
184 If you start Linux from M$-DOS, you might also use some DOS tools for
189 If you set some extended mode and there's one or more extra lines on the
[all …]
|
| /OK3568_Linux_fs/buildroot/arch/ |
| H A D | Config.in.arm | 5 # for some cores, NEON support is optional
9 # For some cores, the FPU is optional
16 # for some cores, VFPv2 is optional
25 # for some cores, VFPv3 is optional
34 # for some cores, VFPv4 is optional
553 For some CPU cores, the NEON SIMD extension is optional.
566 For some CPU cores, the VFP extension is optional. Select
594 built 'soft' with some other code built 'softfp'.
658 available in some ARMv5 processors (ARM926EJ-S) and some
671 available in some ARMv7 processors (Cortex-A{8, 9}). This
[all …]
|
| /OK3568_Linux_fs/u-boot/tools/patman/test/ |
| H A D | test01.txt | 7 This gives a warning with some native compilers:
17 some notes
18 about some things
23 Some notes about
33 This gives a warning with some native compilers:
49 - Some changes
|
| /OK3568_Linux_fs/kernel/arch/arm/include/asm/ |
| H A D | dma.h | 65 * Some architectures may need to do allocate an interrupt
71 * Some architectures may need to do free an interrupt
77 * On some architectures, this may have other side effects like
84 * On some architectures, this may have other side effects like
96 * especially since some DMA architectures don't update the
104 * especially since some DMA architectures don't update the
114 * especially since some DMA architectures don't update the
122 * especially since some DMA architectures don't update the
|
| /OK3568_Linux_fs/u-boot/drivers/reset/ |
| H A D | Kconfig | 8 modules are equipped with a reset signal, typically driven by some
10 controller drivers allow control over these reset signals. In some
20 modules are equipped with a reset signal, typically driven by some
22 controller drivers allow control over these reset signals. In some
80 is that some reset signals, like I2C or MISC reset multiple devices.
88 is that some reset signals, like I2C or MISC reset multiple devices.
95 is that some reset signals, like I2C or MISC reset multiple devices.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | msi.txt | 12 MSIs are distinguished by some combination of:
35 address by some master. An MSI controller may feature a number of doorbells.
87 compatible = "vendor-a,some-controller";
96 /* Each device has some unique ID */
104 /* Each device has some unique ID */
110 compatible = "vendor-c,some-device";
118 compatible = "vendor-c,some-device";
128 compatible = "vendor-c,some-device";
|
| /OK3568_Linux_fs/kernel/fs/affs/ |
| H A D | Changes | 3 things that can be used since quite some time. But
18 blocks (some very old SCSI drives).
81 - cleanup of some interfaces
118 - Added a few comments, fixed some typos (and
119 introduced some new ones), made the debug messages
150 - Removed some unnecessary locks as Bill
176 - Remove some more superfluous code left over from
179 - Fixed some oversights which were in patch 2.1.78.
203 - Fixed some oversights (version wasn't updated on some
211 effort. This also led to some code cleanup.
[all …]
|
| /OK3568_Linux_fs/u-boot/common/ |
| H A D | Kconfig | 93 Some OSes do not support device tree. Bootstage can instead write
136 booted via NAND flash. This is not a must, some SoCs need this,
137 some not.
144 booted via ONENAND. This is not a must, some SoCs need this,
145 some not.
152 booted via QSPI flash. This is not a must, some SoCs need this,
153 some not.
160 booted via SATA. This is not a must, some SoCs need this,
161 some not.
168 booted via SD/EMMC. This is not a must, some SoCs need this,
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/i2c/ |
| H A D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
29 some positive number indicating a non-fault return. The specific
44 transmit mode: some other master was transmitting different
48 atomic context, when some task is already using that I2C bus
49 to execute some other operation.
62 than allowed. This usually indicates some device (maybe the
63 SMBus adapter) needs some fault recovery (such as resetting),
130 timeouts, but it's normal for I2C adapters to impose some
|