Hi Morimoto-san,
On Wed, Aug 31, 2016 at 8:20 AM, Kuninori Morimoto
<kuninori.morimoto.gx@xxxxxxxxxxx> 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 now. It is not about ES3.0 vs. ES2.0, it is about
>> cold-boot vs. warm-boot. I remembered the DA9xxx interrupt storm
>> problems we had, and voila, I could reproduce the lockup on ES2.0 here,
>> but you need to cold-boot and have the da9xxx drivers enabled.
>
> It seems lager board has 2 type of DA9xxx chip, type A, and type B.
> We don't know which chip your / my board has.
>
> My *current* Lager board has no issue on cold / warm boot.
> 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 printed on the chip package, but it is
identified by the da9063 driver (CONFIG_REGULATOR_DA9063=y).
My Koelsch has:
da9063 6-0058: Device detected (chip-ID: 0x61, var-ID: 0x30)
which corresponds to PMIC_DA9063_AD.
Magnus' Lager (remote access) has the same version.
(after adding the missing pieces to DT) Magnus's Gose has:
da9063 6-0058: Device detected (chip-ID: 0x61, var-ID: 0x50)
which corresponds to PMIC_DA9063_BB.
Which revision do you have?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
