From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sun7i: add support for A20-OLinuXino-Lime2
Date: Mon, 29 Sep 2014 15:25:43 +0200 [thread overview]
Message-ID: <20140929132543.GC4081@lukather> (raw)
In-Reply-To: <54295711.9010901@gmail.com>
On Mon, Sep 29, 2014 at 01:56:49PM +0100, Iain Paton wrote:
> On 28/09/14 17:43, Maxime Ripard wrote:
> > On Sun, Sep 28, 2014 at 02:18:31PM +0100, Iain Paton wrote:
>
> >> +
> >> + i2c0: i2c at 01c2ac00 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&i2c0_pins_a>;
> >> + status = "okay";
> >> +
> >> + axp209: pmic at 34 {
> >> + compatible = "x-powers,axp209";
> >> + reg = <0x34>;
> >> + interrupt-parent = <&nmi_intc>;
> >> + interrupts = <0 8>;
> >> +
> >> + interrupt-controller;
> >> + #interrupt-cells = <1>;
> >
> > It would be greate if you could add the regulators used on the board
> > here.
> >
> > You might want to hold off a bit until the merge window is out, since
> > some patches useful for this are still pending, or based your patch on
> > top of linux-next
>
> I'll take a bash at it, although as there seems to be no binding doc
> for the driver and I can't find any other board that has axp209
> regulators defined I may need a bit of help to get this right.
Hmmm, that's odd. I was 100% sure it had one, but now that you mention
it, I can't find it either.
I should find where that patch went, and merge it then...
> What additional patches are we talking about? The following:
> regulator: axp20x: Use parent device as regulator configuration device
> i2c: mv64xxx: continue probe when clock-frequency is missing
> or are there others I'd need to pick out of linux-next?
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/288901.html
> linux-next 20140926 doesn't build for me:
>
> LD init/built-in.o
> kernel/built-in.o: In function `cputime_adjust':
> :(.text+0x25588): undefined reference to `__bad_cmpxchg'
> :(.text+0x255f8): undefined reference to `__bad_cmpxchg'
> /data/linux/source/linux-next-org/Makefile:956: recipe for target 'vmlinux' failed
>
> I suppose as a result of https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/kernel/sched/cputime.c?id=eb1b4af0a64ac7bb0ee36f579c1c7cefcbc3ac2c
>
> having reverted that one, the resulting kernel doesn't want to talk
> to my SD card. Both your tree and 3.16 work fine though.
Leave it out then. If you have no way to test it, it's going to be
very bug prone, and we can always add it later.
The SD card issue is more troublesome. We'll have to look into it.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140929/1498a8f5/attachment.sig>
next prev parent reply other threads:[~2014-09-29 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 13:18 [PATCH] ARM: sun7i: add support for A20-OLinuXino-Lime2 Iain Paton
2014-09-28 16:43 ` Maxime Ripard
2014-09-29 12:56 ` Iain Paton
2014-09-29 13:25 ` Maxime Ripard [this message]
2014-09-29 14:32 ` Iain Paton
2014-10-02 12:48 ` Maxime Ripard
2014-10-05 22:40 ` [PATCH v3 ] " Iain Paton
2014-10-06 9:20 ` Maxime Ripard
2014-10-09 10:27 ` [PATCH v4] " Iain Paton
2014-10-09 19:56 ` Maxime Ripard
2014-10-10 13:15 ` [PATCH v5] " Iain Paton
2014-10-10 13:55 ` Maxime Ripard
2014-10-10 13:15 ` [PATCH v4] " Iain Paton
2014-10-10 13:56 ` Maxime Ripard
2014-10-11 14:00 ` Andreas Färber
2014-10-06 8:56 ` [PATCH] " Javier Martinez Canillas
2014-10-06 9:11 ` Maxime Ripard
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=20140929132543.GC4081@lukather \
--to=maxime.ripard@free-electrons.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).