From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: imx53: Add 'ARM platform' node
Date: Thu, 28 Jun 2018 09:35:32 +0800 [thread overview]
Message-ID: <20180628013530.GE22683@dragon> (raw)
In-Reply-To: <1529329939-14117-1-git-send-email-festevam@gmail.com>
On Mon, Jun 18, 2018 at 10:52:17AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
>
> As per the i.MX53 Reference Manual add an entry for the
> 'ARM platform' region in the device tree.
>
> This is needed for accessing the ARM_GPC register to set the
> DBGEN bit, so that the debug clocks can be turned on.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
> arch/arm/boot/dts/imx53.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx53.dtsi b/arch/arm/boot/dts/imx53.dtsi
> index 1a7a7bb..a70fbf4 100644
> --- a/arch/arm/boot/dts/imx53.dtsi
> +++ b/arch/arm/boot/dts/imx53.dtsi
> @@ -672,6 +672,11 @@
> status = "disabled";
> };
>
> + arm_platform: arm-platform at 63fa0000 {
> + compatible = "fsl,imx53-arm-plat", "fsl,imx51-arm-plat";
Don't we need a bindings for that?
Shawn
> + reg = <0x63fa0000 0x28>;
> + };
> +
> owire: owire at 63fa4000 {
> compatible = "fsl,imx53-owire", "fsl,imx21-owire";
> reg = <0x63fa4000 0x4000>;
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-06-28 1:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 13:52 [PATCH 1/3] ARM: dts: imx53: Add 'ARM platform' node Fabio Estevam
2018-06-18 13:52 ` [PATCH 2/3] ARM: dts: imx53: Add a label for the PMU node Fabio Estevam
2018-06-19 15:49 ` Sebastian Reichel
2018-06-18 13:52 ` [PATCH 3/3] ARM: mx5: Set the DBGEN bit in ARM_GPC register Fabio Estevam
2018-06-19 15:50 ` Sebastian Reichel
2018-06-19 15:49 ` [PATCH 1/3] ARM: dts: imx53: Add 'ARM platform' node Sebastian Reichel
2018-06-28 1:35 ` Shawn Guo [this message]
2018-06-28 3:02 ` Fabio Estevam
2018-06-28 3:21 ` Shawn Guo
2018-07-10 14:01 ` Fabio Estevam
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=20180628013530.GE22683@dragon \
--to=shawnguo@kernel.org \
--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