From: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Anson Huang <b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V4 1/6] ARM: dts: imx6q: add common compatible name for reused modules
Date: Mon, 13 Jan 2014 13:10:16 +0100 [thread overview]
Message-ID: <20140113121016.GJ16215@pengutronix.de> (raw)
In-Reply-To: <1389614031-7253-1-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Mon, Jan 13, 2014 at 07:53:46PM +0800, Anson Huang wrote:
> As some modules are common for all i.MX6 SOCs, to avoid
> checking cpu type for drivers that needs them, just add a
> new compatible name for them.
>
> Signed-off-by: Anson Huang <b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> ---
> arch/arm/boot/dts/imx6q.dtsi | 2 +-
> arch/arm/boot/dts/imx6qdl.dtsi | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
> index 021e0cb..5bc79c7 100644
> --- a/arch/arm/boot/dts/imx6q.dtsi
> +++ b/arch/arm/boot/dts/imx6q.dtsi
> @@ -91,7 +91,7 @@
> };
>
> iomuxc: iomuxc@020e0000 {
> - compatible = "fsl,imx6q-iomuxc";
> + compatible = "fsl,imx6q-iomuxc", "fsl,iomuxc";
>
> ipu2 {
> pinctrl_ipu2_1: ipu2grp-1 {
> diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
> index 8a86502..cb9129b 100644
> --- a/arch/arm/boot/dts/imx6qdl.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl.dtsi
> @@ -622,7 +622,7 @@
> };
>
> src: src@020d8000 {
> - compatible = "fsl,imx6q-src", "fsl,imx51-src";
> + compatible = "fsl,imx6q-src", "fsl,imx51-src", "fsl,src";
> reg = <0x020d8000 0x4000>;
> interrupts = <0 91 IRQ_TYPE_LEVEL_HIGH>,
> <0 96 IRQ_TYPE_LEVEL_HIGH>;
> @@ -630,7 +630,7 @@
> };
>
> gpc: gpc@020dc000 {
> - compatible = "fsl,imx6q-gpc";
> + compatible = "fsl,imx6q-gpc", "fsl,gpc";
> reg = <0x020dc000 0x4000>;
> interrupts = <0 89 IRQ_TYPE_LEVEL_HIGH>,
> <0 90 IRQ_TYPE_LEVEL_HIGH>;
> @@ -840,7 +840,7 @@
> };
>
> mmdc0: mmdc@021b0000 { /* MMDC0 */
> - compatible = "fsl,imx6q-mmdc";
> + compatible = "fsl,imx6q-mmdc", "fsl,mmdc";
This is not nice. Here you introduce a fsl,mmdc compatible claiming all
mmdc are compatible to each other and in the driver code you have:
static const u32 imx6q_mmdc_io_dsm_offset[]
static const u32 imx6dl_mmdc_io_dsm_offset[]
which proves they are *not* compatible.
You do this just to share a
imx6_pm_get_base(&pm_info->mmdc_base, "fsl,mmdc");
across the different i.MX6 SoCs.
You can sanitize this by introducing a SoC struct which you populate
differently for the SoCs
static pm_soc_data imx6q_data {
.mmdc_compat = "fsl,imx6q-mmdc",
};
And by putting cpu_type, mmdc_io_num and others in this struct you can
also remove the if(cpu_is_x()) else if (cpu_is_y()) else...
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-13 12:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 11:53 [PATCH V4 1/6] ARM: dts: imx6q: add common compatible name for reused modules Anson Huang
[not found] ` <1389614031-7253-1-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-01-13 11:53 ` [PATCH V4 2/6] ARM: imx: add suspend in ocram support on i.mx6q Anson Huang
[not found] ` <1389614031-7253-2-git-send-email-b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-01-13 12:44 ` Russell King - ARM Linux
[not found] ` <20140113124445.GV15937-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-01-13 14:19 ` Shawn Guo
2014-01-13 11:53 ` [PATCH V4 3/6] ARM: dts: imx6dl: add common compatible name for reused modules Anson Huang
2014-01-13 11:53 ` [PATCH V4 4/6] ARM: imx: add suspend in ocram support on i.mx6dl Anson Huang
2014-01-13 11:53 ` [PATCH V4 5/6] ARM: dts: imx6sl: add common compatible name for reused modules Anson Huang
2014-01-13 11:53 ` [PATCH V4 6/6] ARM: imx: add suspend in ocram support on i.mx6sl Anson Huang
2014-01-13 12:10 ` Sascha Hauer [this message]
[not found] ` <20140113121016.GJ16215-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-01-13 14:22 ` [PATCH V4 1/6] ARM: dts: imx6q: add common compatible name for reused modules Shawn Guo
[not found] ` <20140113142249.GW23525-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2014-01-13 15:16 ` Sascha Hauer
[not found] ` <20140113151623.GL16215-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-01-14 2:26 ` Shawn Guo
[not found] ` <20140114022609.GA1896-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2014-01-14 9:16 ` Sascha Hauer
2014-01-14 2:37 ` Shawn Guo
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=20140113121016.GJ16215@pengutronix.de \
--to=s.hauer-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=b20788-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).