public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: "A.s. Dong" <aisheng.dong@nxp.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Baruch Siach <baruch@tkos.co.il>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	"patchwork-lst@pengutronix.de" <patchwork-lst@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ
Date: Mon, 26 Feb 2018 15:09:58 +0800	[thread overview]
Message-ID: <20180226070957.GU3217@dragon> (raw)
In-Reply-To: <AM3PR04MB3063F807F42E76CD515A17480C10@AM3PR04MB306.eurprd04.prod.outlook.com>

On Mon, Feb 26, 2018 at 06:52:15AM +0000, A.s. Dong wrote:
> Hi Shawn,
> 
> > -----Original Message-----
> > From: Shawn Guo [mailto:shawnguo@kernel.org]
> > Sent: Monday, February 26, 2018 11:17 AM
> > To: A.s. Dong <aisheng.dong@nxp.com>
> > Cc: Lucas Stach <l.stach@pengutronix.de>; Mark Rutland
> > <mark.rutland@arm.com>; devicetree@vger.kernel.org; Baruch Siach
> > <baruch@tkos.co.il>; Catalin Marinas <catalin.marinas@arm.com>; Will
> > Deacon <will.deacon@arm.com>; patchwork-lst@pengutronix.de; Rob
> > Herring <robh+dt@kernel.org>; dl-linux-imx <linux-imx@nxp.com>;
> > kernel@pengutronix.de; Fabio Estevam <fabio.estevam@nxp.com>; linux-
> > arm-kernel@lists.infradead.org
> > Subject: Re: [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ
> > 
> > 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.
> > 
> 
> I had this question because we have below info in the patch
> "dt-bindings: add binding for i.MX8MQ IOMUXC":
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/fsl,imx8mq-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/fsl,imx8mq-pinctrl.txt
> new file mode 100644
> index 0000000..5c5d2d8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/fsl,imx8mq-pinctrl.txt
> @@ -0,0 +1,39 @@
> ...
> +       Refer to imx8mq-pinfunc.h in device tree source folder for all available
> +       imx8mq PIN_FUNC_ID.

This is just a cross reference in document, and should be okay on
different tree during development cycle.  If we have the pinfunc header
go via pinctrl tree, we will have a more serious dependency between DT
and pinctrl tree.

Shawn

  reply	other threads:[~2018-02-26  7:09 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
     [not found] ` <20180201183126.32384-1-l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-02-01 18:31   ` [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ Lucas Stach
     [not found]     ` <20180201183126.32384-2-l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-02-02  8:13       ` Jacky Bai
     [not found]         ` <HE1PR04MB3113FF72B02D642392D625DF87F90-6LN7OEpIatW7Zxc5AHJ2m89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
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
2018-02-26  6:52         ` A.s. Dong
2018-02-26  7:09           ` Shawn Guo [this message]
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
     [not found]     ` <20180201183126.32384-3-l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-02-05  6:09       ` Rob Herring
2018-02-05  7:24       ` Baruch Siach
     [not found]         ` <20180205072438.nxvhlqk54d7firbz-MwjkAAnuF3khR1HGirfZ1z4kX+cae0hd@public.gmane.org>
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=20180226070957.GU3217@dragon \
    --to=shawnguo@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=baruch@tkos.co.il \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=mark.rutland@arm.com \
    --cc=patchwork-lst@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.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