From: Baruch Siach <baruch@tkos•co.il>
To: Russell King <linux@armlinux•org.uk>,
Shawn Guo <shawnguo@kernel•org>,
Sascha Hauer <s.hauer@pengutronix•de>,
Pengutronix Kernel Team <kernel@pengutronix•de>,
Fabio Estevam <fabio.estevam@nxp•com>,
NXP Linux Team <linux-imx@nxp•com>
Cc: Baruch Siach <baruch@tkos•co.il>,
Jon Nettleton <jon@solid-run•com>,
linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] ARM: dts: hummingboard2: fixes and improvements
Date: Wed, 30 Jan 2019 18:18:37 +0200 [thread overview]
Message-ID: <cover.1548861664.git.baruch@tkos.co.il> (raw)
The first two patches fix UART on the optional mikroBUS header.
The last two patches add optional CAN and RS485 peripherals. I sent these
patches before, but they were not applied at the time:
https://patchwork.kernel.org/patch/10528011/
https://patchwork.kernel.org/patch/10528013/
Both patches are rebased here on top of the UART fixes.
Baruch Siach (4):
ARM: dts: hummingboard2: fix uart3 Rx pin conf
ARM: dts: hummingboard2: add uart3 pinmux for board rev 1.4
ARM: dts: hummingboard2: describe optional rs485
ARM: dts: hummingboard2: describe optional can bus
arch/arm/boot/dts/imx6qdl-hummingboard2.dtsi | 42 +++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)
--
2.20.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:[~2019-01-30 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:18 Baruch Siach [this message]
2019-01-30 16:18 ` [PATCH 1/4] ARM: dts: hummingboard2: fix uart3 Rx pin conf Baruch Siach
2019-01-30 16:18 ` [PATCH 2/4] ARM: dts: hummingboard2: add uart3 pinmux for board rev 1.4 Baruch Siach
2019-01-30 16:18 ` [PATCH 3/4] ARM: dts: hummingboard2: describe optional rs485 Baruch Siach
2019-01-30 16:18 ` [PATCH 4/4] ARM: dts: hummingboard2: describe optional can bus Baruch Siach
2019-01-31 6:42 ` [PATCH 0/4] ARM: dts: hummingboard2: fixes and improvements Jon Nettleton
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=cover.1548861664.git.baruch@tkos.co.il \
--to=baruch@tkos$(echo .)co.il \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=jon@solid-run$(echo .)com \
--cc=kernel@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux@armlinux$(echo .)org.uk \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=shawnguo@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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