All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20120119182019.GI22818@atomide.com>

diff --git a/a/1.txt b/N1/1.txt
index 88529bd..0eafbcd 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,12 +3,12 @@
 > On 19 January 2012 22:26, Tony Lindgren <tony@atomide.com> wrote:
 > > * Thomas Abraham <thomas.abraham@linaro.org> [120119 04:37]:
 > >>
-> >> i2c0: i2c at 18000000 {
-> >> ? ? ? ? [... other properties ...]
-> >> ? ? ? ? pinctrl-active = <&pctrl0 5 0 2 3 0>,
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<&pctrl0 5 1 2 3 0>;
-> >> ? ? ? ? pinctrl-suspend = <&pctrl0 5 0 2 0 0>,
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? <&pctrl0 5 1 2 0 0>;
+> >> i2c0: i2c@18000000 {
+> >>         [... other properties ...]
+> >>         pinctrl-active = <&pctrl0 5 0 2 3 0>,
+> >>                              <&pctrl0 5 1 2 3 0>;
+> >>         pinctrl-suspend = <&pctrl0 5 0 2 0 0>,
+> >>                                 <&pctrl0 5 1 2 0 0>;
 > >> };
 > >
 > > Maybe we should have just the active/suspend/off flags in the
@@ -28,11 +28,11 @@ OK great.
 > >> pinctrl-* specifier is
 > >>
 > >> property-name = <phandle of the pin-controller
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin bank within the pin-controller
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin number within the pin-bank
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin-mux function number
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pull up/down config
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?drive strength config>;
+> >>                            pin bank within the pin-controller
+> >>                            pin number within the pin-bank
+> >>                            pin-mux function number
+> >>                            pull up/down config
+> >>                            drive strength config>;
 > >
 > > Are these all just bits in one register? If so, let's say you
 > > have 16-bits per pin, we might be able to share the generic
@@ -51,11 +51,11 @@ flags separately?
 
 > > The format would then be
 > >
-> > ? ? ? ?#pin-args <4>;
-> > ? ? ? ?...
+> >        #pin-args <4>;
+> >        ...
 > >
-> > ? ? ? ?/* ? ?controller ?offset on ? idle off */
-> > ? ? ? ?pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;
+> >        /*    controller  offset on   idle off */
+> >        pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;
 > >
 > >> * Using the pinmux/pinconfig specifier in device nodes to configure hardware.
 > >>
@@ -103,3 +103,7 @@ could probably be automatically done using runtime PM?
 Cheers,
 
 Tony
+_______________________________________________
+devicetree-discuss mailing list
+devicetree-discuss@lists.ozlabs.org
+https://lists.ozlabs.org/listinfo/devicetree-discuss
diff --git a/a/content_digest b/N1/content_digest
index 0f4b6ff..a8e4d27 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,10 +2,20 @@
  "ref\0CAJuYYwQoh4_SnA9wmy4x+cG0w0hGukxTkODWtcSw_2QHYuDsrg@mail.gmail.com\0"
  "ref\020120119165607.GG22818@atomide.com\0"
  "ref\0CAJuYYwQB1pDu-JS5o3XPA1D8WbVcwbdtD43M4y7PeJNWeNXxQQ@mail.gmail.com\0"
- "From\0tony@atomide.com (Tony Lindgren)\0"
- "Subject\0Pinmux bindings proposal\0"
+ "ref\0CAJuYYwQB1pDu-JS5o3XPA1D8WbVcwbdtD43M4y7PeJNWeNXxQQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>\0"
+ "Subject\0Re: Pinmux bindings proposal\0"
  "Date\0Thu, 19 Jan 2012 10:20:19 -0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Thomas Abraham <thomas.abraham-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\0"
+ "Cc\0linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org <linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>"
+  devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
+  s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
+  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
+  rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
+  kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
+  cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
+  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
+ " Dong Aisheng <dongas86-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "* Thomas Abraham <thomas.abraham@linaro.org> [120119 09:05]:\n"
@@ -13,12 +23,12 @@
  "> On 19 January 2012 22:26, Tony Lindgren <tony@atomide.com> wrote:\n"
  "> > * Thomas Abraham <thomas.abraham@linaro.org> [120119 04:37]:\n"
  "> >>\n"
- "> >> i2c0: i2c at 18000000 {\n"
- "> >> ? ? ? ? [... other properties ...]\n"
- "> >> ? ? ? ? pinctrl-active = <&pctrl0 5 0 2 3 0>,\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<&pctrl0 5 1 2 3 0>;\n"
- "> >> ? ? ? ? pinctrl-suspend = <&pctrl0 5 0 2 0 0>,\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? <&pctrl0 5 1 2 0 0>;\n"
+ "> >> i2c0: i2c@18000000 {\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 [... other properties ...]\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 pinctrl-active = <&pctrl0 5 0 2 3 0>,\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240<&pctrl0 5 1 2 3 0>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 pinctrl-suspend = <&pctrl0 5 0 2 0 0>,\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <&pctrl0 5 1 2 0 0>;\n"
  "> >> };\n"
  "> >\n"
  "> > Maybe we should have just the active/suspend/off flags in the\n"
@@ -38,11 +48,11 @@
  "> >> pinctrl-* specifier is\n"
  "> >>\n"
  "> >> property-name = <phandle of the pin-controller\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin bank within the pin-controller\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin number within the pin-bank\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin-mux function number\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pull up/down config\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?drive strength config>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin bank within the pin-controller\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin number within the pin-bank\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin-mux function number\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pull up/down config\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240drive strength config>;\n"
  "> >\n"
  "> > Are these all just bits in one register? If so, let's say you\n"
  "> > have 16-bits per pin, we might be able to share the generic\n"
@@ -61,11 +71,11 @@
  "\n"
  "> > The format would then be\n"
  "> >\n"
- "> > ? ? ? ?#pin-args <4>;\n"
- "> > ? ? ? ?...\n"
+ "> > \302\240 \302\240 \302\240 \302\240#pin-args <4>;\n"
+ "> > \302\240 \302\240 \302\240 \302\240...\n"
  "> >\n"
- "> > ? ? ? ?/* ? ?controller ?offset on ? idle off */\n"
- "> > ? ? ? ?pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;\n"
+ "> > \302\240 \302\240 \302\240 \302\240/* \302\240 \302\240controller \302\240offset on \302\240 idle off */\n"
+ "> > \302\240 \302\240 \302\240 \302\240pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;\n"
  "> >\n"
  "> >> * Using the pinmux/pinconfig specifier in device nodes to configure hardware.\n"
  "> >>\n"
@@ -112,6 +122,10 @@
  "\n"
  "Cheers,\n"
  "\n"
- Tony
+ "Tony\n"
+ "_______________________________________________\n"
+ "devicetree-discuss mailing list\n"
+ "devicetree-discuss@lists.ozlabs.org\n"
+ https://lists.ozlabs.org/listinfo/devicetree-discuss
 
-db1bdc84bc0f2889c74a6b65d36efa3344d366f1dabc0c9fddd995f4af8d0bc8
+9a4fc738b30b30f81ce97fbe48503946ab5e6fd7edb778014b5e15aa6eac6b25

diff --git a/a/1.txt b/N2/1.txt
index 88529bd..daad31e 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -3,12 +3,12 @@
 > On 19 January 2012 22:26, Tony Lindgren <tony@atomide.com> wrote:
 > > * Thomas Abraham <thomas.abraham@linaro.org> [120119 04:37]:
 > >>
-> >> i2c0: i2c at 18000000 {
-> >> ? ? ? ? [... other properties ...]
-> >> ? ? ? ? pinctrl-active = <&pctrl0 5 0 2 3 0>,
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<&pctrl0 5 1 2 3 0>;
-> >> ? ? ? ? pinctrl-suspend = <&pctrl0 5 0 2 0 0>,
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? <&pctrl0 5 1 2 0 0>;
+> >> i2c0: i2c@18000000 {
+> >>         [... other properties ...]
+> >>         pinctrl-active = <&pctrl0 5 0 2 3 0>,
+> >>                              <&pctrl0 5 1 2 3 0>;
+> >>         pinctrl-suspend = <&pctrl0 5 0 2 0 0>,
+> >>                                 <&pctrl0 5 1 2 0 0>;
 > >> };
 > >
 > > Maybe we should have just the active/suspend/off flags in the
@@ -28,11 +28,11 @@ OK great.
 > >> pinctrl-* specifier is
 > >>
 > >> property-name = <phandle of the pin-controller
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin bank within the pin-controller
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin number within the pin-bank
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin-mux function number
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pull up/down config
-> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?drive strength config>;
+> >>                            pin bank within the pin-controller
+> >>                            pin number within the pin-bank
+> >>                            pin-mux function number
+> >>                            pull up/down config
+> >>                            drive strength config>;
 > >
 > > Are these all just bits in one register? If so, let's say you
 > > have 16-bits per pin, we might be able to share the generic
@@ -51,11 +51,11 @@ flags separately?
 
 > > The format would then be
 > >
-> > ? ? ? ?#pin-args <4>;
-> > ? ? ? ?...
+> >        #pin-args <4>;
+> >        ...
 > >
-> > ? ? ? ?/* ? ?controller ?offset on ? idle off */
-> > ? ? ? ?pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;
+> >        /*    controller  offset on   idle off */
+> >        pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;
 > >
 > >> * Using the pinmux/pinconfig specifier in device nodes to configure hardware.
 > >>
diff --git a/a/content_digest b/N2/content_digest
index 0f4b6ff..437078f 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,10 +2,22 @@
  "ref\0CAJuYYwQoh4_SnA9wmy4x+cG0w0hGukxTkODWtcSw_2QHYuDsrg@mail.gmail.com\0"
  "ref\020120119165607.GG22818@atomide.com\0"
  "ref\0CAJuYYwQB1pDu-JS5o3XPA1D8WbVcwbdtD43M4y7PeJNWeNXxQQ@mail.gmail.com\0"
- "From\0tony@atomide.com (Tony Lindgren)\0"
- "Subject\0Pinmux bindings proposal\0"
+ "From\0Tony Lindgren <tony@atomide.com>\0"
+ "Subject\0Re: Pinmux bindings proposal\0"
  "Date\0Thu, 19 Jan 2012 10:20:19 -0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Thomas Abraham <thomas.abraham@linaro.org>\0"
+ "Cc\0Stephen Warren <swarren@nvidia.com>"
+  Dong Aisheng-B29396 <B29396@freescale.com>
+  linus.walleij@stericsson.com <linus.walleij@stericsson.com>
+  s.hauer@pengutronix.de <s.hauer@pengutronix.de>
+  rob.herring@calxeda.com <rob.herring@calxeda.com>
+  kernel@pengutronix.de <kernel@pengutronix.de>
+  cjb@laptop.org <cjb@laptop.org>
+  Simon Glass (sjg@chromium.org) <sjg@chromium.org>
+  Dong Aisheng <dongas86@gmail.com>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+ " devicetree-discuss@lists.ozlabs.org <devicetree-discuss@lists.ozlabs.org>\0"
  "\00:1\0"
  "b\0"
  "* Thomas Abraham <thomas.abraham@linaro.org> [120119 09:05]:\n"
@@ -13,12 +25,12 @@
  "> On 19 January 2012 22:26, Tony Lindgren <tony@atomide.com> wrote:\n"
  "> > * Thomas Abraham <thomas.abraham@linaro.org> [120119 04:37]:\n"
  "> >>\n"
- "> >> i2c0: i2c at 18000000 {\n"
- "> >> ? ? ? ? [... other properties ...]\n"
- "> >> ? ? ? ? pinctrl-active = <&pctrl0 5 0 2 3 0>,\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?<&pctrl0 5 1 2 3 0>;\n"
- "> >> ? ? ? ? pinctrl-suspend = <&pctrl0 5 0 2 0 0>,\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? <&pctrl0 5 1 2 0 0>;\n"
+ "> >> i2c0: i2c@18000000 {\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 [... other properties ...]\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 pinctrl-active = <&pctrl0 5 0 2 3 0>,\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240<&pctrl0 5 1 2 3 0>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 pinctrl-suspend = <&pctrl0 5 0 2 0 0>,\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <&pctrl0 5 1 2 0 0>;\n"
  "> >> };\n"
  "> >\n"
  "> > Maybe we should have just the active/suspend/off flags in the\n"
@@ -38,11 +50,11 @@
  "> >> pinctrl-* specifier is\n"
  "> >>\n"
  "> >> property-name = <phandle of the pin-controller\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin bank within the pin-controller\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin number within the pin-bank\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pin-mux function number\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?pull up/down config\n"
- "> >> ? ? ? ? ? ? ? ? ? ? ? ? ? ?drive strength config>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin bank within the pin-controller\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin number within the pin-bank\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pin-mux function number\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240pull up/down config\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240drive strength config>;\n"
  "> >\n"
  "> > Are these all just bits in one register? If so, let's say you\n"
  "> > have 16-bits per pin, we might be able to share the generic\n"
@@ -61,11 +73,11 @@
  "\n"
  "> > The format would then be\n"
  "> >\n"
- "> > ? ? ? ?#pin-args <4>;\n"
- "> > ? ? ? ?...\n"
+ "> > \302\240 \302\240 \302\240 \302\240#pin-args <4>;\n"
+ "> > \302\240 \302\240 \302\240 \302\240...\n"
  "> >\n"
- "> > ? ? ? ?/* ? ?controller ?offset on ? idle off */\n"
- "> > ? ? ? ?pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;\n"
+ "> > \302\240 \302\240 \302\240 \302\240/* \302\240 \302\240controller \302\240offset on \302\240 idle off */\n"
+ "> > \302\240 \302\240 \302\240 \302\240pins = <&pinctrl0 0x0030 0x15 0x15 0x7>;\n"
  "> >\n"
  "> >> * Using the pinmux/pinconfig specifier in device nodes to configure hardware.\n"
  "> >>\n"
@@ -114,4 +126,4 @@
  "\n"
  Tony
 
-db1bdc84bc0f2889c74a6b65d36efa3344d366f1dabc0c9fddd995f4af8d0bc8
+a2a5dff56db03bcde753f5c6f7724a8d3056898745271abeb074e4cbd2695270

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.