From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] ARM: omap3-lilly-a83x: update board support
Date: Thu, 22 May 2014 16:28:55 -0700 [thread overview]
Message-ID: <20140522232854.GD29577@atomide.com> (raw)
In-Reply-To: <1400799986-20043-1-git-send-email-chf.fritz@googlemail.com>
* Christoph Fritz <chf.fritz@googlemail.com> [140522 16:07]:
> This set of patches updates board support for omap3-lilly-a83x.
>
> Christoph Fritz (5):
> [RFC-HACK] pinctrl-single: init by postcore_initcall()
I would prefer to start initializing other things later as
then we get proper error messages on the console. Let's first
investigate a bit more if we can just initialize other
drivers later on.
Which version of kernel are you using? With all the fixes
that have gone into this -rc cycle, v3.15-rc4 is pretty much
the first kernel that should behave for us properly for
deferred probe for irqchips that get initialized later on.
Regards,
Tony
> [RFC-HACK] ARM: dts: OMAP3: reorder pinmux_gpio1_pins
> ARM: dts: omap3: set mcbsp2 status
> [RFC] ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable
> ARM: dts: OMAP3 a83x: fix duplicate usb pin config
>
> arch/arm/boot/dts/omap3-lilly-a83x.dtsi | 7 +++---
> arch/arm/boot/dts/omap34xx.dtsi | 28 ++++++++++++----------
> arch/arm/boot/dts/omap36xx.dtsi | 40 ++++++++++++++++---------------
> arch/arm/mach-omap2/gpmc-nand.c | 16 +++++--------
> drivers/pinctrl/pinctrl-single.c | 15 ++++++++++++
> 5 files changed, 61 insertions(+), 45 deletions(-)
>
> --
> 1.7.10.4
>
next prev parent reply other threads:[~2014-05-22 23:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 23:06 [PATCH 0/5] ARM: omap3-lilly-a83x: update board support Christoph Fritz
2014-05-22 23:06 ` [PATCH 1/5] [RFC-HACK] pinctrl-single: init by postcore_initcall() Christoph Fritz
2014-05-22 23:31 ` Tony Lindgren
2014-07-16 11:45 ` Ezequiel Garcia
2014-07-16 12:36 ` Tony Lindgren
2014-07-16 13:30 ` Ezequiel Garcia
2014-05-22 23:06 ` [PATCH 2/5] [RFC-HACK] ARM: dts: OMAP3: reorder pinmux_gpio1_pins Christoph Fritz
2014-05-22 23:32 ` Tony Lindgren
2014-05-22 23:06 ` [PATCH 3/5] ARM: dts: omap3: set mcbsp2 status Christoph Fritz
2014-05-27 20:40 ` Tony Lindgren
2014-05-22 23:06 ` [PATCH 4/5] [RFC] ARM: OMAP2+: gpmc: fix gpmc_hwecc_bch_capable Christoph Fritz
2014-05-27 7:16 ` Gupta, Pekon
2014-07-08 6:25 ` Gupta, Pekon
2014-07-10 10:44 ` Christoph Fritz
2014-05-22 23:06 ` [PATCH 5/5] ARM: dts: OMAP3 a83x: fix duplicate usb pin config Christoph Fritz
2014-05-27 20:40 ` Tony Lindgren
2014-05-22 23:28 ` Tony Lindgren [this message]
2014-05-23 0:24 ` [PATCH 0/5] ARM: omap3-lilly-a83x: update board support Christoph Fritz
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=20140522232854.GD29577@atomide.com \
--to=tony@atomide.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).