All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4DE97B87.1040109@firmworks.com>

diff --git a/a/1.txt b/N1/1.txt
index 5f4b5c9..9b0624a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,7 +6,7 @@ On 6/3/2011 11:24 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?
 >>
@@ -23,12 +23,12 @@ On 6/3/2011 11:24 AM, Stephen Warren wrote:
 >>               /* 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 */
 >>           }
@@ -44,7 +44,7 @@ On 6/3/2011 11:24 AM, Stephen Warren wrote:
 >>                /* No reg property */
 >>                /* No mode property */
 >>            }
->>            address_bound_gpio2: gpio@4 {
+>>            address_bound_gpio2: gpio at 4 {
 >>                reg =<4>;
 >>                /* No mode property */
 >>            }
diff --git a/a/content_digest b/N1/content_digest
index 3cd0c64..b221018 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -14,16 +14,10 @@
  "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C3F5@HQMAIL01.nvidia.com\0"
  "ref\04DE6AFF7.3040905@firmworks.com\0"
  "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C870@HQMAIL01.nvidia.com\0"
- "ref\074CDBE0F657A3D45AFBB94109FB122FF0498E1C870-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\0Fri, 03 Jun 2011 14:25:43 -1000\0"
- "To\0Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>\0"
- "Cc\0devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>"
-  Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@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/3/2011 11:24 AM, Stephen Warren wrote:\n"
@@ -34,7 +28,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"
@@ -51,12 +45,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"
@@ -72,7 +66,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"
@@ -157,4 +151,4 @@
  "not error-prone.  I think that's somewhat orthogonal to the semantic \n"
  issues of the device tree structure.  Both are important.
 
-c75fc991b1d8b230ed770b620055ea971d6db67e077aa613fab7cfda7e735192
+e2e65fc3df4c2bf342c05257493de77862cfb93a138ac9a3f83192806dc679c9

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.