From: Michael Trimarchi <michael@amarulasolutions.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-amarula@amarulasolutions.com
Subject: [PATCH 0/3] Add initial support for iMX8MM power domain
Date: Wed, 1 Jan 2020 17:31:33 +0100 [thread overview]
Message-ID: <20200101163136.1586-1-michael@amarulasolutions.com> (raw)
Add some minimal support for imx8mm power domain. This let my usb otg2
to properly work in host mode. The patches and the description are
quite similar to iMX8MQ. I follow the same logic.
Michael Trimarchi (3):
soc: imx: gpcv2: add support for i.MX8MM SoC
irqchip/irq-imx-gpcv2: Add IRQCHIP_DECLARE for i.MX8MM compatible
arm64: dts: imx8mm: properly describe IRQ hierarchy
.../bindings/power/fsl,imx-gpcv2.txt | 4 +-
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 31 ++++-
drivers/irqchip/irq-imx-gpcv2.c | 2 +
drivers/soc/imx/gpcv2.c | 110 ++++++++++++++++++
4 files changed, 145 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-01-01 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 16:31 Michael Trimarchi [this message]
2020-01-01 16:31 ` [PATCH 1/3] soc: imx: gpcv2: add support for i.MX8MM SoC Michael Trimarchi
2020-01-01 22:44 ` Adam Ford
2020-01-03 18:36 ` kbuild test robot
2020-01-01 16:31 ` [PATCH 2/3] irqchip/irq-imx-gpcv2: Add IRQCHIP_DECLARE for i.MX8MM compatible Michael Trimarchi
2020-01-01 16:31 ` [PATCH 3/3] arm64: dts: imx8mm: properly describe IRQ hierarchy Michael Trimarchi
2020-01-03 22:54 ` kbuild test robot
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=20200101163136.1586-1-michael@amarulasolutions.com \
--to=michael@amarulasolutions.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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