From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ
Date: Mon, 26 Feb 2018 11:17:01 +0800 [thread overview]
Message-ID: <20180226031700.GS3217@dragon> (raw)
In-Reply-To: <AM3PR04MB306E1344C6242887F4797AC80C20@AM3PR04MB306.eurprd04.prod.outlook.com>
On Sun, Feb 25, 2018 at 10:47:11AM +0000, A.s. Dong wrote:
> > Documentation/devicetree/bindings/arm/fsl.txt | 4 +
> > arch/arm64/boot/dts/freescale/imx8mq-pinfunc.h | 623
> > +++++++++++++++++++++++++
>
> Should this belongs to pinctrl part?
No. Those pinfunc defines are used by device tree rather than pinctrl
driver.
Shawn
next prev parent reply other threads:[~2018-02-26 3:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:31 [PATCH v2 1/4] arm64: add basic Kconfig symbols for i.MX8 Lucas Stach
2018-02-01 18:31 ` [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ Lucas Stach
2018-02-02 8:13 ` Jacky Bai
2018-02-05 8:45 ` Shawn Guo
2018-02-05 9:07 ` Jacky Bai
2018-02-05 6:09 ` Rob Herring
2018-02-05 15:00 ` Marc Zyngier
2018-02-25 10:47 ` A.s. Dong
2018-02-26 3:17 ` Shawn Guo [this message]
2018-02-26 6:52 ` A.s. Dong
2018-02-26 7:09 ` Shawn Guo
2018-02-26 8:07 ` A.s. Dong
2018-03-09 3:23 ` Shawn Guo
2018-02-01 18:31 ` [PATCH v2 3/4] arm64: add support for i.MX8M EVK board Lucas Stach
2018-02-05 6:09 ` Rob Herring
2018-02-05 7:24 ` Baruch Siach
2018-02-05 11:10 ` Lucas Stach
2018-02-23 3:46 ` Shawn Guo
2018-02-23 4:32 ` Baruch Siach
2018-02-23 7:05 ` Shawn Guo
2018-02-23 15:03 ` Shawn Guo
2018-02-23 15:30 ` Juergen Borleis
2018-02-23 15:46 ` Lucas Stach
2018-02-24 2:58 ` Bough Chen
2018-02-24 6:00 ` Shawn Guo
2018-02-25 9:54 ` A.s. Dong
2018-02-23 15:45 ` Lucas Stach
2018-02-25 10:00 ` A.s. Dong
2018-02-01 18:31 ` [PATCH v2 4/4] MAINTAINERS: add i.MX8 DT path to i.MX architecture Lucas Stach
2018-02-23 14:56 ` [PATCH v2 1/4] arm64: add basic Kconfig symbols for i.MX8 Shawn Guo
2018-02-25 10:17 ` A.s. Dong
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=20180226031700.GS3217@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).