Hello,
On 15-08-08 19:46:00, Jonathan Cameron wrote:
> On 08/08/15 18:22, maitysancha...@gmail.com wrote:
> > Hello Jonathan,
> >
> > On 15-08-08 15:29:47, Jonathan Cameron wrote:
> >> On 05/08/15 13:10, Sanchayan Maity wrote:
> >>> This patch adds support for IIO buffer to the Vybrid ADC
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 maitysancha...@gmail.com
---
.../devicetree/bindings/nvmem/vf610-ocotp.txt
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 16:27, Sanchayan
Hello,
On 15-08-08 19:46:00, Jonathan Cameron wrote:
On 08/08/15 18:22, maitysancha...@gmail.com wrote:
Hello Jonathan,
On 15-08-08 15:29:47, Jonathan Cameron wrote:
On 05/08/15 13:10, Sanchayan Maity wrote:
This patch adds support for IIO buffer to the Vybrid ADC driver.
IIO
Hello Jonathan,
On 15-08-08 15:29:47, Jonathan Cameron wrote:
> On 05/08/15 13:10, 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
Hello Jonathan,
On 15-08-08 15:29:47, Jonathan Cameron wrote:
On 05/08/15 13:10, 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
Hello,
On 15-08-04 03:18:46, Duan Andy wrote:
> From: Sanchayan Maity Sent: Monday, August 03,
> 2015 11:10 PM
> > To: ji...@kernel.org; linux-...@vger.kernel.org
> > Cc: ste...@agner.ch; Duan Fugang-B38611; hof...@osadl.org;
> > sanjeev_sha...@mentor.com; Estevam Fabio-R49496; knaac...@gmx.de;
Hello Dmitry,
On 15-08-03 14:04:09, Dmitry Torokhov wrote:
> Hi Sanchayan,
>
> On Mon, Aug 03, 2015 at 08:55:44PM +0530, maitysancha...@gmail.com wrote:
> > Hello Dmitry,
> >
> > On 15-07-21 10:20:44, Dmitry Torokhov wrote:
> > > Hi Stefan,
> > >
> > > On Tue, Jul 21, 2015 at 04:43:36PM +0200,
Hello Dmitry,
On 15-08-03 14:04:09, Dmitry Torokhov wrote:
Hi Sanchayan,
On Mon, Aug 03, 2015 at 08:55:44PM +0530, maitysancha...@gmail.com wrote:
Hello Dmitry,
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
Hi Stefan,
On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner
Hello,
On 15-08-04 03:18:46, Duan Andy wrote:
From: Sanchayan Maity maitysancha...@gmail.com Sent: Monday, August 03,
2015 11:10 PM
To: ji...@kernel.org; linux-...@vger.kernel.org
Cc: ste...@agner.ch; Duan Fugang-B38611; hof...@osadl.org;
sanjeev_sha...@mentor.com; Estevam Fabio-R49496;
Hello Dmitry,
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
> Hi Stefan,
>
> On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner wrote:
> > Hi Dmitry,
> >
> > As the original author of the driver I have some remarks to your review
> >
> > On 2015-07-18 01:42, Dmitry Torokhov wrote:
> > >> +
Hello Dmitry,
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
Hi Stefan,
On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner wrote:
Hi Dmitry,
As the original author of the driver I have some remarks to your review
On 2015-07-18 01:42, Dmitry Torokhov wrote:
+/*
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
> Hi Stefan,
>
> On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner wrote:
> > Hi Dmitry,
> >
> > As the original author of the driver I have some remarks to your review
> >
> > On 2015-07-18 01:42, Dmitry Torokhov wrote:
> > >> +
On 15-07-21 10:20:44, Dmitry Torokhov wrote:
Hi Stefan,
On Tue, Jul 21, 2015 at 04:43:36PM +0200, Stefan Agner wrote:
Hi Dmitry,
As the original author of the driver I have some remarks to your review
On 2015-07-18 01:42, Dmitry Torokhov wrote:
+/*
+
Hello Dmitry,
On 15-07-17 16:42:42, Dmitry Torokhov wrote:
> Hi Sanchayan,
>
>
> On Thu, Jul 16, 2015 at 08:43:21PM +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
On 15-07-18 14:03:25, Nicolae Rosia wrote:
> Hi,
>
> On Thu, Jul 16, 2015 at 6:13 PM, 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 vf610_adc driver based
On 15-07-18 14:03:25, Nicolae Rosia wrote:
Hi,
On Thu, Jul 16, 2015 at 6:13 PM, Sanchayan Maity
maitysancha...@gmail.com 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 vf610_adc
Hello Dmitry,
On 15-07-17 16:42:42, Dmitry Torokhov wrote:
Hi Sanchayan,
On Thu, Jul 16, 2015 at 08:43:21PM +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
Hello Jonathan,
On 15-07-11 18:39:10, Jonathan Cameron wrote:
> On 10/07/15 19:06, maitysancha...@gmail.com wrote:
> > Hello Shawn,
> >
> > On 15-07-10 16:53:24, Shawn Guo wrote:
> >> On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
> >>> Add a device tree property which allows
Hello Jonathan,
On 15-07-11 18:39:10, Jonathan Cameron wrote:
On 10/07/15 19:06, maitysancha...@gmail.com wrote:
Hello Shawn,
On 15-07-10 16:53:24, Shawn Guo wrote:
On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
Add a device tree property which allows to specify the
Hello Stefan,
On 15-07-08 22:55:23, Stefan Wahren wrote:
> Hi Sanchayan,
>
> > maitysancha...@gmail.com hat am 8. Juli 2015 um 07:39 geschrieben:
> >
> >
> > [...]
> > > > >
> > > > > Looking at valid_fuse_addr shows me 0x3F as last valid register. So
> > > > > the
> > > > > rest
> > > > > of
Hello Shawn,
On 15-07-10 16:53:24, Shawn Guo wrote:
> On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
> > Add a device tree property which allows to specify the minimum sample
> > time which can be used to calculate the actual ADC cycles required
> > depending on the hardware.
>
Hello Shawn,
On 15-07-10 16:47:04, Shawn Guo wrote:
> On Wed, Jun 24, 2015 at 02:03:39PM +0530, Sanchayan Maity wrote:
> > Hello,
> >
> > This patchset adds a dt binding for specifying sample time
> > for the vybrid adc driver and takes this into account for
> > sampling frequency calculation
Hello Shawn,
On 15-07-10 16:47:04, Shawn Guo wrote:
On Wed, Jun 24, 2015 at 02:03:39PM +0530, Sanchayan Maity wrote:
Hello,
This patchset adds a dt binding for specifying sample time
for the vybrid adc driver and takes this into account for
sampling frequency calculation and related
Hello Shawn,
On 15-07-10 16:53:24, Shawn Guo wrote:
On Wed, Jun 24, 2015 at 02:03:41PM +0530, Sanchayan Maity wrote:
Add a device tree property which allows to specify the minimum sample
time which can be used to calculate the actual ADC cycles required
depending on the hardware.
Hello Stefan,
On 15-07-08 22:55:23, Stefan Wahren wrote:
Hi Sanchayan,
maitysancha...@gmail.com hat am 8. Juli 2015 um 07:39 geschrieben:
[...]
Looking at valid_fuse_addr shows me 0x3F as last valid register. So
the
rest
of the buffer ( 0xD00 -
Hi Stefan,
On 15-07-07 14:49:06, Stefan Wahren wrote:
> Hi Sanchayan,
>
> > maitysancha...@gmail.com hat am 7. Juli 2015 um 07:19 geschrieben:
> >
> >
> > [...]
> > > > diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> > > > index 17f1a57..84c830d 100644
> > > > ---
Hi Stefan,
On 15-07-07 14:49:06, Stefan Wahren wrote:
Hi Sanchayan,
maitysancha...@gmail.com hat am 7. Juli 2015 um 07:19 geschrieben:
[...]
diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index 17f1a57..84c830d 100644
--- a/drivers/nvmem/Kconfig
+++
Hello Stefan,
On 15-07-06 12:16:34, Stefan Wahren wrote:
> Hi Sanchayan,
>
> > Sanchayan Maity hat am 29. Juni 2015 um 13:22
> > geschrieben:
> >
> >
> > The patch adds support for the On Chip One Time Programmable Peripheral
> > (OCOTP) on the Vybrid platform.
>
> please provide a changelog
Hello Stefan,
On 15-07-06 12:16:34, Stefan Wahren wrote:
Hi Sanchayan,
Sanchayan Maity maitysancha...@gmail.com hat am 29. Juni 2015 um 13:22
geschrieben:
The patch adds support for the On Chip One Time Programmable Peripheral
(OCOTP) on the Vybrid platform.
please provide a
Hello Stefan,
On 15-06-24 13:52:28, Stefan Wahren wrote:
> Hi Srinivas,
>
> Am 24.06.2015 um 12:45 schrieb maitysancha...@gmail.com:
> > Hello Stefan,
> >
> > On 15-06-24 11:56:14, Stefan Wahren wrote:
> >> Hi Sanchayan,
> >>
> >> Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
> >>> On
Hello Stefan,
On 15-06-24 11:56:14, Stefan Wahren wrote:
> Hi Sanchayan,
>
> Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
> > On 15-06-23 21:31:41, Stefan Wahren wrote:
> >> Hi Sanchayan,
> >>
> >>> Sanchayan Maity hat am 23. Juni 2015 um 15:44
> >>> geschrieben:
> >>>
> >>>
> >>>
Hello Stefan,
On 15-06-24 11:56:14, Stefan Wahren wrote:
Hi Sanchayan,
Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
On 15-06-23 21:31:41, Stefan Wahren wrote:
Hi Sanchayan,
Sanchayan Maity maitysancha...@gmail.com hat am 23. Juni 2015 um 15:44
geschrieben:
The
Hello Stefan,
On 15-06-24 13:52:28, Stefan Wahren wrote:
Hi Srinivas,
Am 24.06.2015 um 12:45 schrieb maitysancha...@gmail.com:
Hello Stefan,
On 15-06-24 11:56:14, Stefan Wahren wrote:
Hi Sanchayan,
Am 24.06.2015 um 07:19 schrieb maitysancha...@gmail.com:
On 15-06-23 21:31:41,
Hello Srinivas,
On 15-06-23 20:03:31, Srinivas Kandagatla wrote:
> Hi Sanchayan,
>
>
> On 23/06/15 14:44, Sanchayan Maity wrote:
> >The patch adds support for the On Chip One Time Programmable Peripheral
> >(OCOTP) and On Chip ROM (OCROM) support.
> >
> >On Vybrid OCOTP contain data like SoC
On 15-06-23 21:31:41, Stefan Wahren wrote:
> Hi Sanchayan,
>
> > Sanchayan Maity hat am 23. Juni 2015 um 15:44
> > geschrieben:
> >
> >
> > The patch adds support for the On Chip One Time Programmable Peripheral
> > (OCOTP) and On Chip ROM (OCROM) support.
> >
> > On Vybrid OCOTP contain data
Hello Srinivas,
On 15-06-23 20:03:31, Srinivas Kandagatla wrote:
Hi Sanchayan,
On 23/06/15 14:44, Sanchayan Maity wrote:
The patch adds support for the On Chip One Time Programmable Peripheral
(OCOTP) and On Chip ROM (OCROM) support.
On Vybrid OCOTP contain data like SoC ID, MAC
On 15-06-23 21:31:41, Stefan Wahren wrote:
Hi Sanchayan,
Sanchayan Maity maitysancha...@gmail.com hat am 23. Juni 2015 um 15:44
geschrieben:
The patch adds support for the On Chip One Time Programmable Peripheral
(OCOTP) and On Chip ROM (OCROM) support.
On Vybrid OCOTP contain
Hello Srinivas,
On 15-05-21 17:44:12, Srinivas Kandagatla wrote:
> This patch adds bindings for simple nvmem framework which allows nvmem
> consumers to talk to nvmem providers to get access to nvmem cell data.
>
> Signed-off-by: Maxime Ripard
> [Maxime Ripard: intial version of eeprom
Hello Srinivas,
On 15-05-21 17:44:12, Srinivas Kandagatla wrote:
This patch adds bindings for simple nvmem framework which allows nvmem
consumers to talk to nvmem providers to get access to nvmem cell data.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
[Maxime Ripard: intial
Hello,
On 15-06-14 12:16:07, Jonathan Cameron wrote:
> On 08/06/15 18:51, Rob Herring wrote:
> > On Mon, Jun 8, 2015 at 12:42 AM, Sanchayan Maity
> > wrote:
> >> The driver currently does not take into account the minimum sample time
> >> as per the Figure 6-8 Chapter 9.1.1 12-bit ADC electrical
Hello,
On 15-06-14 12:16:07, Jonathan Cameron wrote:
On 08/06/15 18:51, Rob Herring wrote:
On Mon, Jun 8, 2015 at 12:42 AM, Sanchayan Maity
maitysancha...@gmail.com wrote:
The driver currently does not take into account the minimum sample time
as per the Figure 6-8 Chapter 9.1.1 12-bit
Hello Paul,
On 15-06-06 12:26:07, Paul Bolle wrote:
> On Fri, 2015-06-05 at 14:52 +0530, Sanchayan Maity wrote:
> > --- /dev/null
> > +++ b/drivers/soc/fsl/Kconfig
>
> > +config SOC_BUS_VF610
> > + tristate "SoC bus device for the Freescale Vybrid platform"
> > + depends on SOC_VF610
>
Hello Maxime,
On 15-06-06 13:58:33, Maxime Ripard wrote:
> Hi,
>
> On Fri, Jun 05, 2015 at 02:52:37PM +0530, Sanchayan Maity wrote:
> > Add a device tree node for the On-Chip One Time Programmable
> > Controller (OCOTP) and the On-Chip ROM.
> >
> > Signed-off-by: Sanchayan Maity
> > ---
> >
Hello Paul,
On 15-06-06 12:26:07, Paul Bolle wrote:
On Fri, 2015-06-05 at 14:52 +0530, Sanchayan Maity wrote:
--- /dev/null
+++ b/drivers/soc/fsl/Kconfig
+config SOC_BUS_VF610
+ tristate SoC bus device for the Freescale Vybrid platform
+ depends on SOC_VF610
+ select
Hello Maxime,
On 15-06-06 13:58:33, Maxime Ripard wrote:
Hi,
On Fri, Jun 05, 2015 at 02:52:37PM +0530, Sanchayan Maity wrote:
Add a device tree node for the On-Chip One Time Programmable
Controller (OCOTP) and the On-Chip ROM.
Signed-off-by: Sanchayan Maity maitysancha...@gmail.com
Hello,
On 15-05-27 09:31:50, Paul Bolle wrote:
> On Tue, 2015-05-26 at 17:06 +0530, Sanchayan Maity wrote:
> > --- /dev/null
> > +++ b/drivers/soc/fsl/Kconfig
>
> > +config SOC_VF610
> > + bool "SoC bus device for the Freescale Vybrid platform"
> > + select SOC_BUS
> > + help
> >
Hello,
On 15-05-27 09:31:50, Paul Bolle wrote:
On Tue, 2015-05-26 at 17:06 +0530, Sanchayan Maity wrote:
--- /dev/null
+++ b/drivers/soc/fsl/Kconfig
+config SOC_VF610
+ bool SoC bus device for the Freescale Vybrid platform
+ select SOC_BUS
+ help
+Include
Hello Arnd,
On 15-05-22 15:20:00, Arnd Bergmann wrote:
> On Friday 22 May 2015 14:02:52 Stefan Agner wrote:
> > > Can you use syscon_regmap_lookup_by_phandle instead, and put the
> > > phandles in the fsl,vf610-mscm-cpucfg node?
> >
> > Hm, with that we would wire up hardware modules which does
Hello Arnd,
On 15-05-22 15:20:00, Arnd Bergmann wrote:
On Friday 22 May 2015 14:02:52 Stefan Agner wrote:
Can you use syscon_regmap_lookup_by_phandle instead, and put the
phandles in the fsl,vf610-mscm-cpucfg node?
Hm, with that we would wire up hardware modules which does nothing has
Hello Arnd,
On 15-05-22 13:11:46, Arnd Bergmann wrote:
> On Friday 22 May 2015 16:21:54 Sanchayan Maity wrote:
> > +#define OCOTP_CFG0_OFFSET 0x0410
> > +#define OCOTP_CFG1_OFFSET 0x0420
> > +#define MSCM_CPxCOUNT_OFFSET 0x002C
> > +#define MSCM_CPxCFG1_OFFSET
Hello Arnd,
On 15-05-22 13:11:46, Arnd Bergmann wrote:
On Friday 22 May 2015 16:21:54 Sanchayan Maity wrote:
+#define OCOTP_CFG0_OFFSET 0x0410
+#define OCOTP_CFG1_OFFSET 0x0420
+#define MSCM_CPxCOUNT_OFFSET 0x002C
+#define MSCM_CPxCFG1_OFFSET0x0014
Hello Shawn,
On 15-05-19 14:24:13, Shawn Guo wrote:
> On Mon, May 18, 2015 at 11:50:07AM +0530, Sanchayan Maity wrote:
> > Implements SoC bus support to export SoC specific information. Read
> > the unique SoC ID from the Vybrid On Chip One Time Programmable
> > (OCOTP) controller, SoC specific
Hello Shawn,
On 15-05-19 14:24:13, Shawn Guo wrote:
On Mon, May 18, 2015 at 11:50:07AM +0530, Sanchayan Maity wrote:
Implements SoC bus support to export SoC specific information. Read
the unique SoC ID from the Vybrid On Chip One Time Programmable
(OCOTP) controller, SoC specific
Hello,
Ping? Any inputs?
On 15-05-11 10:41:37, Sanchayan Maity wrote:
> Hello,
>
> Currently this patchset is based of on our local branch but would like
> some comments before I push this to mainline through Shawn's tree.
>
> This patchset implements the following
>
Hello,
Ping? Any inputs?
On 15-05-11 10:41:37, Sanchayan Maity wrote:
Hello,
Currently this patchset is based of on our local branch but would like
some comments before I push this to mainline through Shawn's tree.
This patchset implements the following
101 - 156 of 156 matches
Mail list logo
