diff for duplicates of <54D02CD0.4090806@codeaurora.org> diff --git a/a/1.txt b/N1/1.txt index 18a80ac..467d7dd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -21,7 +21,7 @@ On 01/30/15 13:48, Kumar Gala wrote: >>>> + 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. +>>> 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. @@ -29,7 +29,7 @@ On 01/30/15 13:48, Kumar Gala wrote: >> 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. +> 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 diff --git a/a/content_digest b/N1/content_digest index 81e2f06..04f8ed6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,18 +3,10 @@ "ref\0B36DEAB1-2D89-4B6B-991E-C2EDBEB684D9@codeaurora.org\0" "ref\054CBF9AE.6060902@codeaurora.org\0" "ref\0C168E827-6052-4A7B-80EA-6330E8E08D51@codeaurora.org\0" - "From\0Stephen Boyd <sboyd@codeaurora.org>\0" - "Subject\0Re: [Patch v2 1/6] soc: qcom: gsbi: Add support for ADM CRCI muxing\0" + "From\0sboyd@codeaurora.org (Stephen Boyd)\0" + "Subject\0[Patch v2 1/6] soc: qcom: gsbi: Add support for ADM CRCI muxing\0" "Date\0Mon, 02 Feb 2015 18:05:04 -0800\0" - "To\0Kumar Gala <galak@codeaurora.org>\0" - "Cc\0Andy 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>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 01/30/15 13:48, Kumar Gala wrote:\n" @@ -40,7 +32,7 @@ ">>>> +\taliases {\n" ">>>> +\t\tgsbi4 = <&gsbi4>;\n" ">>>> +\t};\n" - ">>> 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\342\200\231s for this purpose.\n" + ">>> 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.\n" ">>>\n" ">> I thought cell-index was \"deprecated\" and referred more to things like\n" ">> enumerating all the devices on a bus by assigning them a unique ID.\n" @@ -48,7 +40,7 @@ ">> that share the same bus with other devices of different types. For\n" ">> example, how would I know that a device is gsbi1 vs serial1 if they both\n" ">> used cell-index and they both had the same parent node?\n" - "> I think the problem was cell-index was never well understood and abused. For the example you are giving you wouldn\342\200\231t 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.\n" + "> 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.\n" "\n" "Can you please explain when cell-index should be used and when aliases\n" "should be used? I'm confused because I recall this message from Rob\n" @@ -62,4 +54,4 @@ "Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,\n" a Linux Foundation Collaborative Project -d5aba67e69612895ddbc0b2a00326e301b5fb97489e73c5ffab432c0e39a63bb +e7884ffd08a63761918ad90a4de41ea2019a3a2a803786139dabb2a4dcb71d51
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.