From: Kevin Hilman <khilman@baylibre.com>
To: Jianxin Pan <jianxin.pan@amlogic.com>
Cc: <linux-amlogic@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Carlo Caione <carlo@caione.org>, Jian Hu <jian.hu@amlogic.com>,
Yixun Lan <yixun.lan@amlogic.com>,
Hanjie Lin <hanjie.lin@amlogic.com>,
Qiufang Dai <qiufang.dai@amlogic.com>,
Victor Wan <victor.wan@amlogic.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] arm64: dts: meson-g12a: Introduce new DT files for Meson-G12A SoC
Date: Wed, 26 Sep 2018 11:08:18 +0200 [thread overview]
Message-ID: <7hzhw44oe5.fsf@baylibre.com> (raw)
In-Reply-To: <1537518881-53137-1-git-send-email-jianxin.pan@amlogic.com> (Jianxin Pan's message of "Fri, 21 Sep 2018 16:34:39 +0800")
Jianxin Pan <jianxin.pan@amlogic.com> writes:
> This attempt will try to add new DT files to support Meson-G12A SoC.
>
> 1) first, Please notice that, in this patch series, the DT node about 16M reserved
> memory for hwrom is removed, since it's not needed by G12A SoC.
> 2) second, the pclk for uart_AO need to be fixed once G12A clock_ao driver is
> merged. In this version, it rely on bootloader to enable the pclk gate which
> belong to AO clock domain. Please add clk_ignore_unused to bootargs.
Applied to v4.20/dt64, added Neils' Reviewed-by tag.
Kevin
prev parent reply other threads:[~2018-09-26 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 8:34 [PATCH v5 0/2] arm64: dts: meson-g12a: Introduce new DT files for Meson-G12A SoC Jianxin Pan
2018-09-21 8:34 ` [PATCH v5 1/2] dt-bindings: arm: amlogic: Add Meson G12A binding Jianxin Pan
2018-09-21 8:34 ` [PATCH v5 2/2] arm64: dts: meson-g12a: add initial g12a s905d2 SoC DT support Jianxin Pan
2018-09-21 8:38 ` [PATCH v5 0/2] arm64: dts: meson-g12a: Introduce new DT files for Meson-G12A SoC Neil Armstrong
2018-09-26 9:08 ` 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=7hzhw44oe5.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=hanjie.lin@amlogic.com \
--cc=jbrunet@baylibre.com \
--cc=jian.hu@amlogic.com \
--cc=jianxin.pan@amlogic.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=qiufang.dai@amlogic.com \
--cc=robh+dt@kernel.org \
--cc=victor.wan@amlogic.com \
--cc=yixun.lan@amlogic.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