From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] SolidRun Hummingboard/Cubox-i DT updates
Date: Mon, 25 Aug 2014 14:29:32 +0800 [thread overview]
Message-ID: <20140825062930.GA6928@dragon> (raw)
In-Reply-To: <20140823091058.GO30401@n2100.arm.linux.org.uk>
On Sat, Aug 23, 2014 at 10:10:58AM +0100, Russell King - ARM Linux wrote:
> Here's a set of patches updating the Cubox-i/Hummingboard DT files.
>
> The first two are fairly important fixes, so should at least go in
> for -rc kernels.
>
> The SPDIF patch is something which could go in -rc as well as it's a
> cosmetic patch, changing the name displayed in (eg) pulseaudio for the
> SPDIF output from the developer-centric "imx-spdif" to "Integrated SPDIF".
I will sent the first 3 for -rc. But I second Iain's comment that the
first patch should have a better commit log to explain why it's an
important fix.
>
> Patch 4 updates the Hummingboard support as SolidRun now have a Dual
> version of this platform, which needs imx6q.dtsi instead of imx6dl.dtsi,
> and also has mSATA support.
Though it's mostly just a DTS split, the diff stat looks too scary to
be a material of -rc.
>
> Patch 5 adds the mSATA support for the Dual version of the Hummingboard.
>
> Patch 6 is the first patch which breaks something on the initial version
> of the Hummingboard, aka Carrier1, specifically the IrDA receiver. In
> hindsight, we should not have used the name "Hummingboard" for the
> Carrier1. The Carrier1 is obsolete, and people are being encouraged to
> dispose of the C1 hardware.
>
> Out of these, I think it would be worth getting the first five patches
> in for 3.17 (even though we're in -rc), but patch 6 should certainly
> wait for the next merge window.
Patches 4 ~ 6 are not fixes in any way, so I prefer to queue them for
the next merge window.
Shawn
next prev parent reply other threads:[~2014-08-25 6:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 9:10 [PATCH 0/6] SolidRun Hummingboard/Cubox-i DT updates Russell King - ARM Linux
2014-08-23 9:11 ` [PATCH 1/6] ARM: dts: microsom-ar8035: MDIO pad must be set open drain Russell King
2014-08-24 9:44 ` Iain Paton
2014-08-24 9:58 ` Russell King - ARM Linux
2014-08-25 6:53 ` Eric Bénard
2014-08-26 12:08 ` Iain Paton
2014-08-26 10:15 ` Shawn Guo
2014-08-26 12:16 ` Iain Paton
2014-08-23 9:11 ` [PATCH 2/6] ARM: dts: hummingboard/cubox-i: add USB OC pinctrl configuration Russell King
2014-08-23 9:11 ` [PATCH 3/6] ARM: dts: hummingboard/cubox-i: change SPDIF output to be more descriptive Russell King
2014-08-23 9:11 ` [PATCH 4/6] ARM: dts: hummingboard: Split HummingBoard DT to support s/dl and d/q Russell King
2014-08-23 9:11 ` [PATCH 5/6] ARM: dts: hummingboard: add mSATA support for iMX6 quad/dual HummingBoard Russell King
2014-08-23 9:11 ` [PATCH 6/6] ARM: dts: hummingboard: gpio-ir on gpio 3,5 Russell King
2014-08-23 13:32 ` Fabio Estevam
2014-08-23 13:36 ` Russell King - ARM Linux
2014-08-23 13:56 ` Fabio Estevam
2014-08-23 14:33 ` Russell King - ARM Linux
2014-08-23 15:02 ` Fabio Estevam
2014-08-27 18:43 ` Russell King - ARM Linux
2014-08-28 8:42 ` Shawn Guo
2014-08-25 6:29 ` Shawn Guo [this message]
2014-08-25 9:51 ` [PATCH 0/6] SolidRun Hummingboard/Cubox-i DT updates Russell King - ARM Linux
2014-08-25 11:19 ` Shawn Guo
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=20140825062930.GA6928@dragon \
--to=shawn.guo@freescale.com \
--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).