From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] DT updates for Hummingboard and new Cubox-i
Date: Fri, 24 Jan 2014 23:09:31 +0800 [thread overview]
Message-ID: <20140124150927.GA2780@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <20140119185246.GB28056@quad.lixom.net>
On Sun, Jan 19, 2014 at 10:52:46AM -0800, Olof Johansson wrote:
> I'm well aware that the DT branch has not been merged, and that's because
> there has been no consensus from DT maintainers on the massive rework
> you did as the base of the branch.
I guess the 'massive rework' you're talking about is the patch series
that begins with 'ARM: dts: imx6qdl: make pinctrl nodes board specific'?
If so, I hope you would agree that we're trying to solve a real
problem [1], even though the solution does not look like the best to
you.
So which specific part of the solution are you objecting to? Those
MX6QDL_*_PINGRP macros defined in imx6qdl-pingrp.h? If that's the
case, I can send a follow-up patch to kill the macros by filling in the
pin group definitions directly. The pros is that the pin group
definitions for given board will be more intuitive, and the cons is that
the change set will be even more massive, because the same multi-lines
pin group definitions will be duplicated in multiple board dts files,
which use the same group of pins for given device.
Or any other better idea?
>
> Given the timing, it's not looking like it will be resolved in time for
> the 3.14 merge window (which might open today).
That's frustrating and will be surprising a lot of people who expect to
see their board support in 3.14 release.
Shawn
[1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/275912/
next prev parent reply other threads:[~2014-01-24 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 18:22 [PATCH 0/2] DT updates for Hummingboard and new Cubox-i Russell King - ARM Linux
2014-01-16 18:22 ` [PATCH 1/2] ARM: move flexcan1 configuration to hummingboard Russell King
2014-01-19 3:26 ` Shawn Guo
2014-01-16 18:22 ` [PATCH 2/2] ARM: add DT support for cubox-i platforms Russell King
2014-01-19 3:18 ` [PATCH 0/2] DT updates for Hummingboard and new Cubox-i Shawn Guo
2014-01-19 18:52 ` Olof Johansson
2014-01-20 0:44 ` Russell King - ARM Linux
2014-01-20 3:34 ` Olof Johansson
2014-01-20 9:55 ` Russell King - ARM Linux
2014-01-20 20:47 ` Olof Johansson
2014-01-20 21:06 ` Russell King - ARM Linux
2014-01-24 15:09 ` Shawn Guo [this message]
2014-01-25 3:44 ` Olof Johansson
2014-01-27 8:16 ` Lucas Stach
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=20140124150927.GA2780@S2101-09.ap.freescale.net \
--to=shawn.guo@linaro.org \
--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