From: Fabio Estevam <festevam@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH 03/13] ARM: imx27: Retrieve the SYSCTRL base address from devicetree
Date: Wed, 16 Sep 2020 18:36:25 -0300 [thread overview]
Message-ID: <CAOMZO5BXB_jvb3RYWBnQBw0Td-r+aco1Stdww0RRrea+t8ns2g@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1WfTU3Z8Tq5=rXjygW7+7VkLs1QFDyBgaHqUcsSNeXow@mail.gmail.com>
Hi Arnd,
On Wed, Sep 16, 2020 at 6:30 PM Arnd Bergmann <arnd@arndb.de> wrote:
> While this is nicer in theory, I don't like the way it breaks compatibility
> with old dtb files that are lacking the device node.
Good point. Let me access this SYSCTRL region via the CCM register space then.
In the current devicetree CCM region already overlaps with the SYSCTRL region.
This way we don't break dt compatibility.
> What is the status of dtb stability otherwise on imx? My impression
> was that it is actually quite good about not breaking this way.
Yes, we try to keep dt compatibility as much as possible.
Thanks
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-16 21:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 20:55 [PATCH 00/13] ARM: imx: Further cleanups due to dt-only conversion Fabio Estevam
2020-09-16 20:55 ` [PATCH 01/13] ARM: dts: imx27: Fix the register range for CCM Fabio Estevam
2020-09-16 20:55 ` [PATCH 02/13] ARM: dts: imx27: Add the SYSCTRL description Fabio Estevam
2020-09-16 20:55 ` [PATCH 03/13] ARM: imx27: Retrieve the SYSCTRL base address from devicetree Fabio Estevam
2020-09-16 21:30 ` Arnd Bergmann
2020-09-16 21:36 ` Fabio Estevam [this message]
2020-09-16 20:55 ` [PATCH 04/13] ARM: imx27: Retrieve the CCM " Fabio Estevam
2020-09-16 20:55 ` [PATCH 05/13] ARM: imx31: Retrieve the IIM " Fabio Estevam
2020-09-16 20:55 ` [PATCH 06/13] ARM: imx3: Retrieve the CCM " Fabio Estevam
2020-09-16 20:55 ` [PATCH 07/13] ARM: imx3: Retrieve the AVIC " Fabio Estevam
2020-09-16 20:55 ` [PATCH 08/13] ARM: imx35: Retrieve the IIM " Fabio Estevam
2020-09-16 20:55 ` [PATCH 09/13] ARM: imx: Remove unused IO_ADDRESS() macros Fabio Estevam
2020-09-16 21:34 ` Arnd Bergmann
2020-09-16 21:56 ` Fabio Estevam
2020-09-17 7:16 ` Arnd Bergmann
2020-09-17 10:17 ` Fabio Estevam
2020-09-29 13:11 ` Linus Walleij
2020-09-29 13:21 ` Arnd Bergmann
2020-09-30 9:34 ` Linus Walleij
2020-09-16 20:55 ` [PATCH 10/13] clk: imx: imx27: Remove mx27_clocks_init() Fabio Estevam
2020-09-16 20:55 ` [PATCH 11/13] clk: imx: imx31: Remove mx31_clocks_init() Fabio Estevam
2020-09-16 20:55 ` [PATCH 12/13] clk: imx: imx35: Remove mx35_clocks_init() Fabio Estevam
2020-09-16 20:55 ` [PATCH 13/13] clk: imx: imx21: Remove clock driver 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=CAOMZO5BXB_jvb3RYWBnQBw0Td-r+aco1Stdww0RRrea+t8ns2g@mail.gmail.com \
--to=festevam@gmail.com \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).