diff for duplicates of <20111020104919.303e3133@skate> diff --git a/a/1.txt b/N1/1.txt index 084226b..d8fff65 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,14 +1,12 @@ Le Thu, 20 Oct 2011 09:33:29 +0100, -Jonathan Cameron <jic23@cam.ac.uk> a =C3=A9crit : +Jonathan Cameron <jic23@cam.ac.uk> a ?crit : > > * Should we have some low-level ADC driver in arch/arm/mach-at91/ that > > allows to request/release/access the ADC channels, this driver > > providing an internal kernel API used by the IIO ADC driver and the > > touchscreen driver ? -> That's definitely not going to go down well against moves to move everyth= -ing -> that looks like a driver out of the arch directories. An equivalent somew= -here +> That's definitely not going to go down well against moves to move everything +> that looks like a driver out of the arch directories. An equivalent somewhere > else might work though. Yes, of course if this needs to be implemented, it should be in some @@ -24,8 +22,7 @@ My IIO knowledge is still too limited to understand what's the problem with exposing an API for push-based capture. > If we sit something underneath the IIO and input drivers (or use the lower -> portions of IIO to do this) then the intent would be to have a fully gene= -ric +> portions of IIO to do this) then the intent would be to have a fully generic > input touchscreen driver on top. I'm not sure that's possible. I am not sure it's possible to make the touchscreen driver generic. On @@ -36,8 +33,7 @@ driver and the AT91 touchscreen driver might be needed. I'd have to look into more details on how the AT91 touchscreen thing works to provide some more details here. -> For example are the switches on the G45's adc (from datasheet) something = -that +> For example are the switches on the G45's adc (from datasheet) something that > all/many similar touch screen controllers have? I have no idea. @@ -52,7 +48,7 @@ used by another in-kernel driver. Regards, Thomas ---=20 +-- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. diff --git a/a/content_digest b/N1/content_digest index ef4f97d..8a7269d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,30 +4,21 @@ "ref\04E9F15B6.90506@free-electrons.com\0" "ref\020111020090532.7df7af70@skate\0" "ref\04E9FDCD9.7030202@cam.ac.uk\0" - "From\0Thomas Petazzoni <thomas.petazzoni@free-electrons.com>\0" - "Subject\0Re: [PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver.\0" + "From\0thomas.petazzoni@free-electrons.com (Thomas Petazzoni)\0" + "Subject\0[PATCH 2/3] ARM: AT91: IIO: Add AT91 ADC driver.\0" "Date\0Thu, 20 Oct 2011 10:49:19 +0200\0" - "To\0Jonathan Cameron <jic23@cam.ac.uk>\0" - "Cc\0Maxime Ripard <maxime.ripard@free-electrons.com>" - linux-iio@vger.kernel.org - Patrice Vilchez <patrice.vilchez@atmel.com> - Nicolas Ferre <nicolas.ferre@atmel.com> - linux-arm-kernel@lists.infradead.org - Mark Brown <broonie@opensource.wolfsonmicro.com> - " Linus Walleij <linus.walleij@linaro.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Le Thu, 20 Oct 2011 09:33:29 +0100,\n" - "Jonathan Cameron <jic23@cam.ac.uk> a =C3=A9crit :\n" + "Jonathan Cameron <jic23@cam.ac.uk> a ?crit :\n" "\n" "> > * Should we have some low-level ADC driver in arch/arm/mach-at91/ that\n" "> > allows to request/release/access the ADC channels, this driver\n" "> > providing an internal kernel API used by the IIO ADC driver and the\n" "> > touchscreen driver ?\n" - "> That's definitely not going to go down well against moves to move everyth=\n" - "ing\n" - "> that looks like a driver out of the arch directories. An equivalent somew=\n" - "here\n" + "> That's definitely not going to go down well against moves to move everything\n" + "> that looks like a driver out of the arch directories. An equivalent somewhere\n" "> else might work though.\n" "\n" "Yes, of course if this needs to be implemented, it should be in some\n" @@ -43,8 +34,7 @@ "with exposing an API for push-based capture.\n" "\n" "> If we sit something underneath the IIO and input drivers (or use the lower\n" - "> portions of IIO to do this) then the intent would be to have a fully gene=\n" - "ric\n" + "> portions of IIO to do this) then the intent would be to have a fully generic\n" "> input touchscreen driver on top. I'm not sure that's possible.\n" "\n" "I am not sure it's possible to make the touchscreen driver generic. On\n" @@ -55,8 +45,7 @@ "look into more details on how the AT91 touchscreen thing works to\n" "provide some more details here.\n" "\n" - "> For example are the switches on the G45's adc (from datasheet) something =\n" - "that\n" + "> For example are the switches on the G45's adc (from datasheet) something that\n" "> all/many similar touch screen controllers have?\n" "\n" "I have no idea.\n" @@ -71,10 +60,10 @@ "Regards,\n" "\n" "Thomas\n" - "--=20\n" + "-- \n" "Thomas Petazzoni, Free Electrons\n" "Kernel, drivers, real-time and embedded Linux\n" "development, consulting, training and support.\n" http://free-electrons.com -9257e9c7bdfd87e6b4945dacf625302487ac73d662bc0dde7147e5b43a51b524 +1e3d9ea43813391632befa6b55367ec6a972939afe8e1e7f6eaad4c64e742f35
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.