From: David Brown <davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: Rohit Vaswani <rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Ian Campbell
<ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Daniel Walker <dwalker-zu3NM2574RrQT0dZR+AlfA@public.gmane.org>,
Bryan Huntsman <bryanh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard
Date: Thu, 26 Sep 2013 13:58:08 -0700 [thread overview]
Message-ID: <20130926205808.GA3146@codeaurora.org> (raw)
In-Reply-To: <50877C70-6066-4E87-9DEA-9F29D098525B-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Thu, Sep 26, 2013 at 02:33:53PM -0500, Kumar Gala wrote:
>> "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 ?
>
>Not 100% sure what people will decide on this. There are a number of
>examples on the PPC side (arch/powerpc/boot/dts) that are soc@ADDR,
>but they don't typically have "reg" properties at the soc level.
>
>Let's go ahead w/o the unit address (as you have it) for now.
What is the address even supposed to mean? Are we expecting multiple
'soc' nodes?
David
--
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
WARNING: multiple messages have this Message-ID (diff)
From: David Brown <davidb@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Rohit Vaswani <rvaswani@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 13:58:08 -0700 [thread overview]
Message-ID: <20130926205808.GA3146@codeaurora.org> (raw)
In-Reply-To: <50877C70-6066-4E87-9DEA-9F29D098525B@codeaurora.org>
On Thu, Sep 26, 2013 at 02:33:53PM -0500, Kumar Gala wrote:
>> "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 ?
>
>Not 100% sure what people will decide on this. There are a number of
>examples on the PPC side (arch/powerpc/boot/dts) that are soc@ADDR,
>but they don't typically have "reg" properties at the soc level.
>
>Let's go ahead w/o the unit address (as you have it) for now.
What is the address even supposed to mean? Are we expecting multiple
'soc' nodes?
David
WARNING: multiple messages have this Message-ID (diff)
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 2/3] ARM: msm: Add support for APQ8074 Dragonboard
Date: Thu, 26 Sep 2013 13:58:08 -0700 [thread overview]
Message-ID: <20130926205808.GA3146@codeaurora.org> (raw)
In-Reply-To: <50877C70-6066-4E87-9DEA-9F29D098525B@codeaurora.org>
On Thu, Sep 26, 2013 at 02:33:53PM -0500, Kumar Gala wrote:
>> "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 ?
>
>Not 100% sure what people will decide on this. There are a number of
>examples on the PPC side (arch/powerpc/boot/dts) that are soc at ADDR,
>but they don't typically have "reg" properties at the soc level.
>
>Let's go ahead w/o the unit address (as you have it) for now.
What is the address even supposed to mean? Are we expecting multiple
'soc' nodes?
David
next prev parent reply other threads:[~2013-09-26 20:58 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
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 [this message]
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=20130926205808.GA3146@codeaurora.org \
--to=davidb-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=bryanh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dwalker-zu3NM2574RrQT0dZR+AlfA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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 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.