From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: christianshewitt@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
tobetter@hardkernel.com
Subject: Re: [PATCH v2 0/3] arm64: dts: meson: add support for ODROID-N2+
Date: Fri, 18 Sep 2020 13:39:56 -0700 [thread overview]
Message-ID: <160046158476.39596.3643985967347076144.b4-ty@baylibre.com> (raw)
In-Reply-To: <20200915152432.30616-1-narmstrong@baylibre.com>
On Tue, 15 Sep 2020 17:24:29 +0200, Neil Armstrong wrote:
> This series splits the existing meson-g12b-odroid-n2.dts into a common
> dtsi and dts, and then adds new bindings and dts for the ODROID-N2+
> which uses an Amlogic S922X rev.C chip that Hardkernel supports with
> the same OPPs as the A311D.
>
> Changes since v1 at [1]:
> - rebase on khilman's v5.10/dt64
> - get all review tags from v1
> - use the A311D OPPs, after review of Vendor kernel, the Rev, C uses the same OPPs (freq + voltage)
> as the A311D SoC of the same family
>
> [...]
Applied, thanks!
[1/3] arm64: dts: meson: convert ODROID-N2 to dtsi
commit: ef599f5f3e10bf1979d8ece29fd7fa511fedd59d
[2/3] dt-bindings: arm: amlogic: add support for the ODROID-N2+
commit: 88ba71cdc5497390350c87e68ce35688e88be3e8
[3/3] arm64: dts: meson: add support for the ODROID-N2+
commit: 98d24896ee117b1f0969405476c943e9307e30d4
Best regards,
--
Kevin Hilman <khilman@baylibre.com>
prev parent reply other threads:[~2020-09-18 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:24 Neil Armstrong
2020-09-15 15:24 ` [PATCH v2 1/3] arm64: dts: meson: convert ODROID-N2 to dtsi Neil Armstrong
2020-09-15 15:24 ` [PATCH v2 2/3] dt-bindings: arm: amlogic: add support for the ODROID-N2+ Neil Armstrong
2020-09-15 15:24 ` [PATCH v2 3/3] arm64: dts: meson: " Neil Armstrong
2020-09-15 19:35 ` [PATCH v2 0/3] arm64: dts: meson: add support for ODROID-N2+ Martin Blumenstingl
2020-09-18 20:39 ` 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=160046158476.39596.3643985967347076144.b4-ty@baylibre.com \
--to=khilman@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=tobetter@hardkernel.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®