linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH 1/3] sunxi: A20-OLinuXino-LIME2: Fix ldo3/ldo4 in DTS
Date: Mon, 28 Mar 2016 15:01:27 +0200	[thread overview]
Message-ID: <56F92B27.5050009@redhat.com> (raw)
In-Reply-To: <56F794E1.4080108@computerlinguist.org>

Hi,

On 27-03-16 10:08, Michael Haas wrote:
> On 03/26/2016 09:56 AM, Iain Paton wrote:
>> Having reread the A20 datasheet yesterday, something in the back of my
>> mind was bothering me overnight so I took some time to check this morning.
>>
>> On the lime2 schematic we see the pins labeled as follows:
>>
>> F19 : VCC_CSI0
>> E18 : VCC_CSI1
>>
>> However the A20 datasheet doesn't label them this way, instead using:
>>
>> F19 : VCC-PE : Port E Power Supply
>> E18 : VCC-PG : Port G Power Supply
>>
>> no mention at all of CSI. CSI just happens to be a function that can be
>> multiplexed onto ports E & G.
>>
>> So lets assume for a moment we don't have a CSI device, or a CSI driver
>> and are not using those pins for CSI functions but are instead using
>> their default GPIO purpose, or in the case of PG perhaps for UART3
>> or UART4.
>>
>> What happens when you disable the regulator?  Hopefully from the above
>> you'll already have worked out that you lose ports E & G when you turn
>> their I/O power supply off and anything multiplexed onto those ports
>> becomes unuseable.
>>
>
> Hi Iain,
>
> I took some time to go through the data sheets and your analysis is on
> point.
>
> I did raise an issue with Olimex via github [0]. Maybe they will update
> their schematics.
>
>
> I do have my breakout board connected to GPIO-1.. and it turns out that
> mostly port G is exposed on GPIO-1. I'll be reverting Hans' patch locally
> so I can toggle some pins today. I am sure he will contribute his own
> thoughts on the matter.
>
>
>> I've also just tested building u-boot with LDO3 & 4 voltages set to
>> 3.3v to be the same as CubieBoard, this works for lime2.
>> So it's unlikely that the 2.8v & 2.3v settings from my previous patch
>> make sense. The crash is actually being caused by something else,
>> probably sequencing, due to unnecessarily turning the regulators off.
>> Whatever the reason, we don't have enough information in the
>> datasheets to know for sure so we simply shouldn't turn them off to
>> begin with.
>
>
> I just tried that on linux and axp20x-regulator.ko refuses to set the
> voltage
> on ldo4:
>
> [   88.914653] at24 1-0050: 2048 byte 24c16 EEPROM, writable, 16 bytes/write
> [   96.893312] axp20x-i2c 0-0034: AXP20x variant AXP209 found
> [   96.910631] axp20x-i2c 0-0034: AXP20X driver loaded
> [   96.955579] input: axp20x-pek as
> /devices/platform/soc at 01c00000/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input0
> [   96.971734] ldo4: failed to apply 3300000uV constraint(-22)
> [   96.990646] axp20x-regulator axp20x-regulator: Failed to register ldo4
> [   97.012686] axp20x-regulator: probe of axp20x-regulator failed with
> error -22
>
> Perhaps this requires another patch [1],

Yes setting the constraints to 3.3v requires the patch you link for things to work.

> but unless there's a real need
> for me to verify this,
> I'll simply revert the u-boot patch and enjoy working GPIO.

Given the entire discussion in this thread, I agree that fixing this in u-boot
is best. But I do not see reverting the u-boot patch disabling ldo3/4 by default
as the solution. ldo3/4 are unused on most boards, so disabling them by default
clearly is the right thing todo IMHO.

Instead please submit a patch for configs/A20-OLinuXino-Lime2_defconfig which
configures them at 2800 mV there (per the Lime2 schematic).

It would be good to also check the Lime1 schematic if they are used in the same
way there, I would also welcome a patch for:

configs/A10-OLinuXino-Lime_defconfig
configs/A20-OLinuXino-Lime_defconfig

Regards,

Hans

  reply	other threads:[~2016-03-28 13:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 19:04 [PATCH 1/3] sunxi: A20-OLinuXino-LIME2: Fix ldo3/ldo4 in DTS Michael Haas
2016-03-25 19:04 ` [PATCH 2/3] sunxi: A20-OLinuXino-LIME2: Add usb-power-supply Michael Haas
2016-03-26  0:48   ` [linux-sunxi] " Iain Paton
2016-04-02 10:36   ` Maxime Ripard
2016-05-01  6:46     ` [linux-sunxi] " Michael Haas
2016-05-02 11:07       ` Maxime Ripard
2016-03-25 19:04 ` [PATCH 3/3] sunxi: A20-OLinuXino-LIME2: Add i2c2 bus in DTS Michael Haas
2016-03-26  0:48   ` [linux-sunxi] " Iain Paton
2016-04-02 10:34   ` Maxime Ripard
2016-04-02 14:42     ` [linux-sunxi] " Priit Laes
2016-04-02 16:21     ` Michael Haas
2016-04-10 10:32       ` Maxime Ripard
2016-03-26  0:58 ` [linux-sunxi] [PATCH 1/3] sunxi: A20-OLinuXino-LIME2: Fix ldo3/ldo4 " Iain Paton
2016-03-26  8:56   ` Iain Paton
2016-03-27  8:08     ` Michael Haas
2016-03-28 13:01       ` Hans de Goede [this message]
2016-03-29 12:03         ` 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=56F92B27.5050009@redhat.com \
    --to=hdegoede@redhat.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).