From: Neil Armstrong <narmstrong@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: khilman@baylibre.com, linux-amlogic@lists.infradead.org,
Guillaume La Roque <glaroque@baylibre.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 06/11] arm64: dts: meson-g12a-x96-max: add regulators
Date: Tue, 19 Mar 2019 21:30:18 +0100 [thread overview]
Message-ID: <56b69e23-6844-eb89-7198-fd2ecf307391@baylibre.com> (raw)
In-Reply-To: <CAFBinCDj=5VpoJGKVGw5bG50EaBHgKz=WLtSwNVVWXtzfoiQ9A@mail.gmail.com>
On 19/03/2019 21:13, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Tue, Mar 19, 2019 at 9:29 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> On 18/03/2019 21:13, Martin Blumenstingl wrote:
>>> Hi Neil,
>>>
>>> On Mon, Mar 18, 2019 at 11:06 AM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>>>
>>>> From: Guillaume La Roque <glaroque@baylibre.com>
>>>>
>>>> Add system regulators for the X96 Max Set-Top-Box.
>>>>
>>>> Still missing
>>>> * VDD_EE (0.8V - PWM controlled)
>>>> * VDD_CPU (PWM controlled)
>>>>
>>>> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
>>>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>>>> ---
>>>> .../boot/dts/amlogic/meson-g12a-x96-max.dts | 67 +++++++++++++++++++
>>>> 1 file changed, 67 insertions(+)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a-x96-max.dts b/arch/arm64/boot/dts/amlogic/meson-g12a-x96-max.dts
>>>> index 0edbd00b358f..5c37930b09e2 100644
>>>> --- a/arch/arm64/boot/dts/amlogic/meson-g12a-x96-max.dts
>>>> +++ b/arch/arm64/boot/dts/amlogic/meson-g12a-x96-max.dts
>>> [...]
>>>> + vcc_5v: regulator-vcc_5v {
>>>> + compatible = "regulator-fixed";
>>>> + regulator-name = "VCC_5V";
>>>> + regulator-min-microvolt = <5000000>;
>>>> + regulator-max-microvolt = <5000000>;
>>>> + vin-supply = <&dc_in>;
>>>> +
>>>> + gpio = <&gpio GPIOH_8 GPIO_OPEN_DRAIN>;
>>>> + enable-active-high;
>>> is there any way to test whether this GPIO is the right one?
>>> I couldn't find a reference to a GPIOH_8 regulator in
>>> buildroot_openlinux_kernel_4.9_fbdev_20180706
>>
>> The x96 is based on the U212 reference design, and the GPIOH_8 controls the 5V_EN signal,
>> but you are right, it's the wrong polarity here, it should be enable-active-low instead.
>> (FYI The SEI510 does not use this at all, 5V is always enabled)
>>
>> The schematics describes :
>> VCC5V_EN (GPIOH_8-Hiz OD): 5V_EN
>> L: Enable
>> Hiz: Disable
> thank you for this explanation!
>
>> FYI, the GPIOH_8 is Open-Drain only, this means this pin cannot pull to TTL 1, only to TTL 0
>> or set as input. We need to add a way to describe this in the pinctrl driver somehow....
> as far as I understand the pinctrl driver changes would result in an
> error when the GPIO is used with "active high" (making incompatible
> drivers or .dts easier to see). is this correct?
I don't have a clear view of that, since it's really GPIO related.
I don't know if we can really disable non-opendrain support for a
specific gpio.
We will need to investigate ! Anyway, using GPIO_OPEN_DRAIN in DT
is the correct way to handle these GPIO lines.
Neil
>
>> I will send a fix on v3
>>
>> I didn't notice because I power the board using a Type-A to Type-A connector,
>> and the 5V from the USB port bypasses this regulator...
> this is good to know.
> I'm also powering some of my boards using a Type-A to Type-A
> connector. I'll need to remember this and this whether boards are
> still booting with the DC plug
>
>
> Regards
> Martin
>
next prev parent reply other threads:[~2019-03-19 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:04 [PATCH v2 00/11] arm64: dts: g12a: Add boards peripherals Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 01/11] arm64: dts: meson-g12a-u200: add uart_AO pinctrl Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 02/11] arm64: dts: meson-g12a-sei510: " Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 03/11] arm64: dts: meson-g12a-x96-max: " Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 04/11] arm64: dts: meson-g12a-u200: add regulators Neil Armstrong
2019-03-18 20:07 ` Martin Blumenstingl
2019-04-09 10:18 ` Neil Armstrong
2019-04-16 0:49 ` Kevin Hilman
2019-03-18 10:04 ` [PATCH v2 05/11] arm64: dts: meson-g12a-sei510: " Neil Armstrong
2019-03-18 20:06 ` Martin Blumenstingl
2019-03-18 10:04 ` [PATCH v2 06/11] arm64: dts: meson-g12a-x96-max: " Neil Armstrong
2019-03-18 20:13 ` Martin Blumenstingl
2019-03-19 8:29 ` Neil Armstrong
2019-03-19 20:13 ` Martin Blumenstingl
2019-03-19 20:30 ` Neil Armstrong [this message]
2019-03-18 10:04 ` [PATCH v2 07/11] arm64: dts: meson-g12a-x96-max: Enable BT Module Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 08/11] arm64: dts: meson-g12a-sei510: Add ADC Key and BT support Neil Armstrong
2019-03-18 20:17 ` Martin Blumenstingl
2019-03-18 10:04 ` [PATCH v2 09/11] arm64: dts: meson-g12a-sei510: Enable USB Neil Armstrong
2019-03-18 20:13 ` Martin Blumenstingl
2019-03-18 10:04 ` [PATCH v2 10/11] arm64: dts: meson-g12a-u200: " Neil Armstrong
2019-03-18 10:04 ` [PATCH v2 11/11] arm64: dts: meson-g12a-x96-max: " Neil Armstrong
2019-03-18 20:13 ` Martin Blumenstingl
2019-03-23 0:14 ` [PATCH v2 00/11] arm64: dts: g12a: Add boards peripherals Kevin Hilman
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=56b69e23-6844-eb89-7198-fd2ecf307391@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
/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
all inboxes | Powered by JetHome®