| /Linux-v6.6/arch/arm/boot/dts/allwinner/ |
| D | sun8i-a23-polaroid-mid2809pxe04.dts | 4 * This file is dual-licensed: you can use it either under the terms
9 * a) This file is free software; you can redistribute it and/or
14 * This file is distributed in the hope that it will be useful,
21 * b) Permission is hereby granted, free of charge, to any person
25 * copy, modify, merge, publish, distribute, sublicense, and/or
27 * Software is furnished to do so, subject to the following
59 post-power-on-delay-ms = <200>;
|
| D | sun8i-a23-polaroid-mid2407pxe03.dts | 4 * This file is dual-licensed: you can use it either under the terms
9 * a) This file is free software; you can redistribute it and/or
14 * This file is distributed in the hope that it will be useful,
21 * b) Permission is hereby granted, free of charge, to any person
25 * copy, modify, merge, publish, distribute, sublicense, and/or
27 * Software is furnished to do so, subject to the following
59 post-power-on-delay-ms = <200>;
|
| D | sun8i-q8-common.dtsi | 4 * This file is dual-licensed: you can use it either under the terms
9 * a) This file is free software; you can redistribute it and/or
14 * This file is distributed in the hope that it will be useful,
21 * b) Permission is hereby granted, free of charge, to any person
25 * copy, modify, merge, publish, distribute, sublicense, and/or
27 * Software is furnished to do so, subject to the following
76 post-power-on-delay-ms = <200>;
|
| D | sun8i-h3-orangepi-zero-plus2.dts | 5 * This file is dual-licensed: you can use it either under the terms
10 * a) This file is free software; you can redistribute it and/or
15 * This file is distributed in the hope that it will be useful,
22 * b) Permission is hereby granted, free of charge, to any person
26 * copy, modify, merge, publish, distribute, sublicense, and/or
28 * Software is furnished to do so, subject to the following
98 post-power-on-delay-ms = <200>;
168 * port cannot provide power externally even if the board is powered
|
| D | sun8i-h2-plus-orangepi-zero.dts | 4 * Based on sun8i-h3-orangepi-one.dts, which is:
7 * This file is dual-licensed: you can use it either under the terms
12 * a) This file is free software; you can redistribute it and/or
17 * This file is distributed in the hope that it will be useful,
24 * b) Permission is hereby granted, free of charge, to any person
28 * copy, modify, merge, publish, distribute, sublicense, and/or
30 * Software is furnished to do so, subject to the following
59 /* ethernet0 is the H3 emac, defined in sun8i-h3.dtsi */
111 post-power-on-delay-ms = <200>;
203 * USB Type-A port VBUS is always on. However, MicroUSB VBUS can only
[all …]
|
| /Linux-v6.6/arch/arm/boot/dts/nxp/imx/ |
| D | imx6qdl-sr-som-ti.dtsi | 4 * This file is dual-licensed: you can use it either under the terms
9 * a) This file is free software; you can redistribute it and/or
13 * This file is distributed in the hope that it will be useful,
20 * b) Permission is hereby granted, free of charge, to any person
24 * copy, modify, merge, publish, distribute, sublicense, and/or
26 * Software is furnished to do so, subject to the following
54 /* This is a hack around the kernel - using "fixed clock"
72 post-power-on-delay-ms = <200>;
|
| D | imx6qdl-tx6.dtsi | 4 * This file is dual-licensed: you can use it either under the terms
9 * a) This file is free software; you can redistribute it and/or
13 * This file is distributed in the hope that it will be useful,
20 * b) Permission is hereby granted, free of charge, to any person
24 * copy, modify, merge, publish, distribute, sublicense, and/or
26 * Software is furnished to do so, subject to the following
269 phy-reset-post-delay = <10>;
382 /* PAD DISP0_DAT0 is used for the Flexcan transceiver control */
|
| /Linux-v6.6/Documentation/process/ |
| D | maintainer-netdev.rst | 13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
14 - don't post large series (> 15 patches), break them up
21 netdev is a mailing list for all network-related Linux stuff. This
28 The netdev list is managed (like many other Linux mailing lists) through
39 Here is a bit of background information on
41 two week "merge window" where the main maintainers feed their new stuff
43 merge window is closed, and it is called/tagged ``-rc1``. No new
46 rc2 is released. This repeats on a roughly weekly basis until rc7
49 official vX.Y is released.
56 and note the top of the "tags" section. If it is rc1, it is early in
[all …]
|
| D | 5.Posting.rst | 6 Sooner or later, the time comes when your work is ready to be presented to
17 When to post
20 There is a constant temptation to avoid posting patches before they are
21 completely "ready." For simple patches, that is not a problem. If the
22 work being done is complex, though, there is a lot to be gained by getting
23 feedback from the community before the work is complete. So you should
27 When posting code which is not yet considered ready for inclusion, it is a
45 - Make sure your code is compliant with the kernel coding style
49 benchmarks showing what the impact (or benefit) of your change is; a
52 - Be sure that you have the right to post the code. If this work was done
[all …]
|
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
13 It is a rare patch which is so good at its first posting that there is no
15 and, as a result, is heavily oriented toward the improvement of posted
17 kernel community to ensure that your code is up to the kernel's quality
18 standards. A failure to participate in this process is quite likely to
39 - Code review is hard work, and it is a relatively thankless occupation;
40 people remember who wrote kernel code, but there is little lasting fame
44 impulse to respond in kind. Code review is about the code, not about
56 the kernel. One job the maintainers do is to keep things looking
61 What all of this comes down to is that, when reviewers send you comments,
[all …]
|
| D | maintainer-kvm-x86.rst | 18 Testing is mandatory. Be consistent with established styles and patterns.
22 KVM x86 is currently in a transition period from being part of the main KVM
23 tree, to being "just another KVM arch". As such, KVM x86 is split across the
28 main KVM tree, while all development for the next cycle is routed through the
29 KVM x86 tree. In the unlikely event that a fix for the current cycle is routed
33 Note, this transition period is expected to last quite some time, i.e. will be
38 The KVM x86 tree is organized into multiple topic branches. The purpose of
39 using finer-grained topic branches is to make it easier to keep tabs on an area
46 via a Cthulhu merge on an as-needed basis, i.e. when a topic branch is updated.
56 typically the week before Linus' opening of the merge window, e.g. the week
[all …]
|
| D | handling-regressions.rst | 27 is optional, but recommended):
125 All this is expected from you and important when it comes to regression, as
129 these tools is regzbot, which heavily relies on the "Link:" tags to associate
145 should be less than two. And it ought to be just a few days, if the issue is
168 On timing once the culprit of a regression is known:
170 * Aim to mainline a fix within two or three days, if the issue is severe or
176 backport); if the culprit became known early during a week and is simple to
181 regression is something people can live with easily for a while -- like a
185 merge window, except when the fix is extraordinarily risky or when the
206 from the mailing list: he is totally fine with that for uncontroversial
[all …]
|
| D | howto.rst | 6 This is the be-all, end-all document on this topic. It contains
13 to the maintainer of this file, who is listed at the bottom of the
22 device." This document's goal is to teach you everything you need to
27 The kernel is written mostly in C, with some architecture-dependent
28 parts written in assembly. A good understanding of C is required for
29 kernel development. Assembly (any architecture) is not required unless
38 The kernel is written using GNU C and the GNU toolchain. While it
40 not featured in the standard. The kernel is a freestanding C
45 and the extensions that it uses, and unfortunately there is no
50 existing development community. It is a diverse group of people, with
[all …]
|
| D | submitting-patches.rst | 8 with "the system." This text is a collection of suggestions which
41 the tree is not listed there.
48 Describe your problem. Whether your patch is a one-line bug fix or
50 motivated you to do this work. Convince the reviewer that there is a
72 Once the problem is established, describe what you are actually doing
74 in plain English for the reviewer to verify that the code is behaving
87 say that this is version N of the patch (series). Don't expect the
101 the commit, to make it easier for reviewers to know what it is about.
112 there is no collision with your six-character ID now, that condition may
116 can be found on the web, add 'Link:' tags pointing to it. If the patch is a
[all …]
|
| /Linux-v6.6/tools/perf/Documentation/ |
| D | perf-stat.txt | 39 - a raw PMU event in the form of rN where N is a hexadecimal value
52 'percore' is a event qualifier that sums up the event counts for both
66 'uncore_' is also ignored when performing this match.
109 The default path is /sys/fs/bpf/perf_attr_map.
124 system-wide collection from all CPUs (default if no target is specified)
151 In per-thread mode, this option is ignored. The -a option is still necessary
152 to activate system-wide monitoring. Default is to count on all CPUs.
192 monitor only in the container (cgroup) called "name". This option is available only
195 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
196 to first event, second cgroup to second event and so on. It is possible to provide
[all …]
|
| /Linux-v6.6/Documentation/gpu/ |
| D | komeda-kms.rst | 15 architecture. A display pipeline is made up of multiple individual and
24 Layer is the first pipeline stage, which prepares the pixel data for the next
33 The usage of scaler is very flexible and can be connected to layer output
41 frame. its output frame can be fed into post image processor for showing it on
58 Final stage of display pipeline, Timing controller is not for the pixel
68 the result need to be fed to merger to merge two part images together, and then
73 Similar to Layer Split, but Splitter is used for writeback, which splits the
326 pipelines. Since komeda is not for D71 only but also intended for later products,
379 The easiest way is binding a plane to a fixed Layer pipeline, but consider the
384 Layer_Split is quite complicated feature, which splits a big image into two
[all …]
|
| /Linux-v6.6/tools/power/pm-graph/ |
| D | README | 49 This tool suite is designed to assist kernel and OS developers in optimizing
52 and will capture dmesg and ftrace data. This data is transformed into a set of
61 - runs with python2 or python3, choice is made by /usr/bin/python link
112 There is a patch which does this for kernel v3.8.0:
160 timeline. This is useful in discovering dependent threads to get a better
161 idea of what each device is waiting for. For instance, the scsi_eh thread,
162 a.k.a. scsi resume error handler, is what each SATA disk device waits for
179 Proc mode adds user process info to the timeline. This is done in a manner
203 The best way to gauge the health of a system is to run a series of
215 file is a tabular list of the tests with relevant info and links. The
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/ |
| D | hub.fuc | 5 * Permission is hereby granted, free of charge, to any person obtaining a
8 * the rights to use, copy, modify, merge, publish, distribute, sublicense,
10 * Software is furnished to do so, subject to the following conditions:
428 // Not sure how exactly this helps, perhaps "ENABLE" is not such a
447 // Not a clue what this is for, except that unless the value is 0x10, the
448 // strand context is saved (and presumably restored) incorrectly..
668 // post-op
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | makefiles.rst | 21 The top Makefile is responsible for building two major products: vmlinux
62 This document is aimed towards normal developers and arch developers.
76 Section `Goal definitions`_ is a quick intro; further chapters provide
92 This tells kbuild that there is one object in that directory, named
95 If foo.o shall be built as a module, the variable obj-m is used.
96 Therefore the following pattern is often used:
103 If CONFIG_FOO is neither y nor m, then the file will not be compiled
114 ``$(AR) rcSTP`` to merge these files into one built-in.a file.
115 This is a thin archive without a symbol table. It will be later
118 The order of files in $(obj-y) is significant. Duplicates in
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | reporting-issues.rst | 27 <https://kernel.org/>`_. If the issue is present there, send a report.
32 check if backporting is in the works or was discarded; if it's neither, ask
47 Once the report is out, answer any questions that come up and help where you
57 everyone else there is this section. It is more detailed and uses a
64 early if an issue that looks like a Linux kernel problem is actually caused by
119 situations; during the merge window that actually might be even the best
134 details, and at the same time is easy to read and understand for others
141 * If your problem is a regression, try to narrow down when the issue was
154 thing a descriptive title or subject that yet again is shorter. Then you're
157 special care which is explained in 'Special handling for high priority
[all …]
|
| /Linux-v6.6/arch/arm/boot/dts/nvidia/ |
| D | tegra20-asus-tf101.dts | 34 * command line and merge other ATAGS info.
663 /* LDO0 is not connected to anything */
963 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1213 * 1: external that is connected to the CPU's diode
1217 * zone is a simpler solution which prevents TF101 from
1219 * The CPU zone is intended to protect silicon from damage.
1292 post-power-on-delay-ms = <200>;
|
| D | tegra30-asus-nexus7-grouper-common.dtsi | 28 * command line and merge other ATAGS info.
958 * SMB347 INOK input pin is connected to PMIC's
959 * ACOK output, which is fixed to ACTIVE_LOW as
960 * long as battery voltage is in a good range.
1059 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1159 post-power-on-delay-ms = <300>;
1239 * 1: external that is connected to the CPU's diode
1243 * zone is a simpler solution which prevents Nexus 7
1245 * The CPU zone is intended to protect silicon from damage.
|
| D | tegra20-acer-a500-picasso.dts | 33 * command line and merge other ATAGS info.
599 /* LDO0 is not connected to anything */
1195 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1205 * oscillator is used as a reference clock-source by the
1445 * 1: external that is connected to the CPU's diode
1449 * zone is a simpler solution which prevents A500 from
1451 * The CPU zone is intended to protect silicon from damage.
1524 post-power-on-delay-ms = <300>;
|
| D | tegra30-asus-transformer-common.dtsi | 32 * command line and merge other ATAGS info.
1234 /* VDD1 is not used by Transformers */
1298 /* LDO5 is not used by Transformers */
1489 /* PMIC has a built-in 32KHz oscillator which is used by PMC */
1699 * 1: external that is connected to the CPU's diode
1705 * tactile perspective. The CPU zone is intended to
1787 post-power-on-delay-ms = <300>;
|
| /Linux-v6.6/Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-codec.rst | 43 of the available MPEG stream types. This control is specific to
145 MPEG Audio encoding. This control is specific to multiplexed MPEG
393 in stereo. Layer III is not (yet) supported. Possible values are:
457 Mutes the audio when capturing. This is not done by muting audio
508 MPEG Video encoding method. This control is specific to multiplexed
587 the average video bitrate. It is ignored if the video bitrate mode
588 is set to constant bitrate.
591 Constant quality level control. This control is applicable when
592 ``V4L2_CID_MPEG_VIDEO_BITRATE_MODE`` value is
593 ``V4L2_MPEG_VIDEO_BITRATE_MODE_CQ``. Valid range is 1 to 100
[all …]
|
