diff for duplicates of <20161026084811.GI8574@dell> diff --git a/a/1.txt b/N1/1.txt index 37c9902..d88a28b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -47,7 +47,7 @@ On Tue, 25 Oct 2016, John Syne wrote: > >>>>>>> #define STEPDELAY_OPEN_MASK (0x3FFFF << 0) > >>>>>>> #define STEPDELAY_OPEN(val) ((val) << 0) > >>>>>>> -#define STEPCONFIG_OPENDLY STEPDELAY_OPEN(0x098) -> >>>>> Wouldn’t this be better to add this to the devicetree? +> >>>>> Wouldn?t this be better to add this to the devicetree? > >>>>> > >>>>> ti,chan-step-avg = <0x16 0x16 0x16 0x16 0x16 0x16 0x16>; > >>>>> ti,chan-step-opendelay = <0x500 0x500 0x500 0x500 0x500 0x500 0x500>; @@ -55,7 +55,7 @@ On Tue, 25 Oct 2016, John Syne wrote: > >>>> > >>>> For a touch screen, there is not need to change in these parameter > >>>> settings, so my opinion is to keep it as is. Or am I missing something? -> >>> I was thinking that if you are using this driver as an ADC, you may want the flexibility to make these changes in the DT. I’m doing this by connecting sensors to the ADC inputs. I’m not using this driver for a touchscreen. +> >>> I was thinking that if you are using this driver as an ADC, you may want the flexibility to make these changes in the DT. I?m doing this by connecting sensors to the ADC inputs. I?m not using this driver for a touchscreen. > >> > >> Here is a DT overlay were this gets using on the BeagleBoneBlack. > >> @@ -66,7 +66,7 @@ On Tue, 25 Oct 2016, John Syne wrote: > > This looks like configuration, no? > > > > DT should be used to describe the hardware. -> You may be right, but how is this different to setting the baud rate on a serial channel or sampling rate on a audio channel? Looking through the DT, there are many configuration settings, so I’m not sure what is the correct way to handle this. Surely it is better to handle this in DT vs hard coding these settings? +> You may be right, but how is this different to setting the baud rate on a serial channel or sampling rate on a audio channel? Looking through the DT, there are many configuration settings, so I?m not sure what is the correct way to handle this. Surely it is better to handle this in DT vs hard coding these settings? I think setting the UART baud rate is also an invalid DT entry. @@ -77,5 +77,5 @@ Perhaps as a Kconfig selection. -- Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org │ Open source software for ARM SoCs +Linaro.org ? Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog diff --git a/a/content_digest b/N1/content_digest index 9c1ce54..ee8257b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,20 +5,10 @@ "ref\0DB09B26E-C5AB-427A-82D5-6FE857E7C218@gmail.com\0" "ref\020161025063847.GD8574@dell\0" "ref\0CC15CFB4-60D0-4A63-A3D3-2079CFA31274@gmail.com\0" - "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0Re: [PATCH] drivers: mfd: ti_am335x_tscadc: increase ADC ref clock to 24MHz\0" + "From\0lee.jones@linaro.org (Lee Jones)\0" + "Subject\0[PATCH] drivers: mfd: ti_am335x_tscadc: increase ADC ref clock to 24MHz\0" "Date\0Wed, 26 Oct 2016 09:48:11 +0100\0" - "To\0John Syne <john3909@gmail.com>\0" - "Cc\0Mugunthan V N <mugunthanvnm@ti.com>" - linux-iio@vger.kernel.org - Tony Lindgren <tony@atomide.com> - Jonathan Cameron <jic23@kernel.org> - Vignesh R <vigneshr@ti.com> - linux-omap@vger.kernel.org - linux-arm-kernel@lists.infradead.org - linux-kernel@vger.kernel.org - Sekhar Nori <nsekhar@ti.com> - " Peter Ujfalusi <peter.ujfalusi@ti.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tue, 25 Oct 2016, John Syne wrote:\n" @@ -70,7 +60,7 @@ "> >>>>>>> #define STEPDELAY_OPEN_MASK\t(0x3FFFF << 0)\n" "> >>>>>>> #define STEPDELAY_OPEN(val)\t((val) << 0)\n" "> >>>>>>> -#define STEPCONFIG_OPENDLY\tSTEPDELAY_OPEN(0x098)\n" - "> >>>>> Wouldn\342\200\231t this be better to add this to the devicetree?\n" + "> >>>>> Wouldn?t this be better to add this to the devicetree?\n" "> >>>>> \n" "> >>>>> \tti,chan-step-avg = <0x16 0x16 0x16 0x16 0x16 0x16 0x16>;\n" "> >>>>> \tti,chan-step-opendelay = <0x500 0x500 0x500 0x500 0x500 0x500 0x500>;\n" @@ -78,7 +68,7 @@ "> >>>> \n" "> >>>> For a touch screen, there is not need to change in these parameter\n" "> >>>> settings, so my opinion is to keep it as is. Or am I missing something?\n" - "> >>> I was thinking that if you are using this driver as an ADC, you may want the flexibility to make these changes in the DT. I\342\200\231m doing this by connecting sensors to the ADC inputs. I\342\200\231m not using this driver for a touchscreen. \n" + "> >>> I was thinking that if you are using this driver as an ADC, you may want the flexibility to make these changes in the DT. I?m doing this by connecting sensors to the ADC inputs. I?m not using this driver for a touchscreen. \n" "> >> \n" "> >> Here is a DT overlay were this gets using on the BeagleBoneBlack. \n" "> >> \n" @@ -89,7 +79,7 @@ "> > This looks like configuration, no?\n" "> > \n" "> > DT should be used to describe the hardware.\n" - "> You may be right, but how is this different to setting the baud rate on a serial channel or sampling rate on a audio channel? Looking through the DT, there are many configuration settings, so I\342\200\231m not sure what is the correct way to handle this. Surely it is better to handle this in DT vs hard coding these settings?\n" + "> You may be right, but how is this different to setting the baud rate on a serial channel or sampling rate on a audio channel? Looking through the DT, there are many configuration settings, so I?m not sure what is the correct way to handle this. Surely it is better to handle this in DT vs hard coding these settings?\n" "\n" "I think setting the UART baud rate is also an invalid DT entry.\n" "\n" @@ -100,7 +90,7 @@ "-- \n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org \342\224\202 Open source software for ARM SoCs\n" + "Linaro.org ? Open source software for ARM SoCs\n" Follow Linaro: Facebook | Twitter | Blog -f51315bfe9a72636ead6fa84394d26e949dc79c1b2385d6e1fc18dd8cacbccd6 +c514eb22fcbbe00f3a6d9f4edab38de4925db95c8683f36f908d6f94a2c28863
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.