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

diff --git a/a/1.txt b/N1/1.txt
index 7efef63..86c806d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,10 +6,10 @@
 > >> be more compact:
 > >> (anyway it's another issue and is flexible to be controlled by #pinmux-cells)
 > >> pinctrl_usdhc4: pinconfig-usdhc4 {
-> >> ? ? ? ? /* 0: pin 1: group */
-> >> ? ? ? ? mux-entity = <0>;
-> >> ? ? ? ? func-name = "usdhc4func";
-> >> ? ? ? ? grp-name = "usdhc4grp";
+> >>         /* 0: pin 1: group */
+> >>         mux-entity = <0>;
+> >>         func-name = "usdhc4func";
+> >>         grp-name = "usdhc4grp";
 > >
 > > The func-name and grp-name should be optional here.
 > > This mux entry is already the group, and can be used as
@@ -39,17 +39,17 @@ I used a function name based on the group name initially
 np->full_name of the device requesting the mux when the
 mux was found ;)
 
-> >> ? ? ? ? mux =
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_CMD ?0 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_CLK ?0 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT0 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT1 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT2 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT3 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT4 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT5 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT6 1 MX6Q_USDHC_PAD_CTRL>
-> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT7 1 MX6Q_USDHC_PAD_CTRL>;
+> >>         mux =
+> >>                 <MX6Q_SD4_CMD  0 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_CLK  0 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT0 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT1 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT2 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT3 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT4 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT5 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT6 1 MX6Q_USDHC_PAD_CTRL>
+> >>                 <MX6Q_SD4_DAT7 1 MX6Q_USDHC_PAD_CTRL>;
 > >> };
 > >
 > > For listing basic pins this format works fine for me. It seems
diff --git a/a/content_digest b/N1/content_digest
index 43857b7..c395f17 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,10 +4,24 @@
  "ref\0CAA+hA=RpkP-FFAr8wqVPjSKEMvO_sRHmOK_9nUYfuW=ps0O_=Q@mail.gmail.com\0"
  "ref\020120203173205.GB1426@atomide.com\0"
  "ref\0CAA+hA=QFB7x0yv65LMuLx1exmiUAuB98D+9Fyyk9oeVu+7F2QQ@mail.gmail.com\0"
- "From\0tony@atomide.com (Tony Lindgren)\0"
- "Subject\0Pinmux bindings proposal V2\0"
+ "From\0Tony Lindgren <tony@atomide.com>\0"
+ "Subject\0Re: Pinmux bindings proposal V2\0"
  "Date\0Fri, 3 Feb 2012 13:05:45 -0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Dong Aisheng <dongas86@gmail.com>\0"
+ "Cc\0Stephen Warren <swarren@nvidia.com>"
+  Shawn Guo <shawn.guo@linaro.org>
+  Dong Aisheng-B29396 <B29396@freescale.com>
+  Linus Walleij (linus.walleij@linaro.org) <linus.walleij@linaro.org>
+  Sascha Hauer (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>
+  Thomas Abraham <thomas.abraham@linaro.org>
+  Grant Likely (grant.likely@secretlab.ca) <grant.likely@secretlab.ca>
+  devicetree-discuss@lists.ozlabs.org <devicetree-discuss@lists.ozlabs.org>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+ " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
  "* Dong Aisheng <dongas86@gmail.com> [120203 09:42]:\n"
@@ -18,10 +32,10 @@
  "> >> be more compact:\n"
  "> >> (anyway it's another issue and is flexible to be controlled by #pinmux-cells)\n"
  "> >> pinctrl_usdhc4: pinconfig-usdhc4 {\n"
- "> >> ? ? ? ? /* 0: pin 1: group */\n"
- "> >> ? ? ? ? mux-entity = <0>;\n"
- "> >> ? ? ? ? func-name = \"usdhc4func\";\n"
- "> >> ? ? ? ? grp-name = \"usdhc4grp\";\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 /* 0: pin 1: group */\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 mux-entity = <0>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 func-name = \"usdhc4func\";\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 grp-name = \"usdhc4grp\";\n"
  "> >\n"
  "> > The func-name and grp-name should be optional here.\n"
  "> > This mux entry is already the group, and can be used as\n"
@@ -51,17 +65,17 @@
  "np->full_name of the device requesting the mux when the\n"
  "mux was found ;)\n"
  "\n"
- "> >> ? ? ? ? mux =\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_CMD ?0 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_CLK ?0 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT0 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT1 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT2 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT3 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT4 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT5 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT6 1 MX6Q_USDHC_PAD_CTRL>\n"
- "> >> ? ? ? ? ? ? ? ? <MX6Q_SD4_DAT7 1 MX6Q_USDHC_PAD_CTRL>;\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 mux =\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_CMD \302\2400 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_CLK \302\2400 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT0 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT1 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT2 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT3 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT4 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT5 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT6 1 MX6Q_USDHC_PAD_CTRL>\n"
+ "> >> \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 <MX6Q_SD4_DAT7 1 MX6Q_USDHC_PAD_CTRL>;\n"
  "> >> };\n"
  "> >\n"
  "> > For listing basic pins this format works fine for me. It seems\n"
@@ -90,4 +104,4 @@
  "\n"
  Tony
 
-ee1064fffc77d9033e7545d23434a7c58916c4f07c12e44b9c88d22445fe6d97
+9a458cb7fd8d8ab95794220f78b62d9f051cb444c695ce727a7d856f04b0497d

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.