Re: [PATCH v2 4/4] spi: spi-fsl-dspi: Minor code cleanup and error path fixes

On 16-11-21 15:22:09, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Code cleanup for improving code readability and error path fixes > > and cleanup removing use of devm_kfree. > > Two things in one, not very nice. Especially the dma_free_coherent is > really a bug and the

Re: [PATCH v2 4/4] spi: spi-fsl-dspi: Minor code cleanup and error path fixes

On 16-11-21 15:22:09, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Code cleanup for improving code readability and error path fixes > > and cleanup removing use of devm_kfree. > > Two things in one, not very nice. Especially the dma_free_coherent is > really a bug and the

Re: [PATCH v2 2/4] spi: spi-fsl-dspi: Fix continuous selection format

On 16-11-21 15:15:41, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change variable and

Re: [PATCH v2 2/4] spi: spi-fsl-dspi: Fix continuous selection format

On 16-11-21 15:15:41, Stefan Agner wrote: > On 2016-11-20 21:54, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change variable and

Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE

Hello Mark, On 16-11-22 00:44:30, maitysancha...@gmail.com wrote: > Hello Mark, > > On 16-11-21 19:18:47, Mark Brown wrote: > > On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote: > > > Current DMA implementation had a bug where the DMA transfer would > > > exit the loop in

Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE

Hello Mark, On 16-11-22 00:44:30, maitysancha...@gmail.com wrote: > Hello Mark, > > On 16-11-21 19:18:47, Mark Brown wrote: > > On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote: > > > Current DMA implementation had a bug where the DMA transfer would > > > exit the loop in

Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE

Hello Mark, On 16-11-21 19:18:47, Mark Brown wrote: > On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote: > > Current DMA implementation had a bug where the DMA transfer would > > exit the loop in dspi_transfer_one_message after the completion of > > a single transfer. This results

Re: [PATCH v2 1/4] spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE

Hello Mark, On 16-11-21 19:18:47, Mark Brown wrote: > On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote: > > Current DMA implementation had a bug where the DMA transfer would > > exit the loop in dspi_transfer_one_message after the completion of > > a single transfer. This results

Re: [PATCH 2/4] spi: spi-fsl-dspi: Fix incorrect DMA setup

On 16-11-17 17:03:19, Stefan Agner wrote: > On 2016-11-17 04:16, Sanchayan Maity wrote: > > Currently dmaengine_prep_slave_single was being called with length > > set to the complete DMA buffer size. This resulted in unwanted bytes > > being transferred to the SPI register leading to clock and

Re: [PATCH 2/4] spi: spi-fsl-dspi: Fix incorrect DMA setup

On 16-11-17 17:03:19, Stefan Agner wrote: > On 2016-11-17 04:16, Sanchayan Maity wrote: > > Currently dmaengine_prep_slave_single was being called with length > > set to the complete DMA buffer size. This resulted in unwanted bytes > > being transferred to the SPI register leading to clock and

Re: [PATCH 3/4] spi: spi-fsl-dspi: Fix continuous selection format

Hello Stefan, On 16-11-17 17:07:24, Stefan Agner wrote: > On 2016-11-17 04:16, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change

Re: [PATCH 3/4] spi: spi-fsl-dspi: Fix continuous selection format

Hello Stefan, On 16-11-17 17:07:24, Stefan Agner wrote: > On 2016-11-17 04:16, Sanchayan Maity wrote: > > Current DMA implementation was not handling the continuous selection > > format viz. SPI chip select would be deasserted even between sequential > > serial transfers. Use the cs_change

Re: [PATCH] ARM: dts: vfxxx: Enable DMA for DSPI2 and DSPI3

On 16-11-11 20:46:12, Fabio Estevam wrote: > On Thu, Nov 10, 2016 at 9:45 AM, Sanchayan Maity > wrote: > > Enable DMA for DSPI2 and DSPI3 on Vybrid. > > You missed your Signed-off-by line. Argh...Sorry about that...Will send a follow patch with this fixed. -

Re: [PATCH] ARM: dts: vfxxx: Enable DMA for DSPI2 and DSPI3

On 16-11-11 20:46:12, Fabio Estevam wrote: > On Thu, Nov 10, 2016 at 9:45 AM, Sanchayan Maity > wrote: > > Enable DMA for DSPI2 and DSPI3 on Vybrid. > > You missed your Signed-off-by line. Argh...Sorry about that...Will send a follow patch with this fixed. - Sanchayan.

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

Hello Shawn, On 16-10-22 15:43:04, Vladimir Zapolskiy wrote: > Hi Shawn, > > On 10/22/2016 06:25 AM, Shawn Guo wrote: > > On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote: > > > Remove the use of DDC I2C bus bitbang to support reading of EDID > > > and rely on support from

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

Hello Shawn, On 16-10-22 15:43:04, Vladimir Zapolskiy wrote: > Hi Shawn, > > On 10/22/2016 06:25 AM, Shawn Guo wrote: > > On Mon, Sep 19, 2016 at 10:41:51AM +0530, Sanchayan Maity wrote: > > > Remove the use of DDC I2C bus bitbang to support reading of EDID > > > and rely on support from

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

Hello, Ping? - Sanchayan. On 16-09-21 16:54:38, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity > --- > arch/arm/boot/dts/Makefile | 1 + > arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts |

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

Hello, Ping? - Sanchayan. On 16-09-21 16:54:38, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity > --- > arch/arm/boot/dts/Makefile | 1 + > arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts | 253 >

Re: [PATCH v2] spi: spi-fsl-dspi: Add DMA support for Vybrid

Hello, Ping? Regards, Sanchayan. On 16-10-04 16:28:33, Sanchayan Maity wrote: > Add DMA support for Vybrid. > > Signed-off-by: Sanchayan Maity > --- > Changes since v1: > - Change in the dspi_dma_xfer function. Use more apt DSPI_FIFO_SIZE > instead of sizeof(u32) > -

Re: [PATCH v2] spi: spi-fsl-dspi: Add DMA support for Vybrid

Hello, Ping? Regards, Sanchayan. On 16-10-04 16:28:33, Sanchayan Maity wrote: > Add DMA support for Vybrid. > > Signed-off-by: Sanchayan Maity > --- > Changes since v1: > - Change in the dspi_dma_xfer function. Use more apt DSPI_FIFO_SIZE > instead of sizeof(u32) > - Do not set RSER on every

Re: [PATCH v1 1/2] ARM: dts: vfxxx: Enable DMA for DSPI on Vybrid

Hello Stefan, On 16-10-03 11:05:59, Stefan Agner wrote: > On 2016-10-03 05:50, Sanchayan Maity wrote: > > Enable DMA for DSPI on Vybrid. > > Hm, we have that in 4.4 already, is that meant for 4.1? Sorry?! I send this out for mainline and the patch series is based on top of shawn's for-next

Re: [PATCH v1 1/2] ARM: dts: vfxxx: Enable DMA for DSPI on Vybrid

Hello Stefan, On 16-10-03 11:05:59, Stefan Agner wrote: > On 2016-10-03 05:50, Sanchayan Maity wrote: > > Enable DMA for DSPI on Vybrid. > > Hm, we have that in 4.4 already, is that meant for 4.1? Sorry?! I send this out for mainline and the patch series is based on top of shawn's for-next

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

Hello, Ping? - Sanchayan. On 16-09-19 10:41:51, Sanchayan Maity wrote: > Remove the use of DDC I2C bus bitbang to support reading of EDID > and rely on support from internal HDMI I2C master controller instead. > As a result remove the device tree property ddc-i2c-bus. > > Signed-off-by:

Re: [PATCH v2 1/3] ARM: dts: imx6qdl-apalis: Do not rely on DDC I2C bus bitbang for HDMI

Hello, Ping? - Sanchayan. On 16-09-19 10:41:51, Sanchayan Maity wrote: > Remove the use of DDC I2C bus bitbang to support reading of EDID > and rely on support from internal HDMI I2C master controller instead. > As a result remove the device tree property ddc-i2c-bus. > > Signed-off-by:

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

Hello, Ping? - Sanchayan. On 16-09-21 16:54:38, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity > --- > arch/arm/boot/dts/Makefile | 1 + > arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts |

Re: [PATCH] ARM: dts: imx6: Add support for Toradex Colibri iMX6 module

Hello, Ping? - Sanchayan. On 16-09-21 16:54:38, Sanchayan Maity wrote: > Add support for Toradex Colibri iMX6 module. > > Signed-off-by: Sanchayan Maity > --- > arch/arm/boot/dts/Makefile | 1 + > arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts | 253 >

Re: [PATCH v1 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight

Hello Marcel, On 16-09-16 13:38:54, Marcel Ziswiler wrote: > On Wed, 2016-09-14 at 12:05 +0530, Sanchayan Maity wrote: > > Use enable-gpios property of PWM backlight driver for backlight > > control. While at it also fix the use of brightness levels required > > by EDT displays which require

Re: [PATCH v1 3/3] ARM: dts: imx6qdl-apalis: Use enable-gpios property for backlight

Hello Marcel, On 16-09-16 13:38:54, Marcel Ziswiler wrote: > On Wed, 2016-09-14 at 12:05 +0530, Sanchayan Maity wrote: > > Use enable-gpios property of PWM backlight driver for backlight > > control. While at it also fix the use of brightness levels required > > by EDT displays which require

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

On 16-07-08 18:23:42, Srinivas Kandagatla wrote: > > > On 08/07/16 17:42, Stefan Agner wrote: > > On 2016-07-08 08:41, Srinivas Kandagatla wrote: > > > On 07/07/16 14:48, maitysancha...@gmail.com wrote: > > > > Hello Srinivas, > > > > > > > > On 16-07-07 1 > > ... > > > > > > > > > > > > >

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

On 16-07-08 18:23:42, Srinivas Kandagatla wrote: > > > On 08/07/16 17:42, Stefan Agner wrote: > > On 2016-07-08 08:41, Srinivas Kandagatla wrote: > > > On 07/07/16 14:48, maitysancha...@gmail.com wrote: > > > > Hello Srinivas, > > > > > > > > On 16-07-07 1 > > ... > > > > > > > > > > > > >

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

Hello Srinivas, On 16-07-07 14:16:36, Srinivas Kandagatla wrote: > > > On 07/07/16 13:33, maitysancha...@gmail.com wrote: > > Hello Srinivas, > > > > On 16-07-07 10:18:49, Srinivas Kandagatla wrote: > > > > > > > > > On 07/07/16 07:39, Sanchayan Maity wrote: > > > > From: Stefan Agner

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

Hello Srinivas, On 16-07-07 14:16:36, Srinivas Kandagatla wrote: > > > On 07/07/16 13:33, maitysancha...@gmail.com wrote: > > Hello Srinivas, > > > > On 16-07-07 10:18:49, Srinivas Kandagatla wrote: > > > > > > > > > On 07/07/16 07:39, Sanchayan Maity wrote: > > > > From: Stefan Agner > > >

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

Hello Srinivas, On 16-07-07 10:18:49, Srinivas Kandagatla wrote: > > > On 07/07/16 07:39, Sanchayan Maity wrote: > > From: Stefan Agner > > > > The existing NVMEM consumer API's do not allow to get a > > NVMEM cell directly given a device tree node. This patch > > adds a

Re: [PATCH v4 3/5] nvmem: core: Add consumer API to get nvmem cell from node

Hello Srinivas, On 16-07-07 10:18:49, Srinivas Kandagatla wrote: > > > On 07/07/16 07:39, Sanchayan Maity wrote: > > From: Stefan Agner > > > > The existing NVMEM consumer API's do not allow to get a > > NVMEM cell directly given a device tree node. This patch > > adds a function to provide

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-27 15:38:17, maitysancha...@gmail.com wrote: > On 16-05-27 10:31:55, Arnd Bergmann wrote: > > On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > > > > > > So if I understand correctly, the binding at the SoC level is fine. > > > Keeping that but

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-27 15:38:17, maitysancha...@gmail.com wrote: > On 16-05-27 10:31:55, Arnd Bergmann wrote: > > On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > > > > > > So if I understand correctly, the binding at the SoC level is fine. > > > Keeping that but

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Stefan, On 16-05-27 10:28:45, Stefan Agner wrote: > On 2016-05-27 03:08, maitysancha...@gmail.com wrote: > > On 16-05-27 10:31:55, Arnd Bergmann wrote: > >> On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > >> > > >> > So if I understand correctly, the binding at

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Stefan, On 16-05-27 10:28:45, Stefan Agner wrote: > On 2016-05-27 03:08, maitysancha...@gmail.com wrote: > > On 16-05-27 10:31:55, Arnd Bergmann wrote: > >> On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > >> > > >> > So if I understand correctly, the binding at

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

On 16-05-27 10:31:55, Arnd Bergmann wrote: > On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > > > > So if I understand correctly, the binding at the SoC level is fine. > > Keeping that but removing the additional made-up properties, viz. below > > > > rom-revision:

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

On 16-05-27 10:31:55, Arnd Bergmann wrote: > On Friday, May 27, 2016 12:03:01 PM CEST maitysancha...@gmail.com wrote: > > > > So if I understand correctly, the binding at the SoC level is fine. > > Keeping that but removing the additional made-up properties, viz. below > > > > rom-revision:

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-24 12:09:41, Rob Herring wrote: > On Mon, May 23, 2016 at 11:14 PM, wrote: > > Hello Rob, > > > > On 16-05-23 16:18:13, Rob Herring wrote: > >> On Fri, May 20, 2016 at 03:32:05PM +0530, Sanchayan Maity wrote: > >> > This adds a SoC driver to be used

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-24 12:09:41, Rob Herring wrote: > On Mon, May 23, 2016 at 11:14 PM, wrote: > > Hello Rob, > > > > On 16-05-23 16:18:13, Rob Herring wrote: > >> On Fri, May 20, 2016 at 03:32:05PM +0530, Sanchayan Maity wrote: > >> > This adds a SoC driver to be used by Freescale Vybrid

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-23 16:18:13, Rob Herring wrote: > On Fri, May 20, 2016 at 03:32:05PM +0530, Sanchayan Maity wrote: > > This adds a SoC driver to be used by Freescale Vybrid SoC's. > > Driver utilises syscon and nvmem consumer API's to get the > > various register values needed and expose the

Re: [PATCH v3 4/4] soc: Add SoC driver for Freescale Vybrid platform

Hello Rob, On 16-05-23 16:18:13, Rob Herring wrote: > On Fri, May 20, 2016 at 03:32:05PM +0530, Sanchayan Maity wrote: > > This adds a SoC driver to be used by Freescale Vybrid SoC's. > > Driver utilises syscon and nvmem consumer API's to get the > > various register values needed and expose the

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

Hello Rob, On 16-05-03 21:30:26, Rob Herring wrote: > On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote: > > Add device tree binding documentation for Vybrid SoC. > > > > Signed-off-by: Sanchayan Maity > > --- > >

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

Hello Rob, On 16-05-03 21:30:26, Rob Herring wrote: > On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote: > > Add device tree binding documentation for Vybrid SoC. > > > > Signed-off-by: Sanchayan Maity > > --- > > .../bindings/arm/freescale/fsl,vf610-soc.txt | 35 > >

Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP

Hello Arnd, On 16-05-02 09:31:12, Arnd Bergmann wrote: > On Monday 02 May 2016 12:35:01 Sanchayan Maity wrote: > > + ocotp@400a5000 { > > + compatible = "fsl,vf610-ocotp"; > > + #address-cells = <1>; > > +

Re: [PATCH v2 2/5] ARM: dts: vfxxx: Add device tree node for OCOTP

Hello Arnd, On 16-05-02 09:31:12, Arnd Bergmann wrote: > On Monday 02 May 2016 12:35:01 Sanchayan Maity wrote: > > + ocotp@400a5000 { > > + compatible = "fsl,vf610-ocotp"; > > + #address-cells = <1>; > > +

Re: [PATCH 05/12] nvmem: vif610-ocotp: remove nvmem regmap dependency

Hello Srinivas, On 16-04-24 20:28:09, Srinivas Kandagatla wrote: > This patch moves to nvmem support in the driver to use callback > instead of regmap. Minor nit, it says "vif610-octop" it should have been vf610-ocotp. For what it's worth, I tested this on Colibri Vybrid VF61 for a while and

Re: [PATCH 05/12] nvmem: vif610-ocotp: remove nvmem regmap dependency

Hello Srinivas, On 16-04-24 20:28:09, Srinivas Kandagatla wrote: > This patch moves to nvmem support in the driver to use callback > instead of regmap. Minor nit, it says "vif610-octop" it should have been vf610-ocotp. For what it's worth, I tested this on Colibri Vybrid VF61 for a while and

Re: [PATCH v1 3/4] ARM: dts: vfxxx: Add OCROM and phandle entries for Vybrid SoC bus driver

Hello, On 16-04-01 14:00:46, Shawn Guo wrote: > On Fri, Mar 11, 2016 at 02:29:30PM +0530, Sanchayan Maity wrote: > > Add OCROM node and introduce phandles to OCROM, MSCM and NVMEM > > OCOTP for use by the Vybrid SoC bus driver. > > > > Signed-off-by: Sanchayan Maity >

Re: [PATCH v1 3/4] ARM: dts: vfxxx: Add OCROM and phandle entries for Vybrid SoC bus driver

Hello, On 16-04-01 14:00:46, Shawn Guo wrote: > On Fri, Mar 11, 2016 at 02:29:30PM +0530, Sanchayan Maity wrote: > > Add OCROM node and introduce phandles to OCROM, MSCM and NVMEM > > OCOTP for use by the Vybrid SoC bus driver. > > > > Signed-off-by: Sanchayan Maity > > --- > >

Re: [RFC PATCH 0/4] Implement USB device/host switch for Vybrid

Hello Peter, On 16-03-29 00:24:46, Peter Chen wrote: > > > > > On 2016-03-25 00:40, Peter Chen wrote: > > > On Tue, Mar 15, 2016 at 02:08:26PM +0530, Sanchayan Maity wrote: > > >> Hello Peter, > > >> > > >> The existing usage of extcon in Chipidea driver relies on OTG > > >> registers. In case

Re: [RFC PATCH 0/4] Implement USB device/host switch for Vybrid

Hello Peter, On 16-03-29 00:24:46, Peter Chen wrote: > > > > > On 2016-03-25 00:40, Peter Chen wrote: > > > On Tue, Mar 15, 2016 at 02:08:26PM +0530, Sanchayan Maity wrote: > > >> Hello Peter, > > >> > > >> The existing usage of extcon in Chipidea driver relies on OTG > > >> registers. In case

Re: [PATCH v1 0/4] Implement SoC bus driver for Vybrid

Hello, Ping. - Sanchayan. On 16-03-11 14:29:27, Sanchayan Maity wrote: > Hello, > > This patchset implements SoC bus support for Freescale Vybrid platform, > implementing the following > https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc > > This a reworked version of an

Re: [PATCH v1 0/4] Implement SoC bus driver for Vybrid

Hello, Ping. - Sanchayan. On 16-03-11 14:29:27, Sanchayan Maity wrote: > Hello, > > This patchset implements SoC bus support for Freescale Vybrid platform, > implementing the following > https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc > > This a reworked version of an

Re: [PATCH v2] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Hello Shawn, On 16-02-14 16:33:49, Shawn Guo wrote: > On Fri, Feb 12, 2016 at 05:53:00PM +0530, Sanchayan Maity wrote: > > Add iio_hwmon node to expose the temperature channel on Vybrid as > > hardware monitor device using the iio_hwmon driver. > > > > Signed-off-by: Sanchayan Maity

Re: [PATCH v2] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Hello Shawn, On 16-02-14 16:33:49, Shawn Guo wrote: > On Fri, Feb 12, 2016 at 05:53:00PM +0530, Sanchayan Maity wrote: > > Add iio_hwmon node to expose the temperature channel on Vybrid as > > hardware monitor device using the iio_hwmon driver. > > > > Signed-off-by: Sanchayan Maity > > --- > >

Re: touchscreen: edt-ft5x06: Prevent DMA driver from mapping an area on stack

Hello, On 15-12-12 20:42:37, Dmitry Torokhov wrote: > On Sat, Dec 12, 2015 at 06:13:55PM +0100, Wolfram Sang wrote: > > > > > Frankly speaking I do not know where the fix should actually be. I2C IMX > > > driver somehow taking care of this or the users of I2C, touchscreen > > > drivers > > > in

Re: touchscreen: edt-ft5x06: Prevent DMA driver from mapping an area on stack

Hello, On 15-12-12 20:42:37, Dmitry Torokhov wrote: > On Sat, Dec 12, 2015 at 06:13:55PM +0100, Wolfram Sang wrote: > > > > > Frankly speaking I do not know where the fix should actually be. I2C IMX > > > driver somehow taking care of this or the users of I2C, touchscreen > > > drivers > > > in

Re: [PATCH] ARM: dts: vfxxx: Fix erroneous property in esdhc0 node

Ping? On 15-10-18 11:18:48, Sanchayan Maity wrote: > Something seems to have gone wrong during the merging of the device > tree changes with the following patch > > "ARM: dts: add property for maximum ADC clock frequencies" > > The property "fsl,adck-max-frequency" instead of being applied for

Re: [PATCH] ARM: dts: vfxxx: Fix erroneous property in esdhc0 node

Ping? On 15-10-18 11:18:48, Sanchayan Maity wrote: > Something seems to have gone wrong during the merging of the device > tree changes with the following patch > > "ARM: dts: add property for maximum ADC clock frequencies" > > The property "fsl,adck-max-frequency" instead of being applied for

Re: [PATCH v5 1/3] ARM: dts: vf500-colibri: Add device tree node for touchscreen support

Hello Shawn, The driver has landed in your tree. Can you queue this DT change for the same? Thanks. - Sanchayan. On 15-09-01 18:06:53, Sanchayan Maity wrote: > Add device tree node for touchscreen support on Colibri VF50. The > touchscreen functionality on VF50 uses the ADC channels of Vybrid

Re: [PATCH v5 1/3] ARM: dts: vf500-colibri: Add device tree node for touchscreen support

Hello Shawn, The driver has landed in your tree. Can you queue this DT change for the same? Thanks. - Sanchayan. On 15-09-01 18:06:53, Sanchayan Maity wrote: > Add device tree node for touchscreen support on Colibri VF50. The > touchscreen functionality on VF50 uses the ADC channels of Vybrid

Re: [PATCH v10 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? - Sanchayan. On 15-09-07 13:51:34, Sanchayan Maity wrote: > Hello, > > Tested on Greg's tree char-misc-next branch along with Stefan's NAND driver > patchset. > > Sample output on Colibri VF50 > > root@colibri-vf:/sys/bus/nvmem/devices/ocotp0# uname -a > Linux colibri-vf

Re: [PATCH v10 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? - Sanchayan. On 15-09-07 13:51:34, Sanchayan Maity wrote: > Hello, > > Tested on Greg's tree char-misc-next branch along with Stefan's NAND driver > patchset. > > Sample output on Colibri VF50 > > root@colibri-vf:/sys/bus/nvmem/devices/ocotp0# uname -a > Linux colibri-vf

Re: [PATCH] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Hi Shawn, On 15-09-06 12:32:32, Shawn Guo wrote: > On Thu, Aug 06, 2015 at 09:28:22PM +0530, Sanchayan Maity wrote: > > Add iio_hwmon node to expose the temperature channel on Vybrid > > as hardware monitor device using the iio_hwmon driver. > > > > Signed-off-by: Sanchayan Maity > > --- > >

Re: [PATCH] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Hi Shawn, On 15-09-06 12:32:32, Shawn Guo wrote: > On Thu, Aug 06, 2015 at 09:28:22PM +0530, Sanchayan Maity wrote: > > Add iio_hwmon node to expose the temperature channel on Vybrid > > as hardware monitor device using the iio_hwmon driver. > > > > Signed-off-by: Sanchayan Maity

Re: [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver

On 15-09-06 16:13:35, Shawn Guo wrote: > On Wed, Aug 12, 2015 at 06:49:21PM +0530, Sanchayan Maity wrote: > > Add the devicetree bindings for the Freescale Vybrid On-Chip > > OTP driver. > > > > Signed-off-by: Sanchayan Maity > > Acked-by: Srinivas Kandagatla > > --- > >

Re: [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller

On 15-09-06 16:15:26, Shawn Guo wrote: > On Wed, Aug 12, 2015 at 06:49:18PM +0530, Sanchayan Maity wrote: > > Add clock support for Vybrid On-Chip One Time Programmable > > (OCOTP) controller. > > > > While the OCOTP block does not require explicit clock gating, > > for programming the OCOTP

Re: [PATCH v9 1/4] clk: clk-vf610: Add clock for Vybrid OCOTP controller

On 15-09-06 16:15:26, Shawn Guo wrote: > On Wed, Aug 12, 2015 at 06:49:18PM +0530, Sanchayan Maity wrote: > > Add clock support for Vybrid On-Chip One Time Programmable > > (OCOTP) controller. > > > > While the OCOTP block does not require explicit clock gating, > > for programming the OCOTP

Re: [PATCH v9 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver

On 15-09-06 16:13:35, Shawn Guo wrote: > On Wed, Aug 12, 2015 at 06:49:21PM +0530, Sanchayan Maity wrote: > > Add the devicetree bindings for the Freescale Vybrid On-Chip > > OTP driver. > > > > Signed-off-by: Sanchayan Maity > > Acked-by: Srinivas Kandagatla

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hi, On 15-09-04 09:21:04, Srinivas Kandagatla wrote: > Hi Sanchayan, > > On 04/09/15 06:50, maitysancha...@gmail.com wrote: > > Hello, > > > > Ping? Anything preventing this from being accepted? I can rework it then if > > so. > Thanks for your patience, > > We are in the middle of merge

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hi, On 15-09-04 09:21:04, Srinivas Kandagatla wrote: > Hi Sanchayan, > > On 04/09/15 06:50, maitysancha...@gmail.com wrote: > > Hello, > > > > Ping? Anything preventing this from being accepted? I can rework it then if > > so. > Thanks for your patience, > > We are in the middle of merge

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? Anything preventing this from being accepted? I can rework it then if so. Thanks. - Sanchayan. On 15-08-12 18:49:17, Sanchayan Maity wrote: > Hello, > > This patchset is based on top of v9 of Srinivas's NVMEM framework patches. > Tested on Greg's tree char-misc-next branch along

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? Anything preventing this from being accepted? I can rework it then if so. Thanks. - Sanchayan. On 15-08-12 18:49:17, Sanchayan Maity wrote: > Hello, > > This patchset is based on top of v9 of Srinivas's NVMEM framework patches. > Tested on Greg's tree char-misc-next branch along

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? Any feedback? Is this good to be merged? Thanks. - Sanchayan. On 15-08-12 18:49:17, Sanchayan Maity wrote: > Hello, > > This patchset is based on top of v9 of Srinivas's NVMEM framework patches. > Tested on Greg's tree char-misc-next branch along with Stefan's NAND driver >

Re: [PATCH v9 0/4] Implement OCOTP driver for Vybrid using NVMEM

Hello, Ping? Any feedback? Is this good to be merged? Thanks. - Sanchayan. On 15-08-12 18:49:17, Sanchayan Maity wrote: Hello, This patchset is based on top of v9 of Srinivas's NVMEM framework patches. Tested on Greg's tree char-misc-next branch along with Stefan's NAND driver patchset.

Re: [PATCH v4 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

Hello Dmitry, On 15-08-21 18:30:57, Dmitry Torokhov wrote: > Hi Sanchayan, > > On Fri, Aug 21, 2015 at 06:56:32PM +0530, Sanchayan Maity wrote: > > The Colibri Vybrid VF50 module supports 4-wire touchscreens using > > FETs and ADC inputs. This driver uses the IIO consumer interface > > and

Re: [PATCH v4 2/3] input: Add DT binding documentation for Colibri VF50 touchscreen

On 15-08-22 18:36:54, Stefan Agner wrote: > On 2015-08-21 06:26, Sanchayan Maity wrote: > > This adds device tree binding documentation for the Colibri VF50 > > touchscreen driver. > > > > Signed-off-by: Sanchayan Maity > > --- > > .../bindings/input/touchscreen/colibri-vf50-ts.txt | 36 > >

Re: [PATCH v4 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

On 15-08-22 18:52:28, Stefan Agner wrote: > Hi Sanchayan, > > On 2015-08-21 06:26, Sanchayan Maity wrote: > > +static int vf50_ts_probe(struct platform_device *pdev) > > +{ > > + struct input_dev *input; > > + struct iio_channel *channels; > > + struct device *dev = >dev; > > + struct

Re: [PATCH v4 1/3] ARM: dts: vf500-colibri: Add device tree node for touchscreen support

On 15-08-22 18:54:28, Stefan Agner wrote: > On 2015-08-21 06:26, Sanchayan Maity wrote: > > Add device tree node for touchscreen support on Colibri VF50. The > > touchscreen functionality on VF50 uses the ADC channels of Vybrid > > and some GPIOs. Also add pinctrl nodes for proper pinmux. > > > >

Re: [PATCH v4 2/3] input: Add DT binding documentation for Colibri VF50 touchscreen

On 15-08-22 18:36:54, Stefan Agner wrote: On 2015-08-21 06:26, Sanchayan Maity wrote: This adds device tree binding documentation for the Colibri VF50 touchscreen driver. Signed-off-by: Sanchayan Maity maitysancha...@gmail.com --- .../bindings/input/touchscreen/colibri-vf50-ts.txt |

Re: [PATCH v4 1/3] ARM: dts: vf500-colibri: Add device tree node for touchscreen support

On 15-08-22 18:54:28, Stefan Agner wrote: On 2015-08-21 06:26, Sanchayan Maity wrote: Add device tree node for touchscreen support on Colibri VF50. The touchscreen functionality on VF50 uses the ADC channels of Vybrid and some GPIOs. Also add pinctrl nodes for proper pinmux.

Re: [PATCH v4 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

On 15-08-22 18:52:28, Stefan Agner wrote: Hi Sanchayan, On 2015-08-21 06:26, Sanchayan Maity wrote: +static int vf50_ts_probe(struct platform_device *pdev) +{ + struct input_dev *input; + struct iio_channel *channels; + struct device *dev = pdev-dev; + struct

Re: [PATCH v4 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

Hello Dmitry, On 15-08-21 18:30:57, Dmitry Torokhov wrote: Hi Sanchayan, On Fri, Aug 21, 2015 at 06:56:32PM +0530, Sanchayan Maity wrote: The Colibri Vybrid VF50 module supports 4-wire touchscreens using FETs and ADC inputs. This driver uses the IIO consumer interface and relies on the

Re: [PATCH] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Ping? - Sanchayan. On 15-08-06 21:28:22, Sanchayan Maity wrote: > Add iio_hwmon node to expose the temperature channel on Vybrid > as hardware monitor device using the iio_hwmon driver. > > Signed-off-by: Sanchayan Maity > --- > arch/arm/boot/dts/vfxxx.dtsi | 5 + > 1 file changed, 5

Re: [PATCH] ARM: dts: vfxxx: Add iio_hwmon node for ADC temperature channel

Ping? - Sanchayan. On 15-08-06 21:28:22, Sanchayan Maity wrote: Add iio_hwmon node to expose the temperature channel on Vybrid as hardware monitor device using the iio_hwmon driver. Signed-off-by: Sanchayan Maity maitysancha...@gmail.com --- arch/arm/boot/dts/vfxxx.dtsi | 5 + 1

Re: [PATCH v4] iio: adc: vf610: Add IIO buffer support for Vybrid ADC

Hello Fugang Duan, Can I have your ACK if you are ok with the changes made by the patch? Thanks & Regards, Sanchayan Maity. On 15-08-17 21:21:40, Sanchayan Maity wrote: > This patch adds support for IIO buffer to the Vybrid ADC driver. > IIO triggered buffer infrastructure along with iio sysfs

Re: [PATCH v4] iio: adc: vf610: Add IIO buffer support for Vybrid ADC

Hello Fugang Duan, Can I have your ACK if you are ok with the changes made by the patch? Thanks Regards, Sanchayan Maity. On 15-08-17 21:21:40, Sanchayan Maity wrote: This patch adds support for IIO buffer to the Vybrid ADC driver. IIO triggered buffer infrastructure along with iio sysfs

Re: [PATCH v3 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

Hello Dmitry, Will take care of all points with the next revision. Thank you for the feedback. - Sanchayan. On 15-08-14 15:53:46, Dmitry Torokhov wrote: > Hi Sanchayan, > > On Wed, Aug 05, 2015 at 02:25:51PM +0530, Sanchayan Maity wrote: > > The Colibri Vybrid VF50 module supports 4-wire

Re: [PATCH v3 3/3] touchscreen: colibri-vf50-ts: Add touchscreen support for Colibri VF50

Hello Dmitry, Will take care of all points with the next revision. Thank you for the feedback. - Sanchayan. On 15-08-14 15:53:46, Dmitry Torokhov wrote: Hi Sanchayan, On Wed, Aug 05, 2015 at 02:25:51PM +0530, Sanchayan Maity wrote: The Colibri Vybrid VF50 module supports 4-wire

Re: [PATCH v3] iio: adc: vf610: Add IIO buffer support for Vybrid ADC

Hello Jonathan, On 15-08-15 21:24:01, Jonathan Cameron wrote: > On 11/08/15 10:05, Sanchayan Maity wrote: > > This patch adds support for IIO buffer to the Vybrid ADC driver. > > IIO triggered buffer infrastructure along with iio sysfs trigger > > is used to leverage continuous sampling support

Re: [PATCH v3] iio: adc: vf610: Add IIO buffer support for Vybrid ADC

Hello Jonathan, On 15-08-15 21:24:01, Jonathan Cameron wrote: On 11/08/15 10:05, Sanchayan Maity wrote: This patch adds support for IIO buffer to the Vybrid ADC driver. IIO triggered buffer infrastructure along with iio sysfs trigger is used to leverage continuous sampling support provided

Re: [PATCH v3 0/3] Add support for touchscreen on Colibri VF50

Hello, Ping? - Sanchayan. On 15-08-05 14:25:48, Sanchayan Maity wrote: > Hello, > > The patchset adds support for 4 wire touchscreen on Toradex Colibri > VF50 modules. Patches are tested on top of shawn's for-next branch. > > Changes since v2: > 1. Fix pin multiplexing for pins in idle state.

Re: [PATCH v3 0/3] Add support for touchscreen on Colibri VF50

Hello, Ping? - Sanchayan. On 15-08-05 14:25:48, Sanchayan Maity wrote: Hello, The patchset adds support for 4 wire touchscreen on Toradex Colibri VF50 modules. Patches are tested on top of shawn's for-next branch. Changes since v2: 1. Fix pin multiplexing for pins in idle state.

Re: [PATCH v8 3/4] drivers: nvmem: Add Vybrid OCOTP support

Hello, On 15-08-12 11:41:55, Srinivas Kandagatla wrote: > Hi Sanchayan, > > Please run checkpatch before you send the patch next time. > Look at Documentation/SubmittingPatches for more details. > > WARNING: line over 80 characters > #225: FILE: drivers/nvmem/vf610-ocotp.c:174: > +

Re: [PATCH v8 3/4] drivers: nvmem: Add Vybrid OCOTP support

Hello, On 15-08-12 11:41:55, Srinivas Kandagatla wrote: Hi Sanchayan, Please run checkpatch before you send the patch next time. Look at Documentation/SubmittingPatches for more details. WARNING: line over 80 characters #225: FILE: drivers/nvmem/vf610-ocotp.c:174: +

Re: [PATCH v7 3/4] drivers: nvmem: Add Vybrid OCOTP support

Hello, On 15-08-10 10:17:53, Srinivas Kandagatla wrote: > Hi Sanchayan, > > > Could you add Greg to the "to list" so that we can request him to pick > this via his tree. Will add Greg in cc with the next revision. > > > Few nits, other than that driver looks good. > > > On 06/08/15

Re: [PATCH v7 4/4] nvmem: Add DT binding documentation for Vybrid OCOTP driver

Hello, On 15-08-10 10:18:01, Srinivas Kandagatla wrote: > > > On 06/08/15 16:27, Sanchayan Maity wrote: > > Add the devicetree bindings for the Freescale Vybrid On-Chip > > OTP driver. > > > > Signed-off-by: Sanchayan Maity > > --- > > .../devicetree/bindings/nvmem/vf610-ocotp.txt|

  1   2   >