From: Jesse Taube <mr.bossman075@gmail.com>
To: linux-imx@nxp.com
Cc: robh+dt@kernel.org, sboyd@kernel.org, shawnguo@kernel.org,
kernel@pengutronix.de, festevam@gmail.com, aisheng.dong@nxp.com,
stefan@agner.ch, linus.walleij@linaro.org,
gregkh@linuxfoundation.org, arnd@arndb.de, linux@armlinux.org.uk,
abel.vesa@nxp.com, dev@lynxeye.de, marcel.ziswiler@toradex.com,
tharvey@gateworks.com, leoyang.li@nxp.com, fugang.duan@nxp.com,
Mr.Bossman075@gmail.com, giulio.benetti@benettiengineering.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [PATCH v1 2/7] dt-bindings: pinctrl: Fix file path for pinfunc include
Date: Mon, 7 Nov 2022 02:15:06 -0500 [thread overview]
Message-ID: <20221107071511.2764628-3-Mr.Bossman075@gmail.com> (raw)
In-Reply-To: <20221107071511.2764628-1-Mr.Bossman075@gmail.com>
Reference to pinfunc.h was wrong. Fix it.
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
---
Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml b/Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml
index 1278f7293560..db5fe66ad873 100644
--- a/Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/fsl,imxrt1050.yaml
@@ -35,7 +35,7 @@ patternProperties:
each entry consists of 6 integers and represents the mux and config
setting for one pin. The first 5 integers <mux_reg conf_reg input_reg
mux_val input_val> are specified using a PIN_FUNC_ID macro, which can
- be found in <include/dt-bindings/pinctrl/pins-imxrt1050.h>. The last
+ be found in <arch/arm/boot/dts/imxrt1050-pinfunc.h>. The last
integer CONFIG is the pad setting value like pull-up on this pin. Please
refer to i.MXRT1050 Reference Manual for detailed CONFIG settings.
$ref: /schemas/types.yaml#/definitions/uint32-matrix
--
2.37.2
next prev parent reply other threads:[~2022-11-07 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 7:15 [PATCH v1 0/7] Clean-up and documentation for i.MXRT1050 Jesse Taube
2022-11-07 7:15 ` [PATCH v1 1/7] dt-bindings: arm: imx: Add i.MXRT compatible Documentation Jesse Taube
2022-11-07 7:15 ` Jesse Taube [this message]
2022-11-07 7:15 ` [PATCH v1 3/7] dt-bindings: timer: gpt: " Jesse Taube
2022-11-07 12:16 ` Rob Herring
2022-11-07 7:15 ` [PATCH v1 4/7] dt-bindings: serial: fsl-lpuart: add i.MXRT1170 compatible Jesse Taube
2022-11-07 7:15 ` [PATCH v1 5/7] dt-bindings: mmc: fsl-imx-esdhc: " Jesse Taube
2022-11-07 7:15 ` [PATCH v1 6/7] pinctrl: freescale: Fix i.MXRT1050 pad names Jesse Taube
2022-11-07 7:15 ` [PATCH v1 7/7] ARM: dts: imx: Update i.MXRT1050.dtsi compatibles Jesse Taube
2022-11-07 7:44 ` Arnd Bergmann
2022-11-07 15:09 ` Jesse Taube
2022-11-08 11:07 ` Arnd Bergmann
2022-11-09 8:54 ` Linus Walleij
2022-11-09 8:52 ` [PATCH v1 0/7] Clean-up and documentation for i.MXRT1050 Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221107071511.2764628-3-Mr.Bossman075@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=dev@lynxeye.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel.ziswiler@toradex.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
--cc=tharvey@gateworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).