From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: add new compatible stream for i.MX6QP mmdc
Date: Wed, 2 Nov 2016 22:42:13 +0800 [thread overview]
Message-ID: <20161102144211.GD19126@dragon> (raw)
In-Reply-To: <1477430817-20381-2-git-send-email-Frank.Li@nxp.com>
On Tue, Oct 25, 2016 at 04:26:57PM -0500, Frank Li wrote:
> mmdc of i.MX6QP are little difference with i.MX6Q.
> added new compatible stream fsl,imx6qp-mmdc
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> arch/arm/boot/dts/imx6qp.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6qp.dtsi b/arch/arm/boot/dts/imx6qp.dtsi
> index 886dbf2..e0fdd0f 100644
> --- a/arch/arm/boot/dts/imx6qp.dtsi
> +++ b/arch/arm/boot/dts/imx6qp.dtsi
> @@ -85,5 +85,12 @@
> pcie: pcie at 0x01000000 {
> compatible = "fsl,imx6qp-pcie", "snps,dw-pcie";
> };
> +
> + aips-bus at 02100000 {
> + mmdc0: mmdc at 021b0000 { /* MMDC0 */
> + compatible = "fsl,imx6qp-mmdc", "fsl,imx6q-mmdc";
Sine we already know that imx6qp-mmdc has a different programming model
from imx6q-mmdc, it makes less sense to have "fsl,imx6q-mmdc" here.
Shawn
> + reg = <0x021b0000 0x4000>;
> + };
> + };
> };
> };
> --
> 2.5.2
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, lznuaa@gmail.com,
mark.rutland@arm.com
Subject: Re: [PATCH 2/2] ARM: dts: add new compatible stream for i.MX6QP mmdc
Date: Wed, 2 Nov 2016 22:42:13 +0800 [thread overview]
Message-ID: <20161102144211.GD19126@dragon> (raw)
In-Reply-To: <1477430817-20381-2-git-send-email-Frank.Li@nxp.com>
On Tue, Oct 25, 2016 at 04:26:57PM -0500, Frank Li wrote:
> mmdc of i.MX6QP are little difference with i.MX6Q.
> added new compatible stream fsl,imx6qp-mmdc
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> arch/arm/boot/dts/imx6qp.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/boot/dts/imx6qp.dtsi b/arch/arm/boot/dts/imx6qp.dtsi
> index 886dbf2..e0fdd0f 100644
> --- a/arch/arm/boot/dts/imx6qp.dtsi
> +++ b/arch/arm/boot/dts/imx6qp.dtsi
> @@ -85,5 +85,12 @@
> pcie: pcie@0x01000000 {
> compatible = "fsl,imx6qp-pcie", "snps,dw-pcie";
> };
> +
> + aips-bus@02100000 {
> + mmdc0: mmdc@021b0000 { /* MMDC0 */
> + compatible = "fsl,imx6qp-mmdc", "fsl,imx6q-mmdc";
Sine we already know that imx6qp-mmdc has a different programming model
from imx6q-mmdc, it makes less sense to have "fsl,imx6q-mmdc" here.
Shawn
> + reg = <0x021b0000 0x4000>;
> + };
> + };
> };
> };
> --
> 2.5.2
>
next prev parent reply other threads:[~2016-11-02 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 21:26 [PATCH 1/2] ARM: imx: mmdc perf function support i.MX6QP Frank Li
2016-10-25 21:26 ` Frank Li
2016-10-25 21:26 ` [PATCH 2/2] ARM: dts: add new compatible stream for i.MX6QP mmdc Frank Li
2016-10-25 21:26 ` Frank Li
2016-11-02 14:42 ` Shawn Guo [this message]
2016-11-02 14:42 ` Shawn Guo
2016-11-02 15:16 ` Zhi Li
2016-11-02 15:16 ` Zhi Li
2016-11-02 14:40 ` [PATCH 1/2] ARM: imx: mmdc perf function support i.MX6QP Shawn Guo
2016-11-02 14:40 ` Shawn Guo
2016-11-02 15:19 ` Zhi Li
2016-11-02 15:19 ` Zhi Li
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=20161102144211.GD19126@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.