Home
last modified time | relevance | path

Searched +full:use +full:- +full:push +full:- +full:pull (Results 1 – 25 of 230) sorted by relevance

12345678910

/openbmc/linux/arch/arm/boot/dts/st/
H A Dstm32h7-pinctrl.dtsi2 * Copyright 2017 - Alexandre Torgue <alexandre.torgue@st.com>
4 * This file is dual-licensed: you can use it either under the terms
24 * restriction, including without limitation the rights to use,
39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
43 #include <dt-bindings/pinctrl/stm32-pinfunc.h>
47 i2c1_pins_a: i2c1-0 {
51 bias-disable;
52 drive-open-drain;
53 slew-rate = <0>;
57 ethernet_rmii: rmii-0 {
[all …]
H A Dstm32f4-pinctrl.dtsi2 * Copyright 2017 - Alexandre Torgue <alexandre.torgue@st.com>
4 * This file is dual-licensed: you can use it either under the terms
24 * restriction, including without limitation the rights to use,
39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
43 #include <dt-bindings/pinctrl/stm32-pinfunc.h>
44 #include <dt-bindings/mfd/stm32f4-rcc.h>
49 #address-cells = <1>;
50 #size-cells = <1>;
52 interrupt-parent = <&exti>;
56 gpio-controller;
[all …]
H A Dstm32mp151a-prtt1l.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
6 /dts-v1/;
9 #include "stm32mp15-pinctrl.dtsi"
10 #include "stm32mp15xxad-pinctrl.dtsi"
11 #include <dt-bindings/gpio/gpio.h>
12 #include <dt-bindings/input/input.h>
13 #include <dt-bindings/leds/common.h>
18 mdio-gpio0 = &mdio0;
22 led-controller-0 {
23 compatible = "gpio-leds";
[all …]
/openbmc/intel-ipmi-oem/include/
H A Dsmbiosmdrv2.hpp5 // you may not use this file except in compliance with the License.
8 // http://www.apache.org/licenses/LICENSE-2.0
41 // ====================== MDR II Pull Command Structures ======================
42 // MDR II Pull Agent status inquiry command
59 // MDR II Pull Agent directory information inquiry command
76 // MDR II Pull Agent data set information inquiry command
94 // MDR II Pull Agent lock data set command
102 // MDR II Pull Agent lock data set response
112 // MDR II Pull Agent unlock data set command
119 // MDR II Pull Agent get data block command
[all …]
H A Dsmbiosmdrv2handler.hpp5 // you may not use this file except in compliance with the License.
8 // http://www.apache.org/licenses/LICENSE-2.0
63 static constexpr const int lastAgentIndex = -1;
90 #pragma pack(push)
141 // ====================== MDR II Pull Command Structures ======================
159 // ====================== MDR II Push Command Structures ======================
166 // MDR II Push Agent send data set info command
178 // MDR II Pull Agent lock data set command
186 // MDR II Pull Agent lock data set response
196 // MDR II Push Agent send data start command
/openbmc/linux/Documentation/devicetree/bindings/mfd/
H A Dst,stmfx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: STMicroelectonics Multi-Function eXpander (STMFX)
9 description: ST Multi-Function eXpander (STMFX) is a slave controller using I2C for
15 - Amelie Delaunay <amelie.delaunay@foss.st.com>
19 const: st,stmfx-0300
27 drive-open-drain: true
29 vdd-supply: true
36 const: st,stmfx-0300-pinctrl
[all …]
/openbmc/linux/Documentation/maintainer/
H A Dpull-requests.rst1 Creating Pull Requests
4 This chapter describes how maintainers can create and submit pull requests
9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
23 the pull request on a separate branch. Typically you will base this branch
24 off of a branch in the developers tree whom you intend to send the pull
27 In order to create the pull request you must first tag the branch that you
33 Greg offers the following. A pull request with miscellaneous stuff for
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
[all …]
H A 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
10 ways to use those features. This document looks in particular at the use
11 of rebasing and merging. Maintainers often get in trouble when they use
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
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
67 - Do not reparent a tree without a good reason to do so. Just being on a
[all …]
/openbmc/linux/Documentation/devicetree/bindings/net/
H A Dsmsc,lan9115.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Smart Mixed-Signal Connectivity (SMSC) LAN911x/912x Controller
10 - Shawn Guo <shawnguo@kernel.org>
13 - $ref: ethernet-controller.yaml#
18 - const: smsc,lan9115
19 - items:
20 - enum:
21 - smsc,lan89218
[all …]
/openbmc/u-boot/arch/arm/dts/
H A Dstm32f4-pinctrl.dtsi2 * Copyright (C) 2017, STMicroelectronics - All Rights Reserved
5 * This file is dual-licensed: you can use it either under the terms
25 * restriction, including without limitation the rights to use,
40 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
44 #include <dt-bindings/pinctrl/stm32-pinfunc.h>
45 #include <dt-bindings/mfd/stm32f4-rcc.h>
49 pinctrl: pin-controller {
50 #address-cells = <1>;
51 #size-cells = <1>;
53 interrupt-parent = <&exti>;
[all …]
H A Dstm32h743-pinctrl.dtsi2 * Copyright 2017 - Alexandre Torgue <alexandre.torgue@st.com>
4 * This file is dual-licensed: you can use it either under the terms
24 * restriction, including without limitation the rights to use,
39 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
43 #include <dt-bindings/pinctrl/stm32h7-pinfunc.h>
47 pin-controller {
48 #address-cells = <1>;
49 #size-cells = <1>;
50 compatible = "st,stm32h743-pinctrl";
52 pins-are-numbered;
[all …]
H A Dstm32f746.dtsi2 * Copyright 2016 - Michael Kurz <michi.kurz@gmail.com>
3 * Copyright 2016 - Vikas MANOCHA <vikas.manocha@st.com>
7 * Copyright 2015 - Maxime Coquelin <mcoquelin.stm32@gmail.com>
9 * This file is dual-licensed: you can use it either under the terms
29 * restriction, including without limitation the rights to use,
44 * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
48 #include "armv7-m.dtsi"
49 #include <dt-bindings/pinctrl/stm32f746-pinfunc.h>
50 #include <dt-bindings/clock/stm32fx-clock.h>
51 #include <dt-bindings/mfd/stm32f7-rcc.h>
[all …]
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Dsubmit-changes.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 .. _ref-why-mailing-lists:
13 Contributing through mailing lists --- Why not using web-based workflows?
42 mailing list approach off-putting and would prefer a web-based GUI.
48 documenting how to use such workflows since we recognise that whilst this was
55 ----------
60 sudo apt install git-core git-email
62 Then, you need to set a name and e-mail address that Git will
63 use to identify your commits::
65 git config --global user.name "Ada Lovelace"
[all …]
/openbmc/linux/Documentation/process/
H A D7.AdvancedTopics.rst12 -------------------------
14 The use of distributed version control for the kernel began in early 2002,
27 teach the reader how to use git; that would be sufficient material for a
32 https://git-scm.com/
34 https://www.kernel.org/pub/software/scm/git/docs/user-manual.html
39 understanding of how git works before trying to use it to make patches
40 available to others. A git-using developer should be able to obtain a copy
42 the tree, use branches, etc. An understanding of git's tools for the
45 remote branches, the index, fast-forward merges, pushes and pulls, detached
54 server with git-daemon is relatively straightforward if you have a system
[all …]
/openbmc/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-mt65xx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mt65xx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - $ref: /schemas/i2c/i2c-controller.yaml#
17 - Qii Wang <qii.wang@mediatek.com>
22 - const: mediatek,mt2712-i2c
23 - const: mediatek,mt6577-i2c
24 - const: mediatek,mt6589-i2c
25 - const: mediatek,mt7622-i2c
[all …]
/openbmc/linux/drivers/pinctrl/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
47 for GPIO use.
66 will be called pinctrl-apple-gpio.
69 bool "Axis ARTPEC-6 pin controller driver"
74 This is the driver for the Axis ARTPEC-6 pin controller. This driver
77 found in Documentation/devicetree/bindings/pinctrl/axis,artpec6-pinctrl.txt
86 functionality. This driver supports the pinmux, push-pull and
117 tristate "X-Powers AXP209 PMIC pinctrl and GPIO Support"
150 called pinctrl-cy8c95x0.
153 tristate "TI DA850/OMAP-L138/AM18XX pull-up and pull-down groups"
[all …]
/openbmc/u-boot/doc/device-tree-bindings/pinctrl/
H A Dst,stm32-pinctrl.txt5 also provides ability to multiplex and configure the output of various on-chip
10 - compatible: value should be one of the following:
11 (a) "st,stm32f429-pinctrl"
12 (b) "st,stm32f746-pinctrl"
13 - #address-cells: The value of this property must be 1
14 - #size-cells : The value of this property must be 1
15 - ranges : defines mapping between pin controller node (parent) to
16 gpio-bank node (children).
17 - pins-are-numbered: Specify the subnodes are using numbered pinmux to
22 - gpio-controller : Indicates this device is a GPIO controller
[all …]
H A Dpinctrl-bindings.txt4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
15 need to reconfigure pins at run-time, for example to tri-state pins when the
30 bindings for the individual client devices in use by that board, i.e. whether
47 pinctrl-0: List of phandles, each pointing at a pin configuration
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
70 pinctrl-names: The list of names to assign states. List entry 0 defines the
78 pinctrl-names = "active", "idle";
79 pinctrl-0 = <&state_0_node_a>;
80 pinctrl-1 = <&state_1_node_a &state_1_node_b>;
[all …]
/openbmc/openbmc/poky/scripts/
H A Dcreate-pull-request3 # Copyright (c) 2010-2013, Intel Corporation.
5 # SPDX-License-Identifier: GPL-2.0-or-later
15 ODIR=pull-$$
24 …: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r relative_to] [-i commit_id] [-d re…
25 -b branch Branch name in the specified remote (default: current branch)
26 -l local branch Local branch name (default: HEAD)
27 -c Create an RFC (Request for Comment) patch series
28 -h Display this help message
29 -a Automatically push local branch (-l) to remote branch (-b),
31 -i commit_id Ending commit (default: HEAD)
[all …]
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Datmel,at91-pio4-pinctrl.txt7 - compatible:
8 "atmel,sama5d2-pinctrl"
9 "microchip,sama7g5-pinctrl"
10 - reg: base address and length of the PIO controller.
11 - interrupts: interrupt outputs from the controller, one for each bank.
12 - interrupt-controller: mark the device node as an interrupt controller.
13 - #interrupt-cells: should be two.
14 - gpio-controller: mark the device node as a gpio controller.
15 - #gpio-cells: should be two.
17 Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
[all …]
H A Dpincfg-node.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pincfg-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
14 and generic. Pin control bindings should use the properties defined below
21 bias-disable:
25 bias-high-impedance:
27 description: high impedance mode ("third-state", "floating")
29 bias-bus-hold:
[all …]
H A Dcypress,cy8c95x0.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Patrick Rudolph <patrick.rudolph@9elements.com>
14 Pin function configuration is performed on a per-pin basis.
19 - cypress,cy8c9520
20 - cypress,cy8c9540
21 - cypress,cy8c9560
26 gpio-controller: true
28 '#gpio-cells':
[all …]
/openbmc/openbmc/poky/documentation/overview-manual/
H A Ddevelopment-environment.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
38 Linus Torvalds in 1991. Conversely, a good example of a non-open source
54 system not intended to run the software --- the development host.
56 You need to set up a development host in order to use it with the Yocto
58 function as the development host. However, it is possible to use a
60 development host. When you have a Mac or Windows-based system, you can
62 `CROPS <https://github.com/crops/poky-container>`__, which leverages
65 environment that is similar to what you see when using a Linux-based
68 ":ref:`dev-manual/start:setting up to use cross platforms (crops)`"
74 for use with the Yocto Project. You need to be sure that the Linux
[all …]
/openbmc/linux/Documentation/devicetree/bindings/gpio/
H A Dgpio.txt5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
11 bindings use it, but are only supported for compatibility reasons and should not
24 and bit-banged data signals:
27 gpio-controller;
28 #gpio-cells = <2>;
32 data-gpios = <&gpio1 12 0>,
44 recommended to use the two-cell approach.
[all …]
/openbmc/linux/Documentation/driver-api/gpio/
H A Ddriver.rst19 GPIO chip. The use case is the indicative: certain lines in a system may be
26 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
31 use hardware offsets 0..31 for these, corresponding to bits 0..31 in the
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
48 numbers need not be contiguous; either of those platforms could also use numbers
49 2000-2063 to identify GPIO lines in a bank of I2C GPIO expanders.
[all …]

12345678910