diff for duplicates of <4FE39EA2.8050809@wwwdotorg.org> diff --git a/a/1.txt b/N1/1.txt index ac7334b..e912f12 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -16,7 +16,7 @@ On 06/20/2012 07:32 PM, Chen Peter-B29397 wrote: > Hi Stephen, > For your suggestion: > -> sdhci at 78000000 { +> sdhci@78000000 { > compatible = "nvidia,tegra30-sdhci", "nvidia,tegra20-sdhci"; > reg = <0x78000000 0x200>; > interrupts = <0 14 0x04>; @@ -49,7 +49,7 @@ ehci { */ hub { hub { /* also dynamic */ - port at 2 { + port@2 { child-supply = <®ulator>; reset-gpios = <&gpio 0 0>; }; @@ -57,11 +57,11 @@ ehci { }; }; -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. diff --git a/a/content_digest b/N1/content_digest index e56a0f5..e2bea47 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -7,10 +7,25 @@ "ref\04FE1DE53.4070202@gmail.com\0" "ref\04FE1EF26.9080401@wwwdotorg.org\0" "ref\0F281D0F91ED19E4D8E63A7504E8A649803BE3E73@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\0F281D0F91ED19E4D8E63A7504E8A649803BE3E73-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\0Thu, 21 Jun 2012 16:22:26 -0600\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Chen Peter-B29397 <B29397-KZfg59tc24xl57MIdRCFDg@public.gmane.org>\0" + "Cc\0marex-ynQEQJNshbs@public.gmane.org <marex-ynQEQJNshbs@public.gmane.org>" + Li Frank-B20596 <B20596-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + Zhao Richard-B20223 <B20223-KZfg59tc24xl57MIdRCFDg@public.gmane.org> + alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org <alexander.shishkin-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> + Estevam Fabio-R49496 <r49496-KZfg59tc24xl57MIdRCFDg@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> + kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> + gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org> + stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@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/20/2012 07:32 PM, Chen Peter-B29397 wrote:\n" @@ -31,7 +46,7 @@ "> Hi Stephen,\n" "> For your suggestion: \n" "> \n" - "> sdhci at 78000000 {\n" + "> sdhci@78000000 {\n" "> \tcompatible = \"nvidia,tegra30-sdhci\", \"nvidia,tegra20-sdhci\";\n" "> \treg = <0x78000000 0x200>;\n" "> \tinterrupts = <0 14 0x04>;\n" @@ -64,7 +79,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" @@ -72,13 +87,13 @@ " };\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. -dd12fe677ee109239745ebbbfd3005b07da5f0a1306da7608ee5739c355eea3a +76488cff5af7d7cc23244d67db5def1957aec162a7023bc86f1aecb26f56c33b
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.