Home
last modified time | relevance | path

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

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx53-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
32 imx53 PIN_FUNC_ID.
Dfsl,imx51-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
32 imx51 PIN_FUNC_ID.
Dfsl,imx50-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
32 imx50 PIN_FUNC_ID.
Dfsl,imx35-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
33 imx35 PIN_FUNC_ID.
Dfsl,imx6dl-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
38 imx6dl PIN_FUNC_ID.
Dfsl,imx6q-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
38 imx6q PIN_FUNC_ID.
Dfsl,vf610-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is
41 for all available PIN_FUNC_ID for Vybrid VF610.
Dfsl,imx6sl-pinctrl.txt9 setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
39 imx6sl PIN_FUNC_ID.
Dfsl,imx6sll-pinctrl.txt10 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
40 imx6sll PIN_FUNC_ID.
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.
Dfsl,imx25-pinctrl.txt23 imx25 PIN_FUNC_ID.
Dfsl,imx6sx-pinctrl.txt10 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
Dfsl,imx6ul-pinctrl.txt11 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
Dfsl,imx7ulp-pinctrl.txt18 using a PIN_FUNC_ID macro, which can be found in
Dfsl,imx8mp-pinctrl.yaml36 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
Dfsl,imx8mn-pinctrl.yaml36 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
Dfsl,imx8mm-pinctrl.yaml36 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
Dfsl,imx8mq-pinctrl.yaml36 mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
Dfsl,imx7d-pinctrl.txt33 input_val> are specified using a PIN_FUNC_ID macro, which can be found in
/kernel/linux/linux-5.10/drivers/pinctrl/freescale/
Dpinctrl-imx.c499 * Each pin represented in fsl,pins consists of a number of u32 PIN_FUNC_ID
500 * and 1 u32 CONFIG, the total size is PIN_FUNC_ID + CONFIG for each pin.
503 * PIN_FUNC_ID format:
595 * the binding format is fsl,pins = <PIN_FUNC_ID CONFIG ...>, in imx_pinctrl_parse_groups()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/freescale/
Dfsl,scu.txt118 PIN_FUNC_ID macro, which can be found in
/kernel/linux/linux-5.10/drivers/pinctrl/renesas/
Dpinctrl-rzn1.c699 * pinmux = <PIN_FUNC_ID CONFIG ...>, in rzn1_pinctrl_parse_groups()
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/
D0031_linux_drivers_perf_phy_pinctrl_ptp_pwm.patch2328 + * Each pin represented in fsl,pins consists of 5 u32 PIN_FUNC_ID and