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 12:17:38 -0700 [thread overview]
Message-ID: <52448852.9050608@codeaurora.org> (raw)
In-Reply-To: <52447779.3010908@codeaurora.org>
On 9/26/2013 11:05 AM, Rohit Vaswani wrote:
> 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.
I see the mail from Stephen Warren for adding a check stating that
"ePAPR 1.1 section 2.2.1.1 "Node Name Requirements" specifies that any
node that has a reg property must include a unit address in its name
with value matching the first entry in its reg property. Conversely, if
a node does not have a reg property, the node name must not include a
unit address."
The soc node we have does not have a reg property ?
>
>>
>>>>> +};
>>>>> +
>>>>> +&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
>
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 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 3:13 No subject Rohit Vaswani
2013-09-24 3:13 ` [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard Rohit Vaswani
2013-09-25 19:49 ` Kumar Gala
2013-09-25 22:35 ` Rohit Vaswani
2013-09-26 16:37 ` Kumar Gala
2013-09-26 18:05 ` Rohit Vaswani
2013-09-26 19:17 ` Rohit Vaswani [this message]
2013-09-26 19:33 ` Kumar Gala
2013-09-26 20:58 ` David Brown
2013-09-26 21:06 ` Kumar Gala
2013-09-26 21:10 ` Rob Herring
2013-09-26 21:23 ` Kumar Gala
2013-09-24 3:13 ` [PATCH 3/3] defconfig: msm_defconfig: Enable CONFIG_ARCH_MSM8974 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=52448852.9050608@codeaurora.org \
--to=rvaswani@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).