From: Adrien Grassein <adrien.grassein@gmail.com>
Cc: robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
catalin.marinas@arm.com, will@kernel.org,
bjorn.andersson@linaro.org, krzk@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Adrien Grassein <adrien.grassein@gmail.com>
Subject: [PATCH v1 0/4] Add peripheral support to imx8mq-nitrogen board
Date: Tue, 30 Mar 2021 10:35:10 +0200 [thread overview]
Message-ID: <20210330083514.5874-1-adrien.grassein@gmail.com> (raw)
Hi,
this patch set aims is to add support of multiple peripheral of the
Boundary8M board:
- USB Host (behind a resatable hub, started by u-boot);
- USB device;
- DB_DSIHD sub board for MIPI-DSI to HDMI output (via lt8912b chip).
Thanks,
Adrien Grassein (4):
arm64: dts: imx8mq-nitrogen: add USB OTG support
arm64: dts: imx8mq-nitrogen: add USB HOST support
arm64: dts: imx8mq-nitrogen: add lt8912 MIPI-DSI to HDMI
arm64: defconfig: Enable LT8912B DRM bridge driver
.../boot/dts/freescale/imx8mq-nitrogen.dts | 185 ++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
2 files changed, 186 insertions(+)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-30 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 8:35 Adrien Grassein [this message]
2021-03-30 8:35 ` [PATCH v1 1/4] arm64: dts: imx8mq-nitrogen: add USB OTG support Adrien Grassein
2021-03-30 8:35 ` [PATCH v1 2/4] arm64: dts: imx8mq-nitrogen: add USB HOST support Adrien Grassein
2021-03-30 8:38 ` Ahmad Fatoum
2021-03-30 8:54 ` Adrien Grassein
2021-03-30 8:35 ` [PATCH v1 3/4] arm64: dts: imx8mq-nitrogen: add lt8912 MIPI-DSI to HDMI Adrien Grassein
2021-03-30 8:35 ` [PATCH v1 4/4] arm64: defconfig: Enable LT8912B DRM bridge driver Adrien Grassein
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=20210330083514.5874-1-adrien.grassein@gmail.com \
--to=adrien.grassein@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).