diff for duplicates of <20110810012349.GA23511@yookeroo.fritz.box> diff --git a/a/1.txt b/N1/1.txt index 2afb11a..a4e59df 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,20 +1,20 @@ On Tue, Aug 09, 2011 at 10:44:29AM -0700, Olof Johansson wrote: > On Tue, Aug 9, 2011 at 10:34 AM, Grant Likely <grant.likely@secretlab.ca> wrote: > -> > We talked about this a bit at Linaro connect. Outside of the more +> > We talked about this a bit at Linaro connect. ?Outside of the more > > complex runtime-reconfiguration of pin mux, there is a general need -> > for arbitrary initialization sequences to registers. Also, pretty +> > for arbitrary initialization sequences to registers. ?Also, pretty > > much exactly what you need for tegra is needed for imx, omap and many -> > others. The though was, rather than trying to come up with some kind +> > others. ?The though was, rather than trying to come up with some kind > > of pinmux-specific binding for pin states, which could end up being > > very verbose if everything was split out into properties, we could > > instead have a binding for register initialization sequences. > > Something like this: > > -> > pinmux-initseq = <reg1 value1> <reg1 value2> ...; +> > ? ? ? ?pinmux-initseq = <reg1 value1> <reg1 value2> ...; > > > > And then add some macros for DTC to make it easier to define things -> > like pinmux setup tables. Although the binding above is probably too +> > like pinmux setup tables. ?Although the binding above is probably too > > simple and naive. > > This seems to break the philosophy of what the device tree should do diff --git a/a/content_digest b/N1/content_digest index d46732d..2bbaa56 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,35 +1,29 @@ "ref\074CDBE0F657A3D45AFBB94109FB122FF049F17229E@HQMAIL01.nvidia.com\0" "ref\020110809173428.GB32195@ponder.secretlab.ca\0" "ref\0CAOesGMjH8hZSAXvDZ6ADO-dtFNecRYC5GsfRiAeV8KMRG=JTkQ@mail.gmail.com\0" - "ref\0CAOesGMjH8hZSAXvDZ6ADO-dtFNecRYC5GsfRiAeV8KMRG=JTkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0" - "From\0David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>\0" - "Subject\0Re: Tegra pinmux Device Tree support\0" + "From\0david@gibson.dropbear.id.au (David Gibson)\0" + "Subject\0Tegra pinmux Device Tree support\0" "Date\0Wed, 10 Aug 2011 11:23:49 +1000\0" - "To\0Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>\0" - "Cc\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>" - Linus Walleij (linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org) <linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> - linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> - devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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 Tue, Aug 09, 2011 at 10:44:29AM -0700, Olof Johansson wrote:\n" "> On Tue, Aug 9, 2011 at 10:34 AM, Grant Likely <grant.likely@secretlab.ca> wrote:\n" "> \n" - "> > We talked about this a bit at Linaro connect. \302\240Outside of the more\n" + "> > We talked about this a bit at Linaro connect. ?Outside of the more\n" "> > complex runtime-reconfiguration of pin mux, there is a general need\n" - "> > for arbitrary initialization sequences to registers. \302\240Also, pretty\n" + "> > for arbitrary initialization sequences to registers. ?Also, pretty\n" "> > much exactly what you need for tegra is needed for imx, omap and many\n" - "> > others. \302\240The though was, rather than trying to come up with some kind\n" + "> > others. ?The though was, rather than trying to come up with some kind\n" "> > of pinmux-specific binding for pin states, which could end up being\n" "> > very verbose if everything was split out into properties, we could\n" "> > instead have a binding for register initialization sequences.\n" "> > Something like this:\n" "> >\n" - "> > \302\240 \302\240 \302\240 \302\240pinmux-initseq = <reg1 value1> <reg1 value2> ...;\n" + "> > ? ? ? ?pinmux-initseq = <reg1 value1> <reg1 value2> ...;\n" "> >\n" "> > And then add some macros for DTC to make it easier to define things\n" - "> > like pinmux setup tables. \302\240Although the binding above is probably too\n" + "> > like pinmux setup tables. ?Although the binding above is probably too\n" "> > simple and naive.\n" "> \n" "> This seems to break the philosophy of what the device tree should do\n" @@ -45,4 +39,4 @@ "\t\t\t\t| _way_ _around_!\n" http://www.ozlabs.org/~dgibson -64459b7b80c6d6c4893339435c12aaae542107041f584007ac035bb694d01b41 +aaad7f03d33fafb722b5d79af76be2cae79da84e8797bc5e68c0e175c01850a7
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.