devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andra Danciu <andradanciu1997@gmail.com>
To: shawnguo@kernel.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
	manivannan.sadhasivam@linaro.org, andrew.smirnov@gmail.com,
	u.kleine-koenig@pengutronix.de, aisheng.dong@nxp.com,
	andradanciu1997@gmail.com, leoyang.li@nxp.com,
	festevam@gmail.com, sriram.dash@nxp.com, l.stach@pengutronix.de,
	pankaj.bansal@nxp.com, ping.bai@nxp.com, pramod.kumar_1@nxp.com,
	bhaskar.upadhaya@nxp.com, richard.hu@technexion.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] Add basic support for pico-pi-imx8m
Date: Thu, 18 Jul 2019 15:16:26 +0300	[thread overview]
Message-ID: <20190718121628.23991-1-andradanciu1997@gmail.com> (raw)

Add support for TechNexion PICO-PI-IMX8M based on patches from Richard Hu
Datasheet is at: https://s3.us-east-2.amazonaws.com/technexion/datasheets/picopiimx8m.pdf

Changes since v2:
 - changed PICO-PI-8M bord compatible from wand,imx8mq-pico-pi to
   technexion,pico-pi-imx8m
 - removed bootargs property
 - removed regulators node and put fixed regulator directly under root node
 - changed node name from usb_otg_vbus to regulator-usb-otg-vbus
 - removed pinctrl-names property from iomuxc node
 - removed wand-pi-8m container node
 - sorted pinctrl nodes alphabetically
 - removed tusb320_irqgrp, tusb320_irqgrp nodes because there is no upstream
   driver
 - changed properties' order in usb_dwc3_1 node

Changes since v1:
 - renamed wandboard-pi-8m.dts to pico-pi-8m.dts
 - removed pinctrl_csi1, pinctrl_wifi_ctrl
 - used generic name for pmic
 - removed gpo node
 - delete regulator-virtuals node
 - remove always-on property from buck1-8 and ldo3-7
 - remove pmic-buck-uses-i2c-dvs property for buck1-4

Andra Danciu (1):
  dt-bindings: arm: fsl: Add the pico-pi-imx8m board

Richard Hu (1):
  arm64: dts: fsl: pico-pi: Add a device tree for the PICO-PI-IMX8M

 Documentation/devicetree/bindings/arm/fsl.yaml |   1 +
 arch/arm64/boot/dts/freescale/Makefile         |   1 +
 arch/arm64/boot/dts/freescale/pico-pi-8m.dts   | 417 +++++++++++++++++++++++++
 3 files changed, 419 insertions(+)
 create mode 100644 arch/arm64/boot/dts/freescale/pico-pi-8m.dts

-- 
2.11.0

             reply	other threads:[~2019-07-18 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 12:16 Andra Danciu [this message]
2019-07-18 12:16 ` [PATCH v3 1/2] arm64: dts: fsl: pico-pi: Add a device tree for the PICO-PI-IMX8M Andra Danciu
2019-07-18 23:05   ` Fabio Estevam
2019-07-19 10:20     ` Andra Danciu
2019-07-18 12:16 ` [PATCH v3 2/2] dt-bindings: arm: fsl: Add the pico-pi-imx8m board Andra Danciu

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=20190718121628.23991-1-andradanciu1997@gmail.com \
    --to=andradanciu1997@gmail.com \
    --cc=aisheng.dong@nxp.com \
    --cc=andrew.smirnov@gmail.com \
    --cc=bhaskar.upadhaya@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=pankaj.bansal@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=pramod.kumar_1@nxp.com \
    --cc=richard.hu@technexion.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=sriram.dash@nxp.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).