diff for duplicates of <4DE6AFF7.3040905@firmworks.com> diff --git a/a/1.txt b/N1/1.txt index 48af1c0..738b4d8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -15,7 +15,7 @@ On 6/1/2011 5:59 AM, Stephen Warren wrote: >>>> gpio-controller1: gpio-controller { >>>> #address-cells =<2>; >>>> #mode-cells =<2>; ->>>> gpio1: gpio@12,0 { +>>>> gpio1: gpio at 12,0 { >>>> reg =<12 0>; >>>> mode =<55 66>; >>>> usage = "Audio Codec chip select"; /* Optional */ @@ -24,7 +24,7 @@ On 6/1/2011 5:59 AM, Stephen Warren wrote: >>>> gpio-controller2: gpio-controller { >>>> #address-cells =<1>; >>>> #mode-cells =<1>; ->>>> gpio2: gpio@4 { +>>>> gpio2: gpio at 4 { >>>> reg =<4>; >>>> #mode-cells =<1>; >>>> } @@ -104,7 +104,7 @@ On 6/1/2011 5:59 AM, Stephen Warren wrote: > #mode-cells in every gpio definition that's inside/underneath the > controller definition; in my mind, "passing on" the requirement to > define the mode would be the default state, so forcing the namer of -> GPIOs (i.e. whoever writes the "gpio1: gpio@12,0 {" definitions) to +> GPIOs (i.e. whoever writes the "gpio1: gpio at 12,0 {" definitions) to > do this seems almost like busy work. Is there a way in *.dts to mark > the #mode-cells field as inherited by children unless overridden? @@ -122,12 +122,12 @@ The example: /* No reg property */ /* No mode property */ } - fully_bound_gpio1: audio-chipsel@12,0 { + fully_bound_gpio1: audio-chipsel at 12,0 { reg = <12 0>; mode = <55 66>; usage = "Audio Codec chip select"; /* Optional */ } - address_bound_gpio1: gpio@13,0 { + address_bound_gpio1: gpio at 13,0 { reg = <13 0>; /* No mode property */ } @@ -143,7 +143,7 @@ The example: /* No reg property */ /* No mode property */ } - address_bound_gpio2: gpio@4 { + address_bound_gpio2: gpio at 4 { reg = <4>; /* No mode property */ } @@ -178,7 +178,7 @@ e) gpios that are mode-bound but not address-bound must have distinct names from each other and from the unbound node name ("gpio"), because of the device tree rule that the combination of name+address must be unique among the children of a given node. It is okay to have both -"gpio" and "gpio@12", but you cannot have two nodes both named just "gpio". +"gpio" and "gpio at 12", but you cannot have two nodes both named just "gpio". f) SoC device tree blobs would probably use only the unbound form. A given platform might choose to specialize the tree by adding additional diff --git a/a/content_digest b/N1/content_digest index 5380b11..da54433 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -12,18 +12,10 @@ "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C22D@HQMAIL01.nvidia.com\0" "ref\04DE536AD.5080200@firmworks.com\0" "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C3F5@HQMAIL01.nvidia.com\0" - "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C3F5-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org\0" - "From\0Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>\0" - "Subject\0Re: [RFC 2/2] ARM:Tegra: Device Tree Support: Initialize audio card gpio's from the device tree.\0" + "From\0wmb@firmworks.com (Mitch Bradley)\0" + "Subject\0[RFC 2/2] ARM:Tegra: Device Tree Support: Initialize audio card gpio's from the device tree.\0" "Date\0Wed, 01 Jun 2011 11:32:39 -1000\0" - "To\0Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>\0" - "Cc\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>" - Segher Boessenkool <segher-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org> - Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org> - devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org> - linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> - Olof Johansson <olofj-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> - " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 6/1/2011 5:59 AM, Stephen Warren wrote:\n" @@ -43,7 +35,7 @@ ">>>> gpio-controller1: gpio-controller {\n" ">>>> #address-cells =<2>;\n" ">>>> #mode-cells =<2>;\n" - ">>>> gpio1: gpio@12,0 {\n" + ">>>> gpio1: gpio at 12,0 {\n" ">>>> reg =<12 0>;\n" ">>>> mode =<55 66>;\n" ">>>> usage = \"Audio Codec chip select\"; /* Optional */\n" @@ -52,7 +44,7 @@ ">>>> gpio-controller2: gpio-controller {\n" ">>>> #address-cells =<1>;\n" ">>>> #mode-cells =<1>;\n" - ">>>> gpio2: gpio@4 {\n" + ">>>> gpio2: gpio at 4 {\n" ">>>> reg =<4>;\n" ">>>> #mode-cells =<1>;\n" ">>>> }\n" @@ -132,7 +124,7 @@ "> #mode-cells in every gpio definition that's inside/underneath the\n" "> controller definition; in my mind, \"passing on\" the requirement to\n" "> define the mode would be the default state, so forcing the namer of\n" - "> GPIOs (i.e. whoever writes the \"gpio1: gpio@12,0 {\" definitions) to\n" + "> GPIOs (i.e. whoever writes the \"gpio1: gpio at 12,0 {\" definitions) to\n" "> do this seems almost like busy work. Is there a way in *.dts to mark\n" "> the #mode-cells field as inherited by children unless overridden?\n" "\n" @@ -150,12 +142,12 @@ " /* No reg property */\n" " /* No mode property */\n" " }\n" - " fully_bound_gpio1: audio-chipsel@12,0 {\n" + " fully_bound_gpio1: audio-chipsel at 12,0 {\n" " reg = <12 0>;\n" " mode = <55 66>;\n" " usage = \"Audio Codec chip select\"; /* Optional */\n" " }\n" - " address_bound_gpio1: gpio@13,0 {\n" + " address_bound_gpio1: gpio at 13,0 {\n" " reg = <13 0>;\n" " /* No mode property */\n" " }\n" @@ -171,7 +163,7 @@ " /* No reg property */\n" " /* No mode property */\n" " }\n" - " address_bound_gpio2: gpio@4 {\n" + " address_bound_gpio2: gpio at 4 {\n" " reg = <4>;\n" " /* No mode property */\n" " }\n" @@ -206,7 +198,7 @@ "names from each other and from the unbound node name (\"gpio\"), because \n" "of the device tree rule that the combination of name+address must be \n" "unique among the children of a given node. It is okay to have both \n" - "\"gpio\" and \"gpio@12\", but you cannot have two nodes both named just \"gpio\".\n" + "\"gpio\" and \"gpio at 12\", but you cannot have two nodes both named just \"gpio\".\n" "\n" "f) SoC device tree blobs would probably use only the unbound form. A \n" "given platform might choose to specialize the tree by adding additional \n" @@ -304,4 +296,4 @@ ">\n" > -9d3d3127bf2b24f89fcbb1c843bdd063734cc3033d45128dee923e25b147ddb8 +964d380ff28f0c97134c9ccc94472d98a198b73d987d9a8f2535ead0b0bf6ac8
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.