diff for duplicates of <20160122065901.GA31145@shlinux2> diff --git a/a/1.txt b/N1/1.txt index 6807c73..e079547 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -56,12 +56,12 @@ On Thu, Jan 21, 2016 at 11:24:21PM +0100, Arnd Bergmann wrote: > In this case, the DT representation would be > > -> usb at ... { /* host controller and root hub */ +> usb@... { /* host controller and root hub */ > compatible = "xhci-generic"; > #address-cells = <1>; > #size-cells = <0>; > -> hub at 1 { /* external hub, superspeed mode class 9/subclass 0/proto 3 */ +> hub@1 { /* external hub, superspeed mode class 9/subclass 0/proto 3 */ > compatible = "usb2109,0812.591", > "usb2109,0812", > "usb2109,class9.0.3", @@ -75,7 +75,7 @@ Do we really need to write "compatible" so complicated? > #size-cells = <0>; > reg = <1>; > -> communications at 4 { /* superspeed ethernet device */ +> communications@4 { /* superspeed ethernet device */ > compatible = "usb0b95,1790.100", > "usb0b95,1790", > "usb0b95,class255.255.0", @@ -89,7 +89,7 @@ Do we really need to write "compatible" so complicated? > reg = <4>; > }; > -> storage at 1 { /* superspeed flash drive */ +> storage@1 { /* superspeed flash drive */ > compatible = "usb1234,5678.600", > "usb1234,5678", > "usbif1234,class8.6.80", @@ -102,7 +102,7 @@ Do we really need to write "compatible" so complicated? > }; > }; > -> hub at 3 { /* same external hub, highspeed mode */ +> hub@3 { /* same external hub, highspeed mode */ > compatible = "usb2109,0812.591", > "usb2109,0812", > "usb2109,class9.0.1", @@ -116,7 +116,7 @@ Do we really need to write "compatible" so complicated? Why "reg" is 3 here? -> wireless at 2 { /* bluetooth device */ +> wireless@2 { /* bluetooth device */ > compatible = "usb0a12,0001.134", > "usb0a12,0001", > "usb0a12,class224.1.1", @@ -129,7 +129,7 @@ Why "reg" is 3 here? > #size-cells = <0>; > reg = <2>; > -> wireless at 0,0 { /* bluetooth config 0, if 0 */ +> wireless@0,0 { /* bluetooth config 0, if 0 */ > compatible = "usbif0a12,0001.134.config0.0", > "usbif0a12,0001.config0.0", > "usbif0a12,class224.1.1", @@ -141,7 +141,7 @@ Why "reg" is 3 here? > reg = <0 0>; > }; > -> wireless at 0,1 { /* bluetooth config 0, if 1 */ +> wireless@0,1 { /* bluetooth config 0, if 1 */ > compatible = "usbif0a12,0001.134.config0.1", > "usbif0a12,0001.config0.1", > "usbif0a12,class224.1.1", @@ -157,8 +157,8 @@ Why "reg" is 3 here? > }; > > In that description, I have included all four kinds of nodes from -> the spec: host controller, device (wireless at 2), interface (wireless at 0.1, -> wireless at 0.2) and combined (hub at 1, hub at 3, storage at 1, communications at 4). +> the spec: host controller, device (wireless@2), interface (wireless@0.1, +> wireless@0.2) and combined (hub@1, hub@3, storage@1, communications@4). > > Peter's example only contained hubs in combined nodes, no device or > interface nodes. I wonder if the code is able to parse all four @@ -186,3 +186,7 @@ I have not seen such kinds of devices, but it is possible in theory. Best Regards, Peter Chen +-- +To unsubscribe from this list: send the line "unsubscribe linux-usb" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index a8d2b5c..38080a3 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,23 @@ "ref\0Pine.LNX.4.44L0.1601211015010.2275-100000@iolanthe.rowland.org\0" "ref\02930830.FLp5q7oBTi@wuerfel\0" - "From\0hzpeterchen@gmail.com (Peter Chen)\0" - "Subject\0[PATCH v3 1/1] USB: core: let USB device know device node\0" + "From\0Peter Chen <hzpeterchen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" + "Subject\0Re: [PATCH v3 1/1] USB: core: let USB device know device node\0" "Date\0Fri, 22 Jan 2016 14:59:01 +0800\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>\0" + "Cc\0Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>" + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org + mark.rutland-5wv7dgnIgG8@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org + pawel.moll-5wv7dgnIgG8@public.gmane.org + valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org + gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org + s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org + linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + balbi-l0cyMroinI0@public.gmane.org + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + Peter Chen <peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + " kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org\0" "\00:1\0" "b\0" "On Thu, Jan 21, 2016 at 11:24:21PM +0100, Arnd Bergmann wrote:\n" @@ -64,12 +78,12 @@ "> In this case, the DT representation would be\n" "> \n" "> \n" - "> \tusb at ... { /* host controller and root hub */\n" + "> \tusb@... { /* host controller and root hub */\n" "> \t\tcompatible = \"xhci-generic\";\n" "> \t\t#address-cells = <1>;\n" "> \t\t#size-cells = <0>;\n" "> \n" - "> \t\thub at 1 { /* external hub, superspeed mode class 9/subclass 0/proto 3 */\n" + "> \t\thub@1 { /* external hub, superspeed mode class 9/subclass 0/proto 3 */\n" "> \t\t\tcompatible = \"usb2109,0812.591\",\n" "> \t\t\t\t \"usb2109,0812\",\n" "> \t\t\t\t \"usb2109,class9.0.3\",\n" @@ -83,7 +97,7 @@ "> \t\t\t#size-cells = <0>;\n" "> \t\t\treg = <1>;\n" "> \n" - "> \t\t\tcommunications at 4 { /* superspeed ethernet device */\n" + "> \t\t\tcommunications@4 { /* superspeed ethernet device */\n" "> \t\t\t\tcompatible = \"usb0b95,1790.100\",\n" "> \t\t\t\t\t \"usb0b95,1790\",\n" "> \t\t\t\t\t \"usb0b95,class255.255.0\",\n" @@ -97,7 +111,7 @@ "> \t\t\t\treg = <4>;\n" "> \t\t\t};\n" "> \n" - "> \t\t\tstorage at 1 { /* superspeed flash drive */\n" + "> \t\t\tstorage@1 { /* superspeed flash drive */\n" "> \t\t\t\tcompatible = \"usb1234,5678.600\",\n" "> \t\t\t\t\t \"usb1234,5678\",\n" "> \t\t\t\t\t \"usbif1234,class8.6.80\",\n" @@ -110,7 +124,7 @@ "> \t\t\t};\n" "> \t\t};\n" "> \t\n" - "> \t\thub at 3 { /* same external hub, highspeed mode */\n" + "> \t\thub@3 { /* same external hub, highspeed mode */\n" "> \t\t\tcompatible = \"usb2109,0812.591\",\n" "> \t\t\t\t \"usb2109,0812\",\n" "> \t\t\t\t \"usb2109,class9.0.1\",\n" @@ -124,7 +138,7 @@ "\n" "Why \"reg\" is 3 here?\n" "\n" - "> \t\t\twireless at 2 { /* bluetooth device */\n" + "> \t\t\twireless@2 { /* bluetooth device */\n" "> \t\t\t\tcompatible = \"usb0a12,0001.134\",\n" "> \t\t\t\t\t \"usb0a12,0001\",\n" "> \t\t\t\t\t \"usb0a12,class224.1.1\",\n" @@ -137,7 +151,7 @@ "> \t\t\t\t#size-cells = <0>;\n" "> \t\t\t\treg = <2>;\n" "> \n" - "> \t\t\t\twireless at 0,0 { /* bluetooth config 0, if 0 */\n" + "> \t\t\t\twireless@0,0 { /* bluetooth config 0, if 0 */\n" "> \t\t\t\t\tcompatible = \"usbif0a12,0001.134.config0.0\",\n" "> \t\t\t\t\t\t\t\"usbif0a12,0001.config0.0\",\n" "> \t\t\t\t\t\t\t\"usbif0a12,class224.1.1\",\n" @@ -149,7 +163,7 @@ "> \t\t\t\t\treg = <0 0>;\n" "> \t\t\t\t};\n" "> \n" - "> \t\t\t\twireless at 0,1 { /* bluetooth config 0, if 1 */\n" + "> \t\t\t\twireless@0,1 { /* bluetooth config 0, if 1 */\n" "> \t\t\t\t\tcompatible = \"usbif0a12,0001.134.config0.1\",\n" "> \t\t\t\t\t\t\t\"usbif0a12,0001.config0.1\",\n" "> \t\t\t\t\t\t\t\"usbif0a12,class224.1.1\",\n" @@ -165,8 +179,8 @@ "> \t};\n" "> \n" "> In that description, I have included all four kinds of nodes from\n" - "> the spec: host controller, device (wireless at 2), interface (wireless at 0.1,\n" - "> wireless at 0.2) and combined (hub at 1, hub at 3, storage at 1, communications at 4).\n" + "> the spec: host controller, device (wireless@2), interface (wireless@0.1,\n" + "> wireless@0.2) and combined (hub@1, hub@3, storage@1, communications@4).\n" "> \n" "> Peter's example only contained hubs in combined nodes, no device or\n" "> interface nodes. I wonder if the code is able to parse all four\n" @@ -193,6 +207,10 @@ "-- \n" "\n" "Best Regards,\n" - Peter Chen + "Peter Chen\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-usb\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -8f5fb5fa77a2e85dae83bf15a4d06500c9846051f416a6b0a0187c4d040ed9a4 +a0f9243959c3bc869887c27ca35cbeacd7e9b6788c82515c3b6c0d53bff0acc9
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.