linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm64: add basic DTS for i.MX8MQ
Date: Tue, 23 Jan 2018 14:23:19 +0100	[thread overview]
Message-ID: <1516713799.25726.21.camel@pengutronix.de> (raw)
In-Reply-To: <20180123103609.GD27764@dragon>

Am Dienstag, den 23.01.2018, 18:36 +0800 schrieb Shawn Guo:
> On Wed, Jan 17, 2018 at 07:32:42PM +0100, Lucas Stach wrote:
> > This adds the basic DTS for the i.MX8MQ.
> > For now only the following peripherals are supported:
> > - IOMUXC (pin controller)
> > - CCM (clock controller)
> > - GPIO
> > - UART
> > - uSDHC (SD/eMMC controller)
> > - FEC (ethernet controller)
> > - i2c
> > 
> > This is enough to get a very basic board support up and running.
> > 
> > One known limitation is that the driver for the GPC interrupt
> > controller is still missing, rendering the CPU sleep states unusable
> > as there is nothing waking them up anymore. This will be fixed in
> > due course.
> > 
> > > > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> > ---
> > ?arch/arm64/boot/dts/Makefile?????????????|???1 +
> > ?arch/arm64/boot/dts/nxp/imx8mq-pinfunc.h | 632 +++++++++++++++++++++++++++++++
> > ?arch/arm64/boot/dts/nxp/imx8mq.dtsi??????| 418 ++++++++++++++++++++
> > ?3 files changed, 1051 insertions(+)
> > ?create mode 100644 arch/arm64/boot/dts/nxp/imx8mq-pinfunc.h
> > ?create mode 100644 arch/arm64/boot/dts/nxp/imx8mq.dtsi
> 
> <snip>

> > +	timer {
> > > > +		compatible = "arm,armv8-timer";
> > > > +		interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(6) | IRQ_TYPE_LEVEL_LOW)>, /* Physical Secure */
> > > > +		?????????????<GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(6) | IRQ_TYPE_LEVEL_LOW)>, /* Physical Non-Secure */
> > > > +		?????????????<GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(6) | IRQ_TYPE_LEVEL_LOW)>, /* Virtual */
> > > > +		?????????????<GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(6) | IRQ_TYPE_LEVEL_LOW)>; /* Hypervisor */
> > > > +		clock-frequency = <8333333>;
> > > > +		interrupt-parent = <&gic>;
> > > > +		arm,no-tick-in-suspend;
> > > > +	};
> > +
> > +	peripherals at 0 {
> 
> What's the reason of using 'peripherals' rather than 'soc' which is the
> case for most device trees?

Just personal preference. I find it a bit confusing to have a soc node,
that doesn't include a lot of stuff (e.g CPUs) that are found on the
SoC. I someone feels strongly about this I'll change it.

> > +		compatible = "simple-bus";
> > +
> 
> Drop the newline.
> 
> > > > +		#address-cells = <1>;
> > > > +		#size-cells = <1>;
> > > > +		ranges = <0x0 0x0 0x0 0x3e000000>;
> > +
> > +
> 
> One newline is enough.
> 
> > > > +		aips-bus at 30000000 { /* AIPS1 */
> > > > +			compatible = "nxp,imx8mq-aips-bus", "simple-bus";
> > +
> 
> Drop the newline.
> 
> > > > +			#address-cells = <1>;
> > > > +			#size-cells = <1>;
> > > > +			ranges = <0x30000000 0x30000000 0x400000>;
> > +
> > > > > > +			gpio1: gpio at 30200000 {
> > +				compatible = "nxp,imx8mq-gpio", "fsl,imx35-gpio";
> 
> It looks a bit odd to have different vendor prefix for the same device.
> But we can understand the reason.??Just curious if this is what vendor
> kernel does?

No, I did it mostly to be consistent with the location of the DT files
under "nxp". I'll change this to match the "freescale" location.

Regards,
Lucas

  reply	other threads:[~2018-01-23 13:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 18:32 [PATCH 1/4] ARM64: add basic Kconfig symbols for i.MX8 Lucas Stach
2018-01-17 18:32 ` [PATCH 2/4] arm64: add basic DTS for i.MX8MQ Lucas Stach
2018-01-22 11:51   ` Arnd Bergmann
2018-01-22 11:57   ` Fabio Estevam
2018-01-22 14:47   ` Shawn Guo
2018-01-22 15:11     ` Arnd Bergmann
2018-01-22 17:50       ` Lucas Stach
2018-01-23  1:40         ` Shawn Guo
2018-01-23 10:36   ` Shawn Guo
2018-01-23 13:23     ` Lucas Stach [this message]
2018-01-25  9:48       ` aisheng.dong at codeaurora.org
2018-01-25 10:27         ` Lucas Stach
2018-01-25 12:34           ` Dong Aisheng
2018-02-02  7:27         ` Shawn Guo
2018-01-29 17:45   ` Rob Herring
2018-01-29 17:55   ` Rob Herring
2018-01-29 18:00     ` Lucas Stach
2018-01-30 14:55       ` Rob Herring
2018-01-17 18:32 ` [PATCH 3/4] arm64: add support for i.MX8M EVK board Lucas Stach
2018-01-22 11:58   ` Fabio Estevam
2018-01-23 10:39   ` Shawn Guo
2018-01-25 10:10     ` aisheng.dong at codeaurora.org
2018-01-25 10:31       ` Lucas Stach
2018-01-25 10:49         ` Dong Aisheng
2018-01-25 11:09           ` Lucas Stach
2018-01-25 13:03             ` Dong Aisheng
2018-01-25 18:03               ` Lucas Stach
2018-01-26  3:06                 ` A.s. Dong
2018-01-24 14:47   ` Baruch Siach
2018-01-25  9:52     ` Baruch Siach
2018-01-29 17:52   ` Rob Herring
2018-01-17 18:32 ` [PATCH 4/4] MAINTAINERS: add i.MX8 DT path to i.MX architecture Lucas Stach
2018-01-22 11:58   ` Fabio Estevam
2018-01-22 11:53 ` [PATCH 1/4] ARM64: add basic Kconfig symbols for i.MX8 Fabio Estevam

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=1516713799.25726.21.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --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).