Home
last modified time | relevance | path

Searched refs:PIN (Results 1 – 25 of 28) sorted by relevance

12

/linux/drivers/pinctrl/
H A Dpinctrl-rp1.c148 #define PIN(i, f0, f1, f2, f3, f4, f5, f6, f7, f8) \ macro
564 PIN(0, spi0, dpi, uart1, i2c0, _, gpio, proc_rio, pio, spi2),
565 PIN(1, spi0, dpi, uart1, i2c0, _, gpio, proc_rio, pio, spi2),
566 PIN(2, spi0, dpi, uart1, i2c1, ir, gpio, proc_rio, pio, spi2),
567 PIN(3, spi0, dpi, uart1, i2c1, ir, gpio, proc_rio, pio, spi2),
568 PIN(4, gpclk0, dpi, uart2, i2c2, uart0, gpio, proc_rio, pio, spi3),
569 PIN(5, gpclk1, dpi, uart2, i2c2, uart0, gpio, proc_rio, pio, spi3),
570 PIN(6, gpclk2, dpi, uart2, i2c3, uart0, gpio, proc_rio, pio, spi3),
571 PIN(7, spi0, dpi, uart2, i2c3, uart0, gpio, proc_rio, pio, spi3),
572 PIN(8, spi0, dpi, uart3, i2c0, _, gpio, proc_rio, pio, spi4),
[all …]
H A Dpinctrl-rockchip.c288 #define PIN_BANK_MUX_ROUTE_FLAGS(ID, PIN, FUNC, REG, VAL, FLAG) \ argument
291 .pin = PIN, \
298 #define RK_MUXROUTE_SAME(ID, PIN, FUNC, REG, VAL) \ argument
299 PIN_BANK_MUX_ROUTE_FLAGS(ID, PIN, FUNC, REG, VAL, ROCKCHIP_ROUTE_SAME)
301 #define RK_MUXROUTE_GRF(ID, PIN, FUNC, REG, VAL) \ argument
302 PIN_BANK_MUX_ROUTE_FLAGS(ID, PIN, FUNC, REG, VAL, ROCKCHIP_ROUTE_GRF)
304 #define RK_MUXROUTE_PMU(ID, PIN, FUNC, REG, VAL) \ argument
305 PIN_BANK_MUX_ROUTE_FLAGS(ID, PIN, FUNC, REG, VAL, ROCKCHIP_ROUTE_PMU)
307 #define RK3588_PIN_BANK_FLAGS(ID, PIN, LABEL, M, P) \ argument
308 PIN_BANK_IOMUX_FLAGS_PULL_FLAGS(ID, PIN, LABEL, M, M, M, M, P, P, P, P)
/linux/drivers/pinctrl/cirrus/
H A Dpinctrl-lochnagar.c444 LN_FUNC(lochnagar##REV##_##ID##_pin.name, PIN, OP)
457 LN_FUNC(lochnagar2_##ID##_BCLK_pin.name, PIN, BOP), \
458 LN_FUNC(lochnagar2_##ID##_LRCLK_pin.name, PIN, LROP), \
459 LN_FUNC(lochnagar2_##ID##_RXDAT_pin.name, PIN, RXOP), \
460 LN_FUNC(lochnagar2_##ID##_TXDAT_pin.name, PIN, TXOP)
477 LN_FUNC("dsp-gpio1", PIN, 0x01),
478 LN_FUNC("dsp-gpio2", PIN, 0x02),
479 LN_FUNC("dsp-gpio3", PIN, 0x03),
480 LN_FUNC("codec-gpio1", PIN, 0x04),
481 LN_FUNC("codec-gpio2", PIN, 0x05),
[all …]
/linux/arch/arm/boot/dts/ti/omap/
H A Dam335x-pocketbeagle.dts220 /* P2_03 (ZCZ ball T10) gpio0_23 0x824 PIN 9 */
229 /* P1_34 (ZCZ ball T11) gpio0_26 0x828 PIN 10 */
238 /* P2_19 (ZCZ ball U12) gpio0_27 0x82c PIN 11 */
247 /* P2_24 (ZCZ ball T12) gpio1_12 0x830 PIN 12 */
256 /* P2_33 (ZCZ ball R12) gpio1_13 0x834 PIN 13 */
265 /* P2_22 (ZCZ ball V13) gpio1_14 0x838 PIN 14 */
283 /* P2_10 (ZCZ ball R14) gpio1_20 0x850 PIN 20 */
292 /* P2_06 (ZCZ ball U16) gpio1_25 0x864 PIN 25 */
301 /* P2_04 (ZCZ ball T16) gpio1_26 0x868 PIN 26 */
310 /* P2_02 (ZCZ ball V17) gpio1_27 0x86c PIN 27 */
[all …]
H A Dam335x-moxa-uc-8100-common.dtsi45 …PADCONF(AM335X_PIN_LCD_VSYNC, PIN_INPUT_PULLDOWN, MUX_MODE7) /* lcd_vsync.gpio2_22 Power off PIN*/
/linux/Documentation/translations/zh_CN/process/
H A Dmaintainer-pgp-guide.rst387 你应该设置用户 PIN (1)、管理员 PIN (3) 和重置代码 (4)。请确保将
388 这些信息记录并存储在安全的地方，尤其是管理员 PIN 码和重置代码（它允
389 许你完全擦除智能卡）。你很少需要使用管理员 PIN 码，如果你不记录它，
397 尽管名称为“PIN”，但卡上的用户 PIN 和管理员 PIN 都不需要是数字。
408 上。对于大多数操作，你将需要 PGP 密钥密码和卡的管理员 PIN::
445 交选择时，系统将首先提示你输入 PGP 密钥密码，然后输入管理员 PIN 码。
497 在你的第一条命令执行时，应该会询问你智能卡的PIN，然后在你运行
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dfsl,imx27-pinctrl.txt10 setting. The format is fsl,pins = <PIN MUX_ID CONFIG>.
12 PIN is an integer between 0 and 0xbf. imx27 has 6 ports with 32 configurable
13 configurable pins each. PIN is PORT * 32 + PORT_PIN, PORT_PIN is the pin
90 For convenience there are macros defined in imx27-pinfunc.h which provide PIN
/linux/Documentation/userspace-api/media/cec/
H A Dcec-ioc-dqevent.rst153 * .. _`CEC-EVENT-PIN-CEC-LOW`:
160 * .. _`CEC-EVENT-PIN-CEC-HIGH`:
167 * .. _`CEC-EVENT-PIN-HPD-LOW`:
176 * .. _`CEC-EVENT-PIN-HPD-HIGH`:
185 * .. _`CEC-EVENT-PIN-5V-LOW`:
194 * .. _`CEC-EVENT-PIN-5V-HIGH`:
H A Dcec-ioc-adap-g-caps.rst127 * .. _`CEC-CAP-MONITOR-PIN`:
H A Dcec-ioc-g-mode.rst156 * .. _`CEC-MODE-MONITOR-PIN`:
163 This mode requires that the :ref:`CEC_CAP_MONITOR_PIN <CEC-CAP-MONITOR-PIN>`
/linux/Documentation/translations/zh_CN/kbuild/
H A Dkbuild.rst275 当签署内核模块时，如果私钥需要密码或 PIN，此变量允许将密码或 PIN 传递给 sign-file 工具。
/linux/arch/arm64/boot/dts/renesas/
H A Dr9a07g043-smarc-pmod.dtso12 * |CN7 (PMOD1 PIN HEADER) |
H A Dr9a08g045s33-smarc-pmod1-type-3a.dtso12 * |PMOD1_3A (PMOD1 PIN HEADER) |
H A Dwhite-hawk-ard-audio-da7212.dtso18 * |CN40 (IO PIN HEADER) |
/linux/Documentation/arch/arm/samsung/
H A Dgpio.rst22 PIN configuration
/linux/arch/arm64/boot/dts/hisilicon/
H A Dhikey970-pmic.dtsi34 ldo4: ldo4 { /* 40 PIN */
/linux/arch/arm64/boot/dts/exynos/
H A Dexynos5433-pinctrl.dtsi14 #define PIN(_pin, _func, _pull, _drv) \ macro
23 PIN(_pin, INPUT, _pull, _drv)
26 PIN(_pin, OUTPUT, _pull, _drv)
29 PIN(_pin, 2, _pull, _drv)
/linux/Documentation/process/
H A Dmaintainer-pgp-guide.rst443 You should set the user PIN (1), Admin PIN (3), and the Reset Code (4).
445 the Admin PIN and the Reset Code (which allows you to completely wipe
446 the smartcard). You so rarely need to use the Admin PIN, that you will
455 Despite having the name "PIN", neither the user PIN nor the admin
456 PIN on the card need to be numbers.
469 passphrase and the admin PIN of the card for most operations::
510 your PGP key passphrase, and then for the admin PIN. If the command
569 This should ask for your smartcard PIN on your first command, and then
/linux/Documentation/translations/it_IT/process/
H A Dmaintainer-pgp-guide.rst469 Dovreste impostare il PIN dell'utente (1), quello dell'amministratore (3) e il
471 posto sicuro -- specialmente il PIN dell'amministratore e il codice di reset
472 (che vi permetterà di azzerare completamente la smartcard). Il PIN
482 A dispetto del nome "PIN", né il PIN utente né quello dell'amministratore
496 vi serviranno sia la passphrase della chiave PGP che il PIN
539 chiave PGP, e poi il PIN dell'amministratore. Se il comando ritorna senza
598 Col primo comando dovrebbe chiedervi il PIN della smartcard, e poi dovrebbe
/linux/Documentation/driver-api/
H A Dpin-control.rst2 PINCTRL (PIN CONTROL) subsystem
22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that
28 in the range 0..maxpin. This numberspace is local to each PIN CONTROLLER, so
33 When a PIN CONTROLLER is instantiated, it will register a descriptor to the
480 - FUNCTIONS have PIN GROUPS as defined on the generic level - so a certain
493 - The combination of a FUNCTION and a PIN GROUP determine a certain function
507 - FUNCTIONS and GROUPS on a certain PIN CONTROLLER are MAPPED to a certain
537 - PINS for a certain FUNCTION using a certain PIN GROUP on a certain
538 PIN CONTROLLER are provided on a first-come first-serve basis, so if some
/linux/Documentation/admin-guide/
H A Dmodule-signing.rst112 PKCS#11 token requires a PIN, this can be provided at build time by
239 If the private key requires a passphrase or PIN, it can be provided in the
/linux/drivers/pinctrl/renesas/
H A Dpinctrl-rzt2h.c45 #define PIN(m) (0x800 + (m)) macro
571 return !!(rzt2h_pinctrl_readb(pctrl, port, PIN(port)) & BIT(bit)); in rzt2h_gpio_get()
/linux/Documentation/devicetree/bindings/sound/
H A Drenesas,rsnd.txt233 ** PIN sharing
/linux/Documentation/kbuild/
H A Dkbuild.rst290 This variable allows a passphrase or PIN to be passed to the sign-file
/linux/Documentation/nvme/
H A Dnvme-pci-endpoint-target.rst357 interrupt_pin Interrupt PIN to use if MSI and MSI-X are not supported

12