From: Rohit Vaswani <rvaswani@codeaurora.org> To: Kumar Gala <galak@codeaurora.org> Cc: David Brown <davidb@codeaurora.org>, Rob Herring <rob.herring@calxeda.com>, Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>, Stephen Warren <swarren@wwwdotorg.org>, Ian Campbell <ian.campbell@citrix.com>, Russell King <linux@arm.linux.org.uk>, Daniel Walker <dwalker@fifo99.com>, Bryan Huntsman <bryanh@codeaurora.org>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org Subject: Re: [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard Date: Thu, 26 Sep 2013 11:05:45 -0700 [thread overview] Message-ID: <52447779.3010908@codeaurora.org> (raw) In-Reply-To: <B0F416B8-042A-49F1-81E9-B217F02AAD1E@codeaurora.org> On 9/26/2013 9:37 AM, Kumar Gala wrote: > <snip> > +++ b/arch/arm/boot/dts/qcom-apq8074-dragonboard.dts > @@ -0,0 +1,6 @@ > +/include/ "qcom-msm8974.dtsi" > + > +/ { > + model = "Qualcomm APQ8074 Dragonboard"; > + compatible = "qcom,apq8074-dragonboard", "qcom,apq8074"; > +}; > diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi b/arch/arm/boot/dts/qcom-msm8974.dtsi > new file mode 100644 > index 0000000..f04b643 > --- /dev/null > +++ b/arch/arm/boot/dts/qcom-msm8974.dtsi > @@ -0,0 +1,35 @@ > +/dts-v1/; > + > +/include/ "skeleton.dtsi" > + > +/ { > + model = "Qualcomm MSM8974"; > + compatible = "qcom,msm8974"; > + interrupt-parent = <&intc>; > + > + soc: soc { }; >>> We should have a unit address here: >>> >>> soc: soc@FOOBAR { >>> >>> also, split out the curly braces so any future patches do have to muck with that. >>> >>> }; >>> >> Im not sure I understand the reasoning behind the unit address for soc ? > Its fairly standard practice and there is a fair amount of discussion about the lack of a unit address for memory nodes. > That still doesn't really answer anything :) - and I couldn't find any discussions about this either. I don't see anybody in upstream adding an address to soc except sun. What is that address supposed to be for - what does it mean ? The soc is way of encapsulating meaningful blocks for the particular SoC. > >>>> +}; >>>> + >>>> +&soc { >>>> + #address-cells = <1>; >>>> + #size-cells = <1>; >>>> + ranges; >>>> + compatible = "simple-bus"; >>>> + >>>> + intc: interrupt-controller@f9000000 { >>>> + compatible = "qcom,msm-qgic2"; >>>> + interrupt-controller; >>>> + #interrupt-cells = <3>; >>>> + reg = <0xf9000000 0x1000>, >>>> + <0xf9002000 0x1000>; >>>> + }; >>>> + >>>> + timer { >>>> + compatible = "arm,armv7-timer"; >>>> + interrupts = <1 2 0xf08>, >>>> + <1 3 0xf08>, >>>> + <1 4 0xf08>, >>>> + <1 1 0xf08>; >>>> + clock-frequency = <19200000>; >>>> + }; >>>> +}; > - k > Thanks, Rohit Vaswani -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: rvaswani@codeaurora.org (Rohit Vaswani) To: linux-arm-kernel@lists.infradead.org Subject: [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard Date: Thu, 26 Sep 2013 11:05:45 -0700 [thread overview] Message-ID: <52447779.3010908@codeaurora.org> (raw) In-Reply-To: <B0F416B8-042A-49F1-81E9-B217F02AAD1E@codeaurora.org> On 9/26/2013 9:37 AM, Kumar Gala wrote: > <snip> > +++ b/arch/arm/boot/dts/qcom-apq8074-dragonboard.dts > @@ -0,0 +1,6 @@ > +/include/ "qcom-msm8974.dtsi" > + > +/ { > + model = "Qualcomm APQ8074 Dragonboard"; > + compatible = "qcom,apq8074-dragonboard", "qcom,apq8074"; > +}; > diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi b/arch/arm/boot/dts/qcom-msm8974.dtsi > new file mode 100644 > index 0000000..f04b643 > --- /dev/null > +++ b/arch/arm/boot/dts/qcom-msm8974.dtsi > @@ -0,0 +1,35 @@ > +/dts-v1/; > + > +/include/ "skeleton.dtsi" > + > +/ { > + model = "Qualcomm MSM8974"; > + compatible = "qcom,msm8974"; > + interrupt-parent = <&intc>; > + > + soc: soc { }; >>> We should have a unit address here: >>> >>> soc: soc at FOOBAR { >>> >>> also, split out the curly braces so any future patches do have to muck with that. >>> >>> }; >>> >> Im not sure I understand the reasoning behind the unit address for soc ? > Its fairly standard practice and there is a fair amount of discussion about the lack of a unit address for memory nodes. > That still doesn't really answer anything :) - and I couldn't find any discussions about this either. I don't see anybody in upstream adding an address to soc except sun. What is that address supposed to be for - what does it mean ? The soc is way of encapsulating meaningful blocks for the particular SoC. > >>>> +}; >>>> + >>>> +&soc { >>>> + #address-cells = <1>; >>>> + #size-cells = <1>; >>>> + ranges; >>>> + compatible = "simple-bus"; >>>> + >>>> + intc: interrupt-controller at f9000000 { >>>> + compatible = "qcom,msm-qgic2"; >>>> + interrupt-controller; >>>> + #interrupt-cells = <3>; >>>> + reg = <0xf9000000 0x1000>, >>>> + <0xf9002000 0x1000>; >>>> + }; >>>> + >>>> + timer { >>>> + compatible = "arm,armv7-timer"; >>>> + interrupts = <1 2 0xf08>, >>>> + <1 3 0xf08>, >>>> + <1 4 0xf08>, >>>> + <1 1 0xf08>; >>>> + clock-frequency = <19200000>; >>>> + }; >>>> +}; > - k > Thanks, Rohit Vaswani -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2013-09-26 18:05 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-24 3:13 (unknown), Rohit Vaswani 2013-09-24 3:13 ` No subject Rohit Vaswani 2013-09-24 3:13 ` Rohit Vaswani [not found] ` <1379992406-3541-1-git-send-email-rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-24 3:13 ` [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard Rohit Vaswani 2013-09-24 3:13 ` Rohit Vaswani 2013-09-24 3:13 ` Rohit Vaswani 2013-09-25 19:49 ` Kumar Gala 2013-09-25 19:49 ` Kumar Gala [not found] ` <4E7868D6-56CB-4AF8-8EBF-069966899C23-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-25 22:35 ` Rohit Vaswani 2013-09-25 22:35 ` Rohit Vaswani 2013-09-25 22:35 ` Rohit Vaswani [not found] ` <5243652F.7090408-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-26 16:37 ` Kumar Gala 2013-09-26 16:37 ` Kumar Gala 2013-09-26 16:37 ` Kumar Gala 2013-09-26 18:05 ` Rohit Vaswani [this message] 2013-09-26 18:05 ` Rohit Vaswani [not found] ` <52447779.3010908-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-26 19:17 ` Rohit Vaswani 2013-09-26 19:17 ` Rohit Vaswani 2013-09-26 19:17 ` Rohit Vaswani [not found] ` <52448852.9050608-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-26 19:33 ` Kumar Gala 2013-09-26 19:33 ` Kumar Gala 2013-09-26 19:33 ` Kumar Gala [not found] ` <50877C70-6066-4E87-9DEA-9F29D098525B-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-26 20:58 ` David Brown 2013-09-26 20:58 ` David Brown 2013-09-26 20:58 ` David Brown [not found] ` <20130926205808.GA3146-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2013-09-26 21:06 ` Kumar Gala 2013-09-26 21:06 ` Kumar Gala 2013-09-26 21:06 ` Kumar Gala 2013-09-26 21:10 ` Rob Herring 2013-09-26 21:10 ` Rob Herring 2013-09-26 21:10 ` Rob Herring [not found] ` <5244A2AA.6050901-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2013-09-26 21:23 ` Kumar Gala 2013-09-26 21:23 ` Kumar Gala 2013-09-26 21:23 ` Kumar Gala 2013-09-24 3:13 ` [PATCH 3/3] defconfig: msm_defconfig: Enable CONFIG_ARCH_MSM8974 Rohit Vaswani 2013-09-24 3:13 ` Rohit Vaswani
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=52447779.3010908@codeaurora.org \ --to=rvaswani@codeaurora.org \ --cc=bryanh@codeaurora.org \ --cc=davidb@codeaurora.org \ --cc=devicetree@vger.kernel.org \ --cc=dwalker@fifo99.com \ --cc=galak@codeaurora.org \ --cc=ian.campbell@citrix.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=mark.rutland@arm.com \ --cc=pawel.moll@arm.com \ --cc=rob.herring@calxeda.com \ --cc=swarren@wwwdotorg.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: linkBe 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.