From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] Meson8b: Odroid-C1 improvements
Date: Wed, 26 Sep 2018 10:52:00 +0200 [thread overview]
Message-ID: <7h8t3o63pr.fsf@baylibre.com> (raw)
In-Reply-To: <20180913202919.20927-1-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Thu, 13 Sep 2018 22:29:15 +0200")
Martin Blumenstingl <martin.blumenstingl@googlemail•com> writes:
> This is a small collection of improvements for the Odroid-C1 board.
> My main goal is to prepare the CPU voltage regulator as I'm using
> the Odroid-C1 to test my changes which will enable CPU frequency
> scaling on Meson8/Meson8b/Meson8m2.
>
> While I was going through the schematics anyways I added more
> regulators, enabled the SAR ADC and added the /chosen/stdout-path
> property to make debugging with "earlycon" easier.
>
> schematics for the board are published by Hardkernel and can be found
> here: [0]
>
> NOTE: This series depends on my patch "ARM: dts: meson8b: add the
> I2C_A, PWM_C and UART_B pins" [1] from my other series called
> "Meson8b: add support for the Endless Mini EC-100" as this defines
> the "pwm_c1_pins" for the CPU voltage regulator (which is controlled
> via PWM).
Applied to v4.20/dt (on top of the Endless series)
Thanks for pointing out the dependencies,
Kevin
prev parent reply other threads:[~2018-09-26 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 20:29 [PATCH 0/4] Meson8b: Odroid-C1 improvements Martin Blumenstingl
2018-09-13 20:29 ` [PATCH 1/4] ARM: dts: meson8b: odroidc1: add the CPU voltage regulator Martin Blumenstingl
2018-09-13 20:29 ` [PATCH 2/4] ARM: dts: meson8b: odroidc1: add the fixed voltage regulators Martin Blumenstingl
2018-09-13 20:29 ` [PATCH 3/4] ARM: dts: meson8b: odroidc1: enable the SAR ADC Martin Blumenstingl
2018-09-13 20:29 ` [PATCH 4/4] ARM: dts: meson8b: odroidc1: add stdout-path property Martin Blumenstingl
2018-09-26 8:52 ` Kevin Hilman [this message]
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=7h8t3o63pr.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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