diff for duplicates of <54E3AF5F.3020902@wwwdotorg.org> diff --git a/a/1.txt b/N1/1.txt index 17b53c4..4eb0844 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -19,19 +19,19 @@ On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote: >> pinctrl-1 = <&state_i2cmux_pta>; >> pinctrl-2 = <&state_i2cmux_idle>; >> ->> i2c@0 { +>> i2c at 0 { >> reg = <0>; >> ... ->> i2c@1 { +>> i2c at 1 { >> reg = <1>; >> ... >> ->> That would generate child busses 0 and 1. If I was to disable the i2c@0 +>> That would generate child busses 0 and 1. If I was to disable the i2c at 0 >> node, then there would still be definitions for child busses 0 and 1 in >> the DT, it's just that child bus 0 wouldn't actually exist at run-time. >> I don't see what part of DT needs to be re-written to accomodate this? > -> The way the current driver works, to disable i2c@0 you'd have to remove +> The way the current driver works, to disable i2c at 0 you'd have to remove > the pinctrl-0 state, pinctrl-names string at position 0, and the node > itself. > @@ -71,8 +71,8 @@ On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote: > board-A.dts: > > i2cmux { -> i2c@0 { status = "okay"; }; -> i2c@1 { status = "okay"; }; +> i2c at 0 { status = "okay"; }; +> i2c at 1 { status = "okay"; }; > }; > > and @@ -80,8 +80,8 @@ On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote: > board-B.dts: > > i2cmux { -> i2c@0 { status = "okay"; }; -> i2c@2 { status = "okay"; }; +> i2c at 0 { status = "okay"; }; +> i2c at 2 { status = "okay"; }; > }; OK, that all makes sense, but I don't think there's any change at all to diff --git a/a/content_digest b/N1/content_digest index 9fd8563..08fcea7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,19 +2,10 @@ "ref\01424199129-22099-2-git-send-email-sebastian.hesselbarth@gmail.com\0" "ref\054E3A8A7.8080703@wwwdotorg.org\0" "ref\054E3ADB9.1040008@gmail.com\0" - "From\0Stephen Warren <swarren@wwwdotorg.org>\0" - "Subject\0Re: [PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes\0" + "From\0swarren@wwwdotorg.org (Stephen Warren)\0" + "Subject\0[PATCH 1/8] i2c: mux-pinctrl: Rework to honor disabled child nodes\0" "Date\0Tue, 17 Feb 2015 14:15:11 -0700\0" - "To\0Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>\0" - "Cc\0Jason Cooper <jason@lakedaemon.net>" - Andrew Lunn <andrew@lunn.ch> - Gregory Clement <gregory.clement@free-electrons.com> - Gabriel Dobato <dobatog@gmail.com> - Wolfram Sang <wsa@the-dreams.de> - linux-i2c@vger.kernel.org - devicetree@vger.kernel.org - linux-arm-kernel@lists.infradead.org - " linux-kernel@vger.kernel.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 02/17/2015 02:08 PM, Sebastian Hesselbarth wrote:\n" @@ -38,19 +29,19 @@ ">> pinctrl-1 = <&state_i2cmux_pta>;\n" ">> pinctrl-2 = <&state_i2cmux_idle>;\n" ">>\n" - ">> i2c@0 {\n" + ">> i2c at 0 {\n" ">> reg = <0>;\n" ">> ...\n" - ">> i2c@1 {\n" + ">> i2c at 1 {\n" ">> reg = <1>;\n" ">> ...\n" ">>\n" - ">> That would generate child busses 0 and 1. If I was to disable the i2c@0\n" + ">> That would generate child busses 0 and 1. If I was to disable the i2c at 0\n" ">> node, then there would still be definitions for child busses 0 and 1 in\n" ">> the DT, it's just that child bus 0 wouldn't actually exist at run-time.\n" ">> I don't see what part of DT needs to be re-written to accomodate this?\n" ">\n" - "> The way the current driver works, to disable i2c@0 you'd have to remove\n" + "> The way the current driver works, to disable i2c at 0 you'd have to remove\n" "> the pinctrl-0 state, pinctrl-names string at position 0, and the node\n" "> itself.\n" ">\n" @@ -90,8 +81,8 @@ "> board-A.dts:\n" ">\n" "> i2cmux {\n" - "> i2c@0 { status = \"okay\"; };\n" - "> i2c@1 { status = \"okay\"; };\n" + "> i2c at 0 { status = \"okay\"; };\n" + "> i2c at 1 { status = \"okay\"; };\n" "> };\n" ">\n" "> and\n" @@ -99,8 +90,8 @@ "> board-B.dts:\n" ">\n" "> i2cmux {\n" - "> i2c@0 { status = \"okay\"; };\n" - "> i2c@2 { status = \"okay\"; };\n" + "> i2c at 0 { status = \"okay\"; };\n" + "> i2c at 2 { status = \"okay\"; };\n" "> };\n" "\n" "OK, that all makes sense, but I don't think there's any change at all to \n" @@ -170,4 +161,4 @@ "Yes, I have both Seaboard and Ventana still (the two Tegra boards that \n" use this driver). I haven't used them in a while; I hope they still work:-) -cf6ae7212dcec2d5428d3093e47076ed54537098df45133e5226531615086af4 +ec4c72e84ab5d190e2daad0c3bd55a6b70e8da0361596805497a31474965ca6e
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.