From: joshc@codeaurora.org (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: qcom: Update msm8960 device trees
Date: Wed, 28 May 2014 15:09:49 -0500 [thread overview]
Message-ID: <20140528200948.GI2012@joshc.qualcomm.com> (raw)
In-Reply-To: <1401301643-20191-1-git-send-email-galak@codeaurora.org>
On Wed, May 28, 2014 at 01:27:23PM -0500, Kumar Gala wrote:
> * Move SoC peripherals into an SoC container node
> * Move serial enabling into board file (qcom-msm8960-cdp.dts)
> * Cleanup cpu node to match binding spec, enable-method and compatible
> should be per cpu, not part of the container
> * Drop interrupts property from l2-cache node as its not part of the
> binding spec
>
> Signed-off-by: Kumar Gala <galak@codeaurora.org>
> ---
> arch/arm/boot/dts/qcom-msm8960-cdp.dts | 6 ++
> arch/arm/boot/dts/qcom-msm8960.dtsi | 165 +++++++++++++++++----------------
> 2 files changed, 93 insertions(+), 78 deletions(-)
>
> diff --git a/arch/arm/boot/dts/qcom-msm8960-cdp.dts b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> index a58fb88..8e77ed7 100644
> --- a/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> +++ b/arch/arm/boot/dts/qcom-msm8960-cdp.dts
> @@ -3,4 +3,10 @@
> / {
> model = "Qualcomm MSM8960 CDP";
> compatible = "qcom,msm8960-cdp", "qcom,msm8960";
> +
> + soc {
> + serial at 16440000 {
> + status = "ok";
> + };
> + };
> };
Is now the time put these serial nodes under a GSBI parent node?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-05-28 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 18:27 [PATCH] ARM: dts: qcom: Update msm8960 device trees Kumar Gala
2014-05-28 20:09 ` Josh Cartwright [this message]
2014-05-28 20:18 ` Kumar Gala
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=20140528200948.GI2012@joshc.qualcomm.com \
--to=joshc@codeaurora.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;
as well as URLs for NNTP newsgroup(s).