diff for duplicates of <20120509143159.GU3955@opensource.wolfsonmicro.com> diff --git a/a/1.txt b/N1/1.txt index 41259ae..7c12755 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,11 +3,11 @@ On Wed, May 09, 2012 at 10:13:28PM +0800, Thomas Abraham wrote: > > On Wed, May 09, 2012 at 03:34:54AM +0530, Thomas Abraham wrote: > >> +- gpios: The gpio specifier for clock, mosi and miso interface lines (in no -> >> + particular order). The format of the gpio specifier depends on the gpio -> >> + controller. +> >> + ?particular order). The format of the gpio specifier depends on the gpio +> >> + ?controller. -> > This seems odd... This isn't a bitbanging controller, and surely the -> > driver will need to know which signal is which? I suspect this is +> > This seems odd... ?This isn't a bitbanging controller, and surely the +> > driver will need to know which signal is which? ?I suspect this is > > actually for pinmux rather than to identify the signals but that should > > at least be made clear and really should be being done using the pinmux > > API. @@ -23,9 +23,9 @@ I'd suggest just specifying the order - someone might want to use it later for some reason and it's not really a hardship for someone to use it. Avoids any "how does that work?" questions like I had. -> >> + - samsung,spi-cs-gpio: A gpio specifier that specifies the gpio line used as -> >> + the slave select line by the spi controller. The format of the gpio -> >> + specifier depends on the gpio controller. +> >> + ?- samsung,spi-cs-gpio: A gpio specifier that specifies the gpio line used as +> >> + ? ?the slave select line by the spi controller. The format of the gpio +> >> + ? ?specifier depends on the gpio controller. > > We should really have a binding for this at the SPI level (and ideally > > some code to manage setting the GPIO too) - it's pretty common to use a @@ -39,3 +39,10 @@ it. Avoids any "how does that work?" questions like I had. Yeah, I know. I'm saying we should try to come up with a binding for this that can be used by new SPI contollers going forward so things are consistent. +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: signature.asc +Type: application/pgp-signature +Size: 836 bytes +Desc: Digital signature +URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120509/15462c0f/attachment.sig> diff --git a/a/2.bin b/a/2.bin deleted file mode 100644 index fcbd96d..0000000 --- a/a/2.bin +++ /dev/null @@ -1,17 +0,0 @@ ------BEGIN PGP SIGNATURE----- -Version: GnuPG v1.4.12 (GNU/Linux) - -iQIcBAEBAgAGBQJPqn/VAAoJEBus8iNuMP3dIwgP/3KPY/u7tdmncacubX4YNq26 -fkT53lEMXPD5GNuFpeifkemEmgW/yU7q4o8qYUvcxnYaoQ3kBY4UJ6Sphfj02GUY -+oEH4tTtKhrbxBXsZD7KNtlLNO2vZpv4zNxz7Zjp0iKbX0XGIpkSwerP0R7OFoLi -dCvkCXNt9YbZNmPaV5SvbXqhE5UbkmjJBzFjoF/I4/g2bUBkOz3cuAzax/iQqipZ -15j+7Ikt/1u19mN/qNm1rbdGgTKyv9u8cD0aAc2RbHkmHiB8QkQZEP8g9rmFDZYf -OcG9xY7Nn2+9yzKoV/xYR6yVHYSjGoNSvJR841zxOvI8qFgR8tc6kLA76JwNBild -A22jztub5Sc4p64UykJE0k61xTa876pA7XJjG4zrpvUoJN2KDXfPDIx8XsXomHua -Ab53pDVoZrhig1ZbeEjh6/hVbvw8hWWRiocuZX6dyPOaPh1vsUeDolrkN4uhFv4q -dfDwo2qIJVpUplYjjjiYY5JFoVUrA5EUwLrEz19S9OIRpm2gHAqki0C1UdmyanuW -pQLO65zd9YHnEYjzkZSqnXMcMgJ3mpCd0gi+9zPSjvP/AAK9TOm/3KK6Tt+t4oJy -JRmzfIG54US56HLAJbqLNak0CPVaCcTxhBTAI8Bycd1o/oRnebofhXwXU5fY60RR -ZghtrfNI4v8TpIaEE9bo -=4jZk ------END PGP SIGNATURE----- diff --git a/a/2.hdr b/a/2.hdr deleted file mode 100644 index 3237378..0000000 --- a/a/2.hdr +++ /dev/null @@ -1,2 +0,0 @@ -Content-Type: application/pgp-signature; name="signature.asc" -Content-Description: Digital signature diff --git a/a/content_digest b/N1/content_digest index 571ff65..f6dd6be 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,30 +2,22 @@ "ref\01336514694-22393-11-git-send-email-thomas.abraham@linaro.org\0" "ref\020120509090716.GC28702@sirena.org.uk\0" "ref\0CAJuYYwQF9Hh3wJpPTfXm_5iirvHzgwDu6imuSgH-ggenj=Vc8Q@mail.gmail.com\0" - "From\0Mark Brown <broonie@opensource.wolfsonmicro.com>\0" - "Subject\0Re: [PATCH 10/10] spi: s3c64xx: add device tree support\0" + "From\0broonie@opensource.wolfsonmicro.com (Mark Brown)\0" + "Subject\0[PATCH 10/10] spi: s3c64xx: add device tree support\0" "Date\0Wed, 9 May 2012 15:32:00 +0100\0" - "To\0Thomas Abraham <thomas.abraham@linaro.org>\0" - "Cc\0spi-devel-general@lists.sourceforge.net" - devicetree-discuss@lists.ozlabs.org - kgene.kim@samsung.com - rob.herring@calxeda.com - grant.likely@secretlab.ca - jaswinder.singh@linaro.org - linux-samsung-soc@vger.kernel.org - " linux-arm-kernel@lists.infradead.org\0" - "\01:1\0" + "To\0linux-arm-kernel@lists.infradead.org\0" + "\00:1\0" "b\0" "On Wed, May 09, 2012 at 10:13:28PM +0800, Thomas Abraham wrote:\n" "> On 9 May 2012 17:07, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:\n" "> > On Wed, May 09, 2012 at 03:34:54AM +0530, Thomas Abraham wrote:\n" "\n" "> >> +- gpios: The gpio specifier for clock, mosi and miso interface lines (in no\n" - "> >> + \302\240particular order). The format of the gpio specifier depends on the gpio\n" - "> >> + \302\240controller.\n" + "> >> + ?particular order). The format of the gpio specifier depends on the gpio\n" + "> >> + ?controller.\n" "\n" - "> > This seems odd... \302\240This isn't a bitbanging controller, and surely the\n" - "> > driver will need to know which signal is which? \302\240I suspect this is\n" + "> > This seems odd... ?This isn't a bitbanging controller, and surely the\n" + "> > driver will need to know which signal is which? ?I suspect this is\n" "> > actually for pinmux rather than to identify the signals but that should\n" "> > at least be made clear and really should be being done using the pinmux\n" "> > API.\n" @@ -41,9 +33,9 @@ "later for some reason and it's not really a hardship for someone to use\n" "it. Avoids any \"how does that work?\" questions like I had.\n" "\n" - "> >> + \302\240- samsung,spi-cs-gpio: A gpio specifier that specifies the gpio line used as\n" - "> >> + \302\240 \302\240the slave select line by the spi controller. The format of the gpio\n" - "> >> + \302\240 \302\240specifier depends on the gpio controller.\n" + "> >> + ?- samsung,spi-cs-gpio: A gpio specifier that specifies the gpio line used as\n" + "> >> + ? ?the slave select line by the spi controller. The format of the gpio\n" + "> >> + ? ?specifier depends on the gpio controller.\n" "\n" "> > We should really have a binding for this at the SPI level (and ideally\n" "> > some code to manage setting the GPIO too) - it's pretty common to use a\n" @@ -56,27 +48,13 @@ "\n" "Yeah, I know. I'm saying we should try to come up with a binding for\n" "this that can be used by new SPI contollers going forward so things are\n" - consistent. - "\01:2\0" - "fn\0signature.asc\0" - "d\0Digital signature\0" - "b\0" - "-----BEGIN PGP SIGNATURE-----\n" - "Version: GnuPG v1.4.12 (GNU/Linux)\n" - "\n" - "iQIcBAEBAgAGBQJPqn/VAAoJEBus8iNuMP3dIwgP/3KPY/u7tdmncacubX4YNq26\n" - "fkT53lEMXPD5GNuFpeifkemEmgW/yU7q4o8qYUvcxnYaoQ3kBY4UJ6Sphfj02GUY\n" - "+oEH4tTtKhrbxBXsZD7KNtlLNO2vZpv4zNxz7Zjp0iKbX0XGIpkSwerP0R7OFoLi\n" - "dCvkCXNt9YbZNmPaV5SvbXqhE5UbkmjJBzFjoF/I4/g2bUBkOz3cuAzax/iQqipZ\n" - "15j+7Ikt/1u19mN/qNm1rbdGgTKyv9u8cD0aAc2RbHkmHiB8QkQZEP8g9rmFDZYf\n" - "OcG9xY7Nn2+9yzKoV/xYR6yVHYSjGoNSvJR841zxOvI8qFgR8tc6kLA76JwNBild\n" - "A22jztub5Sc4p64UykJE0k61xTa876pA7XJjG4zrpvUoJN2KDXfPDIx8XsXomHua\n" - "Ab53pDVoZrhig1ZbeEjh6/hVbvw8hWWRiocuZX6dyPOaPh1vsUeDolrkN4uhFv4q\n" - "dfDwo2qIJVpUplYjjjiYY5JFoVUrA5EUwLrEz19S9OIRpm2gHAqki0C1UdmyanuW\n" - "pQLO65zd9YHnEYjzkZSqnXMcMgJ3mpCd0gi+9zPSjvP/AAK9TOm/3KK6Tt+t4oJy\n" - "JRmzfIG54US56HLAJbqLNak0CPVaCcTxhBTAI8Bycd1o/oRnebofhXwXU5fY60RR\n" - "ZghtrfNI4v8TpIaEE9bo\n" - "=4jZk\n" - "-----END PGP SIGNATURE-----\n" + "consistent.\n" + "-------------- next part --------------\n" + "A non-text attachment was scrubbed...\n" + "Name: signature.asc\n" + "Type: application/pgp-signature\n" + "Size: 836 bytes\n" + "Desc: Digital signature\n" + URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120509/15462c0f/attachment.sig> -9fe2948a0f28059a7d5f45fdb30e8be18d965401233cc4aa1a8bacce2c68c741 +17fdd29a7c70393da8fbcaa584d30cebec10a24a2dd6fa74ec101e06791eaf75
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.