From: Stephen Boyd <sboyd@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Andy Gross <agross@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@sonymobile.com>,
linux-soc@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [Patch v2 1/6] soc: qcom: gsbi: Add support for ADM CRCI muxing
Date: Mon, 02 Feb 2015 18:05:04 -0800 [thread overview]
Message-ID: <54D02CD0.4090806@codeaurora.org> (raw)
In-Reply-To: <C168E827-6052-4A7B-80EA-6330E8E08D51@codeaurora.org>
On 01/30/15 13:48, Kumar Gala wrote:
> On Jan 30, 2015, at 3:37 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
>> On 01/30/15 08:32, Kumar Gala wrote:
>>> On Jan 30, 2015, at 12:25 AM, Andy Gross <agross@codeaurora.org> wrote:
>>>
>>>> Required properties if child node exists:
>>>> - #address-cells: Must be 1
>>>> - #size-cells: Must be 1
>>>> - ranges: Must be present
>>>>
>>>> +Note: Each GSBI should have an alias correctly numbered in "aliases" node.
>>>> +
>>>> Properties for children:
>>>>
>>>> A GSBI controller node can contain 0 or more child nodes representing serial
>>>> @@ -37,6 +41,10 @@ Example for APQ8064:
>>>>
>>>> #include <dt-bindings/soc/qcom,gsbi.h>
>>>>
>>>> + aliases {
>>>> + gsbi4 = <&gsbi4>;
>>>> + };
>>> You appear to be using the alias name to determine a index number for the gsbi, if that is the case, than you should probably just add a cell-index node to the gsbi’s for this purpose.
>>>
>> I thought cell-index was "deprecated" and referred more to things like
>> enumerating all the devices on a bus by assigning them a unique ID.
>> Aliases, on the other hand, allow us to enumerate a subset of devices
>> that share the same bus with other devices of different types. For
>> example, how would I know that a device is gsbi1 vs serial1 if they both
>> used cell-index and they both had the same parent node?
> I think the problem was cell-index was never well understood and abused. For the example you are giving you wouldn’t use cell-index because you are talking about things that would have different compatibles. For what it appears we really are enumerating the GSBI hardware to match some programming interface convention. If that is the case than I think cell-index is proper.
Can you please explain when cell-index should be used and when aliases
should be used? I'm confused because I recall this message from Rob
Herring[1] where it's indicated that cell-index is pretty much
deprecated. I'm also interested to find out what cell means in
cell-index. Does it have any relation to *-cells properties?
[1] https://lkml.org/lkml/2012/11/10/102
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-02-03 2:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 6:25 [Patch v2 0/6] GSBI CRCI Autoconfiguration Support Andy Gross
2015-01-30 6:25 ` [Patch v2 1/6] soc: qcom: gsbi: Add support for ADM CRCI muxing Andy Gross
2015-01-30 16:32 ` Kumar Gala
[not found] ` <B36DEAB1-2D89-4B6B-991E-C2EDBEB684D9-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-01-30 21:37 ` Stephen Boyd
2015-01-30 21:48 ` Kumar Gala
2015-02-03 2:05 ` Stephen Boyd [this message]
2015-01-30 6:25 ` [Patch v2 2/6] mfd: qcom,tcsr: Add device tree binding for TCSR Andy Gross
2015-01-30 6:25 ` [Patch v2 3/6] ARM: DT: apq8064: Add TCSR support Andy Gross
2015-01-30 6:25 ` [Patch v2 4/6] ARM: DT: ipq8064: " Andy Gross
2015-01-30 6:25 ` [Patch v2 5/6] ARM: DT: msm8660: " Andy Gross
2015-01-30 6:25 ` [Patch v2 6/6] ARM: DT: msm8960: " Andy Gross
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=54D02CD0.4090806@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@kernel.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).