Home
last modified time | relevance | path

Searched +full:pulled +full:- +full:up (Results 1 – 25 of 25) sorted by relevance

/Documentation/devicetree/bindings/sound/
Deverest,es7241.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Neil Armstrong <neil.armstrong@linaro.org>
15 - everest,es7241
17 reset-gpios:
21 m0-gpios:
25 m1-gpios:
29 everest,sdout-pull-down:
33 the sdout. If the sdout is pulled down, leftj format is used.
[all …]
/Documentation/devicetree/bindings/iio/light/
Dveml6030.yaml1 # SPDX-License-Identifier: GPL-2.0+
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rishi Gupta <gupt21@gmail.com>
28 - vishay,veml6030
34 - 0x10 # ADDR pin pulled down
35 - 0x48 # ADDR pin pulled up
40 Refer to interrupt-controller/interrupts.txt for generic
45 - compatible
46 - reg
[all …]
/Documentation/process/
D7.AdvancedTopics.rst12 -------------------------
30 wish to come up to speed with git will find more information at:
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
40 available to others. A git-using developer should be able to obtain a copy
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
50 exercise while coming up to speed.
52 When you are ready to start putting up git trees for others to look at, you
53 will, of course, need a server that can be pulled from. Setting up such a
54 server with git-daemon is relatively straightforward if you have a system
[all …]
D6.Followthrough.rst17 kernel community to ensure that your code is up to the kernel's quality
23 ----------------------
31 - If you have explained your patch well, reviewers will understand its
35 Many of the changes you may be asked to make - from coding style tweaks
36 to substantial rewrites - come from the understanding that Linux will
39 - Code review is hard work, and it is a relatively thankless occupation;
47 - Similarly, code reviewers are not trying to promote their employers'
54 - Be prepared for seemingly silly requests for coding style changes
82 can help future reviewers avoid the questions which came up the first time
112 -----------------
[all …]
Dhowto.rst6 This is the be-all, end-all document on this topic. It contains
18 ------------
27 The kernel is written mostly in C, with some architecture-dependent
30 you plan to do low-level development for that architecture. Though they
34 - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
35 - "Practical C Programming" by Steve Oualline [O'Reilly]
36 - "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
60 ------------
65 described in :ref:`Documentation/process/license-rules.rst <kernel_licensing>`.
72 https://www.gnu.org/licenses/gpl-faq.html
[all …]
Dmaintainer-netdev.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. _netdev-FAQ:
10 -----
12 - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
14 - don't post large series (> 15 patches), break them up
15 - don't repost your patches within one 24h period
16 - reverse xmas tree
19 ------
21 netdev is a mailing list for all network-related Linux stuff. This
[all …]
Dbackporting.rst1 .. SPDX-License-Identifier: GPL-2.0
18 merging branches, or resolving conflicts in their day-to-day work, so
19 when a merge conflict does pop up, it can be daunting. Luckily,
24 This document aims to be a comprehensive, step-by-step guide to
31 in which case you just cherry-pick it directly using
32 ``git cherry-pick``. However, if the patch comes from an email, as it
42 where the patch applies cleanly and *then* cherry-pick it over to your
47 can apply it to the most recent mainline kernel and then cherry-pick it
54 in more unrelated changes in the context of the diff when cherry-picking
57 A good reason to prefer ``git cherry-pick`` over ``git am`` is that git
[all …]
Dsubmitting-patches.rst13 works, see Documentation/process/development-process.rst. Also, read
14 Documentation/process/submit-checklist.rst
17 Documentation/devicetree/bindings/submitting-patches.rst.
20 If you're unfamiliar with ``git``, you would be well-advised to learn how to
26 :ref:`Documentation/process/maintainer-handbooks.rst <maintainer_handbooks_main>`.
29 ----------------------------
46 ---------------------
48 Describe your problem. Whether your patch is a one-line bug fix or
54 Describe user-visible impact. Straight up crashes and lockups are
59 vendor/product-specific trees that cherry-pick only specific patches
[all …]
/Documentation/devicetree/bindings/gpio/
Dnxp,pcf8575.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: PCF857x-compatible I/O expanders
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
13 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be
14 driven high by a pull-up current source or driven low to ground. This
20 setting up line direction is thus to do it explicitly.
25 - maxim,max7328
26 - maxim,max7329
[all …]
/Documentation/devicetree/bindings/usb/
Dsamsung,exynos-usb2.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/samsung,exynos-usb2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - samsung,exynos4210-ehci
16 - samsung,exynos4210-ohci
21 clock-names:
23 - const: usbhost
32 phy-names:
[all …]
/Documentation/devicetree/bindings/leds/
Dkinetic,ktd2692.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Markuss Broks <markuss.broks@gmail.com>
13 KTD2692 is the ideal power solution for high-power flash LEDs.
14 It uses ExpressWire single-wire programming for maximum flexibility.
20 Also, When the AUX pin is pulled high while CTRL pin is high,
21 LED current will be ramped up to the flash-mode current level.
27 ctrl-gpios:
31 aux-gpios:
[all …]
/Documentation/power/
Dcharger-manager.rst7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
34 battery temperature. We can accomplish this by waking up the system
[all …]
/Documentation/maintainer/
Drebasing-and-merging.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Git source-code management system. Git is a powerful tool with a lot of
30 - Changing the parent (starting) commit upon which a series of patches is
36 - Changing the history of a set of patches by fixing (or deleting) broken
48 - History that has been exposed to the world beyond your private system
49 should usually not be changed. Others may have pulled a copy of your
54 That said, there are always exceptions. Some trees (linux-next being
61 - Do not rebase a branch that contains history created by others. If you
62 have pulled changes from another developer's repository, you are now a
67 - Do not reparent a tree without a good reason to do so. Just being on a
[all …]
Dpull-requests.rst9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
36 named ``char-misc-next``, you would be using the following command::
38 git tag -s char-misc-4.15-rc1 char-misc-next
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
41 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
42 (see Documentation/maintainer/configure-git.rst).
50 any, testing has been done. All of this information will end up in the tag
[all …]
Dmessy-diffstat.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Handling messy pull-request diffstats
7 Subsystem maintainers routinely use ``git request-pull`` as part of the
14 and how to fix things up; it is derived from The Wisdom of Linus Torvalds,
17 .. _Linus1: https://lore.kernel.org/lkml/CAHk-=wg3wXH2JNxkQi+eLZkpuxqV+wPiHhw_Jf7ViH33Sw7PHA@mail.g…
18 .. _Linus2: https://lore.kernel.org/lkml/CAHk-=wgXbSa8yq8Dht8at+gxb_idnJ7X5qWZQWRBN4_CUPr=eQ@mail.g…
23 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
28 $ git diff --stat --summary vN-rc2..vN-rc3
38 ... vM --- vN-rc1 --- vN-rc2 --- vN-rc3 --- ... --- vN-rc7 --- vN
40 +-- c1 --- c2 --- ... --- cN
[all …]
/Documentation/devicetree/bindings/mfd/
Dsamsung,s2mps11.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
18 sub-blocks.
23 - samsung,s2mps11-pmic
24 - samsung,s2mps13-pmic
25 - samsung,s2mps14-pmic
26 - samsung,s2mps15-pmic
27 - samsung,s2mpu02-pmic
[all …]
/Documentation/doc-guide/
Dcontributing.rst1 .. SPDX-License-Identifier: GPL-2.0
6 Documentation is an important part of any software-development project.
8 developers work more effectively. Without top-quality documentation, a lot
9 of time is wasted in reverse-engineering the code and making avoidable
23 ---------------------------
36 ones. For this reason, eliminating warnings is one of the highest-priority
42 positives, leading to patches aimed at simply shutting the compiler up.
59 - Resource-managed devfreq_register_notifier()
61 - Resource-managed devfreq_unregister_notifier()
65 A quick look at the source file named above turned up a couple of kerneldoc
[all …]
/Documentation/i2c/
Dgpio-fault-injection.rst12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually
15 injection. They will be described now along with their intended use-cases.
21 -----
31 -----
56 --------------------------
62 being pulled low by the device while SCL is high. So, similar to the "sda" file
68 -----------------------
80 This is a highly delicate state, the device is set up to write any data to
82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
90 bus arbitration against another master in a multi-master setup.
[all …]
/Documentation/scsi/
DChangeLog.sym53c8xx_22 * version sym-2.1.0-20001230
3 - Initial release of SYM-2.
6 * version sym-2.1.1-20010108
7 - Change a couple of defines containing ncr or NCR by their
11 * version sym-2.1.2-20010114
12 - Fix a couple of printfs:
17 * version sym-2.1.3-20010117
18 - Wrong residual values were returned in some situations.
19 This broke cdrecord with linux-2.4.0, for example.
22 * version sym-2.1.4-20010120
[all …]
DChangeLog.lpfc2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
26 * Added PCI ID for LP10000-S.
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
33 - was causing spurious 0710 messages.
55 - stop using volatile. if you need special ordering use memory
57 - switch lpfc_sli_pcimem_bcopy to take void * arguments.
58 - remove typecast for constants - a U postfix marks them
60 - add a MAILBOX_CMD_SIZE macro, as most users of
[all …]
Dncr53c8xx.rst1 .. SPDX-License-Identifier: GPL-2.0
11 95170 DEUIL LA BARRE - FRANCE
57 10.2.17 Fix up PCI configuration space
64 10.4 PCI configuration fix-up boot option
81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers
82 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers
97 - Gerard Roudier <groudier@free.fr>
101 - Wolfgang Stanglmeier <wolf@cologne.de>
102 - Stefan Esser <se@mi.Uni-Koeln.de>
106 - ncr53c8xx generic driver that supports all the SYM53C8XX family including
[all …]
/Documentation/driver-api/gpio/
Ddriver.rst26 between 0 and n-1, n being the number of GPIOs managed by the chip.
29 example if a system uses a memory-mapped set of I/O-registers where 32 GPIO
30 lines are handled by one bit per line in a 32-bit register, it makes sense to
44 So for example one platform could use global numbers 32-159 for GPIOs, with a
46 global numbers 0..63 with one set of GPIO controllers, 64-79 with another type
47 of GPIO controller, and on one particular board 80-95 with an FPGA. The legacy
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
60 - methods to establish GPIO line direction
61 - methods used to access GPIO line values
62 - method to set electrical configuration for a given GPIO line
[all …]
/Documentation/bpf/
Dbpf_devel_QA.rst10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
68 Note furthermore that both base branches (bpf-next_base and bpf_base) will be
[all …]
/Documentation/admin-guide/sysctl/
Dvm.rst13 ------------------------------------------------------------------------------
27 - admin_reserve_kbytes
28 - compact_memory
29 - compaction_proactiveness
30 - compact_unevictable_allowed
31 - dirty_background_bytes
32 - dirty_background_ratio
33 - dirty_bytes
34 - dirty_expire_centisecs
35 - dirty_ratio
[all …]
/Documentation/gpu/
Ddrm-vm-bind-locking.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR MIT)
30 meta-data. Typically one per client (DRM file-private), or one per
33 associated meta-data. The backing storage of a gpu_vma can either be
34 a GEM object or anonymous or page-cache pages mapped also into the CPU
40 is anonymous or page-cache pages as described above.
43 page-table entries point to that backing store.
47 the :doc:`dma-buf doc </driver-api/dma-buf>`.
53 allows deadlock-safe locking of multiple dma_resvs in arbitrary
55 :doc:`dma-buf doc </driver-api/dma-buf>`.
62 long-running mode.
[all …]