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 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 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 - sizeof(valid_fuse_addr) ) in case of raw access
> > > > could be
> >
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 - sizeof(valid_fuse_addr) ) in case of raw access
could be
uninitializied.
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 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
> > > +++ b/drivers/nvmem/Kconfig
> > > @@ -33,4 +33,14 @@ config
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
+++ b/drivers/nvmem/Kconfig
@@ -33,4 +33,14 @@ config NVMEM_SUNXI_SID
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
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 your cover letter and a new version after changes.
I think it's important
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 changelog in your cover letter and a new version after changes.
I
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
The patch adds support for the On Chip One Time Programmable Peripheral
(OCOTP) on the Vybrid platform.
Signed-off-by: Sanchayan Maity
---
drivers/nvmem/Kconfig | 10 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/vf610-ocotp.c | 250
3
The patch adds support for the On Chip One Time Programmable Peripheral
(OCOTP) on the Vybrid platform.
Signed-off-by: Sanchayan Maity maitysancha...@gmail.com
---
drivers/nvmem/Kconfig | 10 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/vf610-ocotp.c | 250
14 matches
Mail list logo