diff for duplicates of <4FE8871B.7060408@wwwdotorg.org> diff --git a/a/1.txt b/N1/1.txt index 759b04a..769f232 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -19,7 +19,7 @@ On 06/21/2012 06:03 PM, Chen Peter-B29397 wrote: >> */ >> hub { >> hub { /* also dynamic */ ->> port at 2 { +>> port@2 { >> child-supply = <®ulator>; >> reset-gpios = <&gpio 0 0>; >> }; @@ -27,12 +27,12 @@ On 06/21/2012 06:03 PM, Chen Peter-B29397 wrote: >> }; >> }; >> ->> But without knowing what might be connected to port at 2, how do we know +>> But without knowing what might be connected to port@2, how do we know >> how to sequence the power supply and reset GPIOs according to its >> requirements? I guess this is part of the specification of the port >> itself though, not the attached device, since anything that is allowed >> to plug in must conform to whatever sequencing the port is designed to ->> give. If the connected device is known, the port at 2 node in DT can encode +>> give. If the connected device is known, the port@2 node in DT can encode >> whatever sequencing requirements are associated with the known connected >> device. > @@ -47,4 +47,8 @@ or SDIO controller) would be the one that needs to implement this, not the class driver for the thing that could be plugged in (WiFi or 3G device). > But the generic 3G and HUB devices are special, there is only one common driver -> for each of them (drivers/usb/core/hub.c & drivers/serial/option.c) +> for each of them (drivers/usb/core/hub.c & drivers/serial/option.c) +-- +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 a53aac8..e3ec621 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,10 +9,26 @@ "ref\0F281D0F91ED19E4D8E63A7504E8A649803BE3E73@039-SN2MPN1-023.039d.mgd.msft.net\0" "ref\04FE39EA2.8050809@wwwdotorg.org\0" "ref\0F281D0F91ED19E4D8E63A7504E8A649803BE45CD@039-SN2MPN1-023.039d.mgd.msft.net\0" - "From\0swarren@wwwdotorg.org (Stephen Warren)\0" - "Subject\0[Patch v5 08/13] ARM: imx6q: add config-on-boot gpios\0" + "ref\0F281D0F91ED19E4D8E63A7504E8A649803BE45CD-RL0Hj/+nBVDtkydW1Tv2Dq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org\0" + "From\0Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>\0" + "Subject\0Re: [Patch v5 08/13] ARM: imx6q: add config-on-boot gpios\0" "Date\0Mon, 25 Jun 2012 09:43:23 -0600\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Chen Peter-B29397 <B29397-KZfg59tc24xl57MIdRCFDg@public.gmane.org>\0" + "Cc\0Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>" + Zhao Richard-B20223 <B20223-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + marex-ynQEQJNshbs@public.gmane.org <marex-ynQEQJNshbs@public.gmane.org> + Li Frank-B20596 <B20596-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + Estevam Fabio-R49496 <r49496-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org <alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> + devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org> + linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + balbi-l0cyMroinI0@public.gmane.org <balbi-l0cyMroinI0@public.gmane.org> + stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org> + kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> + gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org> + dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org <dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + " Richard Zhao <linuxzsc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0" "\00:1\0" "b\0" "On 06/21/2012 06:03 PM, Chen Peter-B29397 wrote:\n" @@ -36,7 +52,7 @@ ">> */\n" ">> hub {\n" ">> hub { /* also dynamic */\n" - ">> port at 2 {\n" + ">> port@2 {\n" ">> child-supply = <®ulator>;\n" ">> reset-gpios = <&gpio 0 0>;\n" ">> };\n" @@ -44,12 +60,12 @@ ">> };\n" ">> };\n" ">>\n" - ">> But without knowing what might be connected to port at 2, how do we know\n" + ">> But without knowing what might be connected to port@2, how do we know\n" ">> how to sequence the power supply and reset GPIOs according to its\n" ">> requirements? I guess this is part of the specification of the port\n" ">> itself though, not the attached device, since anything that is allowed\n" ">> to plug in must conform to whatever sequencing the port is designed to\n" - ">> give. If the connected device is known, the port at 2 node in DT can encode\n" + ">> give. If the connected device is known, the port@2 node in DT can encode\n" ">> whatever sequencing requirements are associated with the known connected\n" ">> device.\n" "> \n" @@ -64,6 +80,10 @@ "the class driver for the thing that could be plugged in (WiFi or 3G device).\n" "\n" "> But the generic 3G and HUB devices are special, there is only one common driver\n" - > for each of them (drivers/usb/core/hub.c & drivers/serial/option.c) + "> for each of them (drivers/usb/core/hub.c & drivers/serial/option.c) \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 -8872575d7a037688744381e1e7c032cf1271876af49d7b9425e0342dc60d50b7 +014ba91dd25f45adb55f4fc2841b64ee2b4c5539e86e62df60c9077085f4a8a8
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.