linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 2 Oct 2014 14:48:07 +0200	[thread overview]
Message-ID: <20141002124807.GC4039@lukather> (raw)
In-Reply-To: <54296D8B.3080304@gmail.com>

On Mon, Sep 29, 2014 at 03:32:43PM +0100, Iain Paton wrote:
> On 29/09/14 14:25, Maxime Ripard wrote:
> > On Mon, Sep 29, 2014 at 01:56:49PM +0100, Iain Paton wrote:
> 
> >> 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
> 
> Ok, I'll pull those on top of something not quite as bleeding edge as linux-next
> 
> > 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.
> 
> I moved my root disk to a SATA drive, so only a minor inconvenience.
> 
> dmesg shows the following with the regulators node as in the v2 patch, 
> the bottom half being mostly what I'd expect
> 
> [    0.868607] sunxi-rtc 1c20d00.rtc: RTC enabled
> [    0.877062] Adding alias for supply acin,(null) -> acin,0-0034
> [    0.882948] Adding alias for supply vin2,(null) -> vin2,0-0034
> [    0.888775] Adding alias for supply vin3,(null) -> vin3,0-0034
> [    0.894612] Adding alias for supply ldo24in,(null) -> ldo24in,0-0034
> [    0.900956] Adding alias for supply ldo3in,(null) -> ldo3in,0-0034
> [    0.907160] Adding alias for supply ldo5in,(null) -> ldo5in,0-0034
> [    0.914029] LDO1: 1300 mV 
> [    0.917428] LDO2: 1800 <--> 3300 mV at 3000 mV 
> [    0.922483] LDO3: 700 <--> 3500 mV at 2275 mV 
> [    0.927136] LDO4: 1250 <--> 3300 mV at 2800 mV 
> [    0.932334] LDO5: 1800 <--> 3300 mV at 2800 mV 
> [    0.937308] DCDC2: 1400 mV 
> [    0.940552] DCDC3: 1250 mV 
> [    0.943474] axp20x 0-0034: AXP20X driver loaded

No, it's not. You don't have the parenting relationship between the
regulators, and you shouldn't use the aliases anymore.

Like I said, you'd better drop that part until things settle down.

> > The SD card issue is more troublesome. We'll have to look into it.
> 
> dmesg shows the mmc driver loading:
> 
> [    0.957716] sdhci: Secure Digital Host Controller Interface driver
> [    0.963963] sdhci: Copyright(c) Pierre Ossman
> [    0.968843] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found
> [    0.974918] sunxi-mmc 1c0f000.mmc: Got CD GPIO
> [    1.012036] sunxi-mmc 1c0f000.mmc: base:0xf00ac000 irq:64
> [    1.017623] sdhci-pltfm: SDHCI platform and OF driver helper
> 
> however on an older, working, kernel I get a number on the end of 
> the 'Got CD GPIO' line like this:
> 
> [    0.896271] sunxi-mmc 1c0f000.mmc: Got CD GPIO #225.

That's interesting. It seems like it might be related to the recent
breakages in the boot farm on the A31. These breakages were not
happening on the arm-soc branch, but on linux-next only, so it must be
coming from somewhere else, which is not that great, but rules out the
DTS.

I'll bisect it this weekend, but don't worry too much about it.

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/20141002/8ef224cc/attachment.sig>

  reply	other threads:[~2014-10-02 12:48 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
2014-09-29 14:32       ` Iain Paton
2014-10-02 12:48         ` Maxime Ripard [this message]
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=20141002124807.GC4039@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).