From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] ARM: dts: imx6qdl: make pinctrl nodes board specific
Date: Thu, 31 Oct 2013 16:09:01 +0000 [thread overview]
Message-ID: <20131031160901.GD16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHCPf3vTcu9RCk8=9MUs4nkyJ-8jevh5koxfzdLzE5+qM0ZspQ@mail.gmail.com>
On Thu, Oct 31, 2013 at 10:45:08AM -0500, Matt Sealey wrote:
> I suggested this to Shawn a couple weeks ago and got a bit of pushback.
>
> There's probably a ton more to do in this regard to keep the DT
> per-board more concise, but this drops tree size by a respectable
> amount on i.MX51 too (just on a tree I have internally, it's something
> like 8.5KiB) and I can't see any redundant data in the ones he
> patched.
The issue I have is that this pushes support for Carrier-1 through to
_six_ months before it appears in a mainline -final kernel - the timeline
ends up looking like this:
- Prepare and merge this patch to allow DAT3 to be configured in the
merge window starting next week.
- Rebase Carrier-1 changes on that when it hits mainline
- Wait for 3.13-rc1
- Get Carrier-1 DT files merged into the IMX tree for the following
merge window at some point
- Wait for v3.13 to be released about three months from now.
- Carrier-1 support gets merged into mainline
- Carrier-1 support appears in v3.14 three months after that.
That's an awfully long turn-around time given that the DT description
is functional today, and has been for the last month, and the only
thing that's really blocking it is the problems of that DAT3 signal.
next prev parent reply other threads:[~2013-10-31 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 3:42 [PATCH RFC] ARM: dts: imx6qdl: make pinctrl nodes board specific Shawn Guo
2013-10-28 13:30 ` Dirk Behme
2013-10-29 2:31 ` Shawn Guo
2013-10-31 8:03 ` Sascha Hauer
2013-10-31 10:29 ` Russell King - ARM Linux
2013-10-31 15:45 ` Matt Sealey
2013-10-31 16:09 ` Russell King - ARM Linux [this message]
2013-10-31 20:11 ` Matt Sealey
2013-11-01 8:33 ` Shawn Guo
2013-11-04 22:50 ` Matt Sealey
2013-11-05 2:06 ` Shawn Guo
2013-11-05 22:00 ` Matt Sealey
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=20131031160901.GD16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).