On Wed, 2017-08-16 at 18:33 +0300, Leonard Crestez wrote:
> On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote:
> >
> > On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> > >
> > > On 08/08/17 12:38, Leonard Crestez wrote:
> > > >
> > > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas
On Wed, 2017-08-16 at 18:33 +0300, Leonard Crestez wrote:
> On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote:
> >
> > On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> > >
> > > On 08/08/17 12:38, Leonard Crestez wrote:
> > > >
> > > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas
On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote:
> On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> > On 08/08/17 12:38, Leonard Crestez wrote:
> > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> > > > On 08/08/17 08:21, Zhang Rui wrote:
> > > > > I'm okay with
On Tue, 2017-08-08 at 20:58 +0800, Zhang Rui wrote:
> On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> > On 08/08/17 12:38, Leonard Crestez wrote:
> > > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> > > > On 08/08/17 08:21, Zhang Rui wrote:
> > > > > I'm okay with
On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> >
>
> On 08/08/17 12:38, Leonard Crestez wrote:
> >
> > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> > >
> > > On 08/08/17 08:21, Zhang Rui wrote:
> > > >
> > > > On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo
On Tue, 2017-08-08 at 12:44 +0100, Srinivas Kandagatla wrote:
> >
>
> On 08/08/17 12:38, Leonard Crestez wrote:
> >
> > On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> > >
> > > On 08/08/17 08:21, Zhang Rui wrote:
> > > >
> > > > On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo
On 08/08/17 12:38, Leonard Crestez wrote:
On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
On 08/08/17 08:21, Zhang Rui wrote:
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
On newer imx SOCs accessing
On 08/08/17 12:38, Leonard Crestez wrote:
On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
On 08/08/17 08:21, Zhang Rui wrote:
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
On newer imx SOCs accessing
On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> On 08/08/17 08:21, Zhang Rui wrote:
> > On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
> > > On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> > > > On newer imx SOCs accessing OCOTP directly is wrong because
On Tue, 2017-08-08 at 12:00 +0100, Srinivas Kandagatla wrote:
> On 08/08/17 08:21, Zhang Rui wrote:
> > On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
> > > On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> > > > On newer imx SOCs accessing OCOTP directly is wrong because
On 08/08/17 08:21, Zhang Rui wrote:
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
On newer imx SOCs accessing OCOTP directly is wrong because the
ocotp clock
needs to be enabled first. Add support for reading those same
On 08/08/17 08:21, Zhang Rui wrote:
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
On newer imx SOCs accessing OCOTP directly is wrong because the
ocotp clock
needs to be enabled first. Add support for reading those same
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
> On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> >
> > On newer imx SOCs accessing OCOTP directly is wrong because the
> > ocotp clock
> > needs to be enabled first. Add support for reading those same
> > values through
> >
On Tue, 2017-07-25 at 16:08 +0800, Shawn Guo wrote:
> On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> >
> > On newer imx SOCs accessing OCOTP directly is wrong because the
> > ocotp clock
> > needs to be enabled first. Add support for reading those same
> > values through
> >
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
> needs to be enabled first. Add support for reading those same values through
> the nvmem API instead.
>
> The older path is preserved for compatibility
On Fri, Jul 14, 2017 at 05:11:08PM +0300, Leonard Crestez wrote:
> On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
> needs to be enabled first. Add support for reading those same values through
> the nvmem API instead.
>
> The older path is preserved for compatibility
On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
needs to be enabled first. Add support for reading those same values through
the nvmem API instead.
The older path is preserved for compatibility with older dts and because it
works correctly on imx6qdl chips.
On newer imx SOCs accessing OCOTP directly is wrong because the ocotp clock
needs to be enabled first. Add support for reading those same values through
the nvmem API instead.
The older path is preserved for compatibility with older dts and because it
works correctly on imx6qdl chips.
18 matches
Mail list logo