Re: renesas-drivers-2016-08-23-v4.8-rc3

On Thu, Aug 25, 2016 at 6:46 PM, Wolfram Sang wrote: >> > How can we check which ES version we are running? I recall seeing some >> > patch from Geert that printed out useful information during boot, any >> > chance that could make it upstream (if it is not already)? >> >>

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Morimoto-san, On Fri, Sep 2, 2016 at 3:38 AM, Kuninori Morimoto wrote: >> >> Even with my recent patch? >> > >> > I tried your patch, and it solved this issue. >> >> Interesting... >> >> Does "[PATCH/RFT 0/4] ARM: shmobile: R-Car Gen2: Allow booting secondary

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Geert > >> Even with my recent patch? > > > > I tried your patch, and it solved this issue. > > Interesting... > > Does "[PATCH/RFT 0/4] ARM: shmobile: R-Car Gen2: Allow booting secondary CPU > cores in debug mode", without Wolfram's patch, also fix it? Interesting... Your patch (without

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Morimoto-san, On Thu, Sep 1, 2016 at 9:06 AM, Kuninori Morimoto wrote: >> > I can reproduce this on Lager board now. >> > If I OFF:ed on SW8 : 4bit (= MD21), kernel boot will be failed. >> > It happened on both board >> >> Even with my recent patch? > > I

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Wolfram > > I can reproduce this on Lager board now. > > If I OFF:ed on SW8 : 4bit (= MD21), kernel boot will be failed. > > It happened on both board > > Even with my recent patch? I tried your patch, and it solved this issue. Thanks. I will post Tested-by to it Best regards --- Kuninori

Re: renesas-drivers-2016-08-23-v4.8-rc3

> I can reproduce this on Lager board now. > If I OFF:ed on SW8 : 4bit (= MD21), kernel boot will be failed. > It happened on both board Even with my recent patch? signature.asc Description: PGP signature

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Geert, Wolfram > > Magnus has my previous Lager board, so I can't try it today. > > I think my current board and previous board have different type of chip. > > Magnus will bring me my previous board tomorrow, so I will check it, > > and try your solution. > > The revision doesn't seem to be

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Wolfram, On Wed, Aug 31, 2016 at 10:07 AM, Wolfram Sang wrote: > Am I recalling correctly that noone of us has access to DA9063 > documentation? Is this still true? Or do we know the differences of the > revisions? Yes. I had completely forgotten I did apply for

Re: renesas-drivers-2016-08-23-v4.8-rc3

> The revision doesn't seem to be printed on the chip package, but it is > identified by the da9063 driver (CONFIG_REGULATOR_DA9063=y). Am I recalling correctly that noone of us has access to DA9063 documentation? Is this still true? Or do we know the differences of the revisions?

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Morimoto-san, On Wed, Aug 31, 2016 at 8:20 AM, Kuninori Morimoto wrote: >> > I noticed that Lager "ES3.0" board can't boot on this and previous -rc2 >> > branch. >> > In my and Shimoda-san's check, "ES2.0" seems have no problem. >> >> I understand the issue

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Wolfram > > I noticed that Lager "ES3.0" board can't boot on this and previous -rc2 > > branch. > > In my and Shimoda-san's check, "ES2.0" seems have no problem. > > I understand the issue now. It is not about ES3.0 vs. ES2.0, it is about > cold-boot vs. warm-boot. I remembered the DA9xxx

Re: renesas-drivers-2016-08-23-v4.8-rc3

> > How can we check which ES version we are running? I recall seeing some > > patch from Geert that printed out useful information during boot, any > > chance that could make it upstream (if it is not already)? > > It's part of my topic/renesas-debug branch. Just merge that into latest >

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Magnus, On Thu, Aug 25, 2016 at 4:42 AM, Magnus Damm wrote: > On Wed, Aug 24, 2016 at 9:58 AM, Kuninori Morimoto > wrote: >> I noticed that Lager "ES3.0" board can't boot on this and previous -rc2 >> branch. >> In my and Shimoda-san's

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Wolfram > > I tried it, but same result. > > I see. Do we have a list of changes between ES2.0 and 3.0? We checked difference about I2C/IIC/PFC between ES2.0 and ES3.0, but we couldn't find. So, it seems 1) unknown chip something ? 2) board individual difference ? 3) uboot difference ?

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Morimoto-san, everyone, On Wed, Aug 24, 2016 at 9:58 AM, Kuninori Morimoto <kuninori.morimoto...@renesas.com> wrote: > > Hi Geert, Simon, Wolfram > >> I have pushed renesas-drivers-2016-08-23-v4.8-rc3 to >> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-

Re: renesas-drivers-2016-08-23-v4.8-rc3

> I tried it, but same result. I see. Do we have a list of changes between ES2.0 and 3.0? signature.asc Description: PGP signature

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Wolfram Thank you for your feedback > > 09a28bb8b17e8cab3e9c120b7e37f631cc334a8f > > ("ARM: dts: lager: use demuxer for IIC3/I2C3") > > Can you try this patch I sent yesterday? > > [PATCH] i2c: mux: demux-pinctrl: run properly with multiple instances I tried it, but same result.

Re: renesas-drivers-2016-08-23-v4.8-rc3

> > 09a28bb8b17e8cab3e9c120b7e37f631cc334a8f > ("ARM: dts: lager: use demuxer for IIC3/I2C3") Can you try this patch I sent yesterday? [PATCH] i2c: mux: demux-pinctrl: run properly with multiple instances signature.asc Description: PGP signature

Re: renesas-drivers-2016-08-23-v4.8-rc3

Hi Geert, Simon, Wolfram > I have pushed renesas-drivers-2016-08-23-v4.8-rc3 to > https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git > > This tree is meant to ease development of platform support and drivers > for Renesas ARM SoCs. It is created by merging (

renesas-drivers-2016-08-23-v4.8-rc3

I have pushed renesas-drivers-2016-08-23-v4.8-rc3 to https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git This tree is meant to ease development of platform support and drivers for Renesas ARM SoCs. It is created by merging (a) the for-next branches of various subsystem trees