01:19 <Danct12> https://patchwork.kernel.org/project/linux-arm-msm/list/?series=747222

01:20 <Danct12> this should now be properly ready for series now

01:21 <Danct12> commits are now in proper order, dual licensed and pretty much it

05:08 <junari> Hi guys

05:08 <junari> I am trying to make a port for my leeco c103 on the msm8976. As a start, I use developments with leeco s2 in the kiciuk repository. Android kernel source code of the c103 was finded here https://github.com/ampir-nn/android_kernel_leeco_msm8976-9.x/tree/master. First I changed the nodes of the regulator. Then I finded which the panel to be used in the cmdline. With linux-mdss-dsi-panel-driver-generator generated panel's driver. Then I finded proper blsp

05:08 <junari> for type c connector (fusb302). I tried to describe it correctly in the device tree. But, when I load generated pmos firmware I get ripples and lines on the screen and nothing in usb. Can anyone suggest what else I can do?

05:09 <junari> here my DT https://gist.github.com/iuncuim/bd3b986e7a70307f08569b81d4599263

05:12 <Danct12> junari: hey, i would recommend start with basic hardware functionality first

05:13 <Danct12> use simplefb for now

05:18 <junari> What should I do for this? Its about framebuffer in device tree?

09:08 <krzk> Danct12: I don't know the context you are asking for. I have like 100 patches each day in my inbox, so no clue to what you are referring.

09:09 <krzk> Danct12: but general rule is each logical change to existing source is done in separate patch. Adding new code - like new driver, new board, new DTS - is considered one logical change.

09:41 <aka_[m]> <junari> "What should I do for this? Its..." <- if you get some corruption on screen then maybe you get some ramoops

09:41 <aka_[m]> i would try rebooting to recovery by holding vol+ +power

09:41 <aka_[m]> then look for console-ramoops

09:42 <aka_[m]> there is chance everything almost probe besides panel

09:42 <aka_[m]> do you have usb working by any chance?

09:43 <aka_[m]> also if you are not using some custom lk2nd which i only have built you need to limit cpus during boot to 4

09:43 <aka_[m]> best would be bringing them all up tho

09:44 <aka_[m]> otherwise its goint to take a while

09:45 <aka_[m]> im overwhelmingly depressed lately and i doubt im going to do anything with its mainline state

10:24 <junari> aka_: my usb don't working, I think it because fusb302 not correct described in dts. I don't use lk2nd yet. I will look to console-ramoops, thanks. Did you try run simple-fb? I cannot find memory region for it. In your case panel-generator generate correct driver?

10:25 <aka_[m]> junari: if you had lk2nd working it would say you where region is

10:25 <aka_[m]> if its not anywhere in dts you can assume its platform defaults

10:25 <aka_[m]> or maybe bootloader does not initalize fb at boot like sony loire does

11:51 <aka_[m]> how bad would be adding detection function to some panel driver to read cmdline and then match proper pdata?

11:51 <aka_[m]> by default some drivers like nt36672 ones have compatible where it matches to just singular pdata, what about adding additional table where you set compatible to execute function on array of pdatas.