[Letux-kernel] [PATCH 00/20] A bunch of JZ4730 fixups for letux-kernel

[H. Nikolaus Schaller]

> Am 26.12.2020 um 17:38 schrieb Paul Boddie <paul at boddie.org.uk>:
> 
> I did wonder whether the transmission of the last byte might need to be 
> accompanied by the stop condition,

Yes, it should or well, the STOP must come after the last byte. There is code in my irq handler.

But it now works with interrupts always enabled. So it looks as if I have found the
right triggers to end an interrupt request...

So I think I will have some more minor changes and then merge it into letux-5.10.3 for
more public testing. This will become available on the goldelico git soon.

What is still strange is the system time. First of all, "date" now runs much slower
than real time. I think this has changed after I hot the LCD create some /dev/fb0
and X11 running. Needs more time to verify this assumed dependency.

And there are really strange values printed to dmesg. The sequence is correct, but the
time jumps back and forth?

Well, it may be as simple as the time_val tv_usec having random and negative values...

[    0.000000] clocksource: ingenic-timer: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 506303385 ns
[    0.001770] sched_clock: 16 bits at 57kHz, resolution 17361ns, wraps every 568880208ns
[    0.306666] Console: colour dummy device 80x25
[    0.577725] printk: console [tty0] enabled
[    0.710937] Calibrating delay loop... 1254.19 BogoMIPS (lpj=6270976)
[    1.354097] pid_max: default: 32768 minimum: 301
[    1.523229] LSM: Security Framework initializing
[    1.681666] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.778298] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    1.345295] rcu: Hierarchical SRCU implementation.
[    1.583229] devtmpfs: initialized
[    1.298784] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    1.612135] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.974565] pinctrl core: initialized pinctrl subsystem
[    1.267482] regulator-dummy: no parameters, enabled
[    1.560607] NET: Registered protocol family 16
[    0.976944] thermal_sys: Registered thermal governor 'fair_share'
[    0.978888] thermal_sys: Registered thermal governor 'step_wise'
[    1.296545] thermal_sys: Registered thermal governor 'user_space'
[    1.355902] jz4780-dma 13020000.dma: JZ4780 DMA controller initialised

...

[    6.920677] hid-generic 0003:0A81:0205.0002: input: USB HID v1.10 Mouse [CHESEN PS2 to USB Converter] on usb-13030000.uhc-2.3/input1
[    6.731788] usb 1-2.4: new full-speed USB device number 4 using ohci-platform
[    7.113437] usb 1-2.4: New USB device found, idVendor=0ace, idProduct=1215, bcdDevice=48.10
[    7.115642] usb 1-2.4: New USB device strings: Mfr=16, Product=32, SerialNumber=0
[    7.084392] usb 1-2.4: Product: USB2.0 WLAN
[    6.956284] usb 1-2.4: Manufacturer: ZyDAS
[    7.942569] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.158385] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.273263] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    7.375590] cfg80211: failed to load regulatory.db

I am not at all sure but it may have started with the latest TCU/CGU update?

BR,
Nikolaus

PS: I just found that after removing all my printk() the i2c driver starts to fail.
I need one printing the state and the status register :(
So there is another timing issue to be fixed before publishing it...