Home
last modified time | relevance | path

Searched full:pin_func_id (Results 1 – 13 of 13) sorted by relevance

/linux/Documentation/devicetree/bindings/pinctrl/
H A Dfsl,vf610-iomuxc.yaml34 The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a pin
43 for all available PIN_FUNC_ID for Vybrid VF610.
H A Dfsl,imx-pinctrl.txt27 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
30 looks like <PIN_FUNC_ID CONFIG> in the example below.
H A Dfsl,imx25-pinctrl.txt23 imx25 PIN_FUNC_ID.
H A Dfsl,scu-pinctrl.yaml39 specified using a PIN_FUNC_ID macro, which can be found in
H A Dfsl,imx8ulp-pinctrl.yaml36 mux_mode input_val> are specified using a PIN_FUNC_ID macro, which can
H A Dfsl,imxrt1050.yaml37 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
H A Dfsl,imxrt1170.yaml37 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
H A Dfsl,imx8m-pinctrl.yaml40 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
H A Dfsl,imx7ulp-iomuxc1.yaml42 using a PIN_FUNC_ID macro, which can be found in
H A Dfsl,imx7d-pinctrl.yaml45 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
/linux/Documentation/devicetree/bindings/firmware/
H A Dnxp,imx95-scmi-pinctrl.yaml30 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
/linux/drivers/pinctrl/freescale/
H A Dpinctrl-imx.c444 * Each pin represented in fsl,pins consists of a number of u32 PIN_FUNC_ID
445 * and 1 u32 CONFIG, the total size is PIN_FUNC_ID + CONFIG for each pin.
447 * PIN_FUNC_ID format:
531 * the binding format is fsl,pins = <PIN_FUNC_ID CONFIG ...>, in imx_pinctrl_parse_groups()
/linux/drivers/pinctrl/renesas/
H A Dpinctrl-rzn1.c702 * pinmux = <PIN_FUNC_ID CONFIG ...>, in rzn1_pinctrl_parse_groups()