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
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 correctly
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 dspi_tran
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 in
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 MOSI
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 variabl
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.
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 internal
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
> arch/arm/boot
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 i
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 branc
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: Sanchay
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
> arch/arm/boot
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 inver
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
>
> ...
>
> > > > > >
> > > > > > Ou
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
> > >
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 th
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 removin
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 the
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: phand
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 SoC's.
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 S
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
> > ++
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>;
> > +
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
all
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
> > ---
> > arch/arm/boot/dt
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
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 ol
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
> > ---
> >
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
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
>
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
>
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 4.2.0-rc
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
> > ---
> > ar
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
> > ---
> > .../devicetree/bindings
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 timin
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 window,
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 w
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
> patchs
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 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
> > +++
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;
> > + struc
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.
> >
> >
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 inser
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 t
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 touch
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 pr
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.
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:
> +
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,
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| 20
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.
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 pr
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-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 rel
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
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
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 th
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 and
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/Kco
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 in
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:
> >>>
> >>>
> >>> Th
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,
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 lik
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 framework
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 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
> > ---
> > ar
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 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 n
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 in
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
> https://www.kernel.org/do
78 matches
Mail list logo
