00:35 <DavidHeidelberg> approx. 200 lines of warnings from 8900 done, now 8700 remaining :D

00:37 <DavidHeidelberg> 5hrs / 200 lines, so let's assume it's one month of 8hr per day fixing

00:37 <DavidHeidelberg> *4hrs

00:37 <DavidHeidelberg> well, 27 days.

00:39 <DavidHeidelberg> after 27 days, we should get rid of all warnings. 2 humans could do it in 13 days, 3 people 9 days...

08:48 <maxim[m]> David Heidelberg: Hi, the `nvidia,only-1-8-v` in the tegra-sdhci binding isn't actually parsed by the driver

09:00 <DavidHeidelberg> maxim thanks for looking into MR! I did noticed that, but I assume maybe in future will be or I guess I'll drop it ;-)

09:26 <maxim[m]> A `only-1-8-v` property does exist downstream though: https://github.com/LineageOS/android_kernel_nvidia_linux-4.9_kernel_kernel-4.9/commit/90ecea32c5dbedc98fb8f256d42c22754ebf8efb Not sure if this will ever be added

12:15 <DavidHeidelberg> thx maxim , I reused it for no-1-8-v flag :)

13:02 <maxim[m]> David Heidelberg: I would suggest to remove it in a separate commit before the yaml conversion and add a Fixes: tag maybe, because it seems to have slipped in by mistake

13:03 <DavidHeidelberg> could do, anyway not sure about it's importance

17:27 <DavidHeidelberg> new goal, only 4400 warnings.

20:37 <digetx> DavidHeidelberg: please don't send it to grate if it's unrelated to tegra

20:38 <DavidHeidelberg> well, everything which is connected to the DTS files

20:38 <DavidHeidelberg> so it's and it's not related. When you compile tegra_defconfig dts, it firing up

20:40 <digetx> you may send it if it's about tegra dts

20:42 <DavidHeidelberg> got from 8000 to 4000 warnings lines for `make dtbs_check` on tegra_defconfig

20:43 <DavidHeidelberg> but it's about 40 commits, approx 15 should be FIXUPs for grate commits, rest of for upstream

20:43 <jenneron[m]> do we really need to do that with tegra_defconfig? grate_defconfig should cover grate needs

20:44 <jenneron[m]> oh, it's dts related, so it will be same

20:44 <DavidHeidelberg> well, I guess on grate_defconfig less HW gets builds, so less warnings

20:44 <DavidHeidelberg> *HW -> drivers

20:44 <DavidHeidelberg> and not all tegra1xx and tegra2xx, only tegra20,30,114, right?

20:44 <jenneron[m]> yes

20:45 <digetx> send it and I'll take a look, after we'll decide what to do next with it

20:45 <DavidHeidelberg> kk, currently it has far from perfect, but yamllint and dt-doc-checker passes on everything

20:46 <DavidHeidelberg> digetx goal is enable `make dtbs_check` == 0 warnings for CI, so new issues with DT gets discovered earlier

20:46 <DavidHeidelberg> since when new warning appear now, no-one (even me) won't look into ~8000 lines..

20:50 <DavidHeidelberg> currently we're on ~3800 lines of warnings.. if anyone here is bored and don't know how spend some quality time, there is lot of device-tree/bindings in .txt format which needs to be converted to YAML :D

20:50 <DavidHeidelberg> digetx maybe I could send you fixups for tegra maintained commits?

20:51 <DavidHeidelberg> would u have moment to look at them?

20:52 <digetx> yes

21:45 <DavidHeidelberg> it's here: https://github.com/grate-driver/linux/pull/74 hopefully there isn't anything which isn't currently only in grate

22:36 <jenneron[m]> https://github.com/grate-driver/linux/pull/74/commits/fe0bfd143dcc597d802b118c9a2c64e391b005c3 wtf is regulator@103 why i didn't know about that

22:37 <jenneron[m]> nevermind, i should add a fixup commit for this dts

22:41 <jenneron[m]> David Heidelberg: btw i know that usually regulators and pinctrl are placed at the bottom in device-trees, but do you know where it is documented? as well as alphabetical order for label reference

22:41 <jenneron[m]> i couldn't find that

22:42 <DavidHeidelberg> Not sure either