00:21
<
sjg1 >
marex: Yes you can cast. That is common
00:22
<
sjg1 >
marex: Re pointers, I mean that EFI code uses a u64 to hold a pointer and (I think) a void * to hold an address. But it is a long time since I looked at it
00:22
<
marex >
sjg1: ignore those two patches for now
00:23
<
marex >
sjg1: I think you will have to revisit it soon due to the binman EFI capsule stuff, no ?
00:24
<
sjg1 >
marex: I think it is separate, for now.
00:28
<
marex >
sjg1: well, I finally misused CI to spit out .img files for the remaining 7 or so tests
00:30
<
sjg1 >
marex: So your local setup can't do that?
00:32
<
marex >
sjg1: it was easier to spent 10 seconds on having CI do it
00:34
<
marex >
sjg1: frankly, I would expect userspace tool test suite to not spam host system with sudo ...
00:43
<
sjg1 >
marex: Perhaps you can fix it? It annoys me too. I remember when I had to sudo to write to a USB stick, but now that has been fixed
00:44
<
marex >
sjg1: perhaps I can add it as another entry on the todo ?
00:44
persmule has quit [Remote host closed the connection]
00:48
mmu_man has quit [Ping timeout: 245 seconds]
00:49
<
marex >
sjg1: perhaps we need a public todo for the project
00:54
<
marex >
aha ... so ... another bug fixed
00:57
<
marex >
sjg1: is that Tartarus only thing ?
00:57
<
sjg1 >
No, but there is one for each custodian, I believe
01:09
persmule has joined #u-boot
01:14
___nick___ has joined #u-boot
01:14
___nick___ has quit [Client Quit]
01:16
___nick___ has joined #u-boot
01:21
vagrantc has joined #u-boot
01:25
persmule has quit [Remote host closed the connection]
01:27
persmule has joined #u-boot
01:27
pgreco has quit [Remote host closed the connection]
01:27
pgreco has joined #u-boot
02:15
alpernebbi has quit [Ping timeout: 248 seconds]
02:19
alpernebbi has joined #u-boot
02:23
camus has joined #u-boot
02:45
pbsds has joined #u-boot
02:47
swiftgeek has quit [Ping timeout: 246 seconds]
03:05
vagrantc has quit [Quit: leaving]
03:10
redbrain has quit [Read error: Connection reset by peer]
03:16
redbrain has joined #u-boot
03:59
swiftgeek has joined #u-boot
04:12
sng has joined #u-boot
04:12
sng has quit [Remote host closed the connection]
04:12
sng has joined #u-boot
04:24
Clamor has joined #u-boot
04:27
Wouter0100670440 has joined #u-boot
04:38
naoki has joined #u-boot
04:42
gsz has joined #u-boot
05:04
devarsh has joined #u-boot
05:10
dormito has quit [Ping timeout: 240 seconds]
05:15
goliath has joined #u-boot
05:20
sng has quit [Remote host closed the connection]
05:21
sng has joined #u-boot
05:46
dormito has joined #u-boot
05:49
sng has quit [Read error: Connection reset by peer]
06:20
stefanro has joined #u-boot
06:38
sng has joined #u-boot
06:59
sng has quit [Remote host closed the connection]
07:01
sng has joined #u-boot
07:02
ezulian has joined #u-boot
07:08
frieder has joined #u-boot
07:42
ikarso has joined #u-boot
07:51
sszy has joined #u-boot
09:00
naoki has quit [Quit: naoki]
09:05
sng has quit [Remote host closed the connection]
09:12
Wouter0100670440 has joined #u-boot
09:39
sng has joined #u-boot
10:31
Clamor has quit [Ping timeout: 248 seconds]
10:31
Clamor has joined #u-boot
10:32
<
mps >
do anyone here use starfive visionfive v2 with mainline kernel and mainline u-boot? For me mainline kernel doesn't work with mainline u-boot, while it works fine with starfive u-boot
10:35
frieder has quit [Read error: Connection reset by peer]
10:42
vigneshr has quit [Quit: Connection closed for inactivity]
10:43
frieder has joined #u-boot
11:11
camus has quit [Ping timeout: 256 seconds]
11:12
camus has joined #u-boot
11:16
Brainzman has joined #u-boot
11:25
sng has quit [Remote host closed the connection]
11:35
prabhakarlad has quit [Quit: Client closed]
11:40
<
marex >
Clamor: what is that ?
11:41
<
marex >
Clamor: I see ton of ads and other goo
11:43
<
Clamor >
This is a log from uboot I took. I will switch paste service if this is crowded
11:44
<
marex >
paste.debian.net seems to work well, and no ads
11:45
<
Clamor >
I have inserted logs in pmic, regualtors and i2c probes to track calls
11:47
<
marex >
ahh, lemme check the driver in mainline U-Boot source tree, since I assume that's what you're using (there is no version information in the incomplete log)
11:47
<
marex >
$ git grep max77663_sd_probe | wc -l
11:47
<
Clamor >
It is not merged yet
11:48
<
Clamor >
Last 4 commits
11:49
mmu_man has joined #u-boot
11:49
<
Clamor >
Though they are fairly simple and should not fail
11:50
<
Clamor >
I am using the latest mainline u-boot with those patches on top
11:51
<
marex >
if you need drivers to be probed after bind, there is a PROBE_AFTER_BIND DM flag for it
11:51
<
Clamor >
No it is not included
11:51
<
marex >
dont use the post bind hack
11:52
<
Clamor >
I am not, though it fixes situation
11:53
<
Clamor >
I am aware of probe_after_bind flag
11:53
<
marex >
yep, just yesterday I spent like 5 hours debugging memory leak caused by such misuse
11:54
<
Clamor >
I am testing commits from pmic-uclass-new with just max77663 drivers
11:55
<
marex >
Clamor: and probe of some of the driver is called twice, right ?
11:56
<
Clamor >
Yes, regulator drivers as you can see
11:57
<
Clamor >
First time regulator drivers probe is called it triggers all chain of probes, but not the second time
11:57
<
marex >
Clamor: do you know dm_dump_tree() ?
11:58
<
marex >
might give you an idea about the state of DM tree before/after the probe
11:58
<
marex >
maybe some things are not probed because they are already probed
11:59
<
Clamor >
dm tree? Yes I have it
11:59
<
marex >
Clamor: also, try and add dummy .remove and .unbind calls to your drivers, could it be those are called ?
11:59
<
marex >
Clamor: maybe the driver is unbound at some point too, and then reprobed
12:00
<
Clamor >
It feels like i2c is unbound but uboot assumes it is still there
12:00
<
Clamor >
Good advice, thanks
12:04
<
marex >
Clamor: if I wasn't fighting with similar stuff a few hours ago ... oh well
12:04
<
marex >
Clamor: you can spam the code with dm_dump_tree() to check the state of the DM (and what is probed and not probed)
12:04
<
marex >
there is this [+] in the listing if device is probed , [ ] otherwise
12:05
<
Clamor >
Yes, I know how tree works
12:07
<
marex >
Clamor: you can also always just add printf()s to DM core and print dev->name and dev->drv->name all over the place
12:07
<
Clamor >
Ok, I see no unbinds and remove
12:07
<
marex >
(yeah, stack unwinding for backtraces would be nice to have)
12:07
<
marex >
Clamor: if you have no unbind/remove implemented, DM core calls the generic ones
12:08
<
Clamor >
I have dummy calls with prints
12:08
<
marex >
and neither is called ?
12:09
<
marex >
Clamor: what about in the regulator(s) ?
12:09
<
marex >
Clamor: stick printf into device_remove() and device_unbind() for maximum ease
12:11
<
Clamor >
marex: may you check those 4 commits with your board (if pmics are implemented)?
12:14
<
marex >
btw are you able to reproduce it on sandbox too ?
12:18
sng has joined #u-boot
12:19
<
Clamor >
No, I cannot reproduce it on sandbox
12:20
<
Clamor >
That post probe stuff is required to set up regulator according to tree
12:22
<
marex >
which tree ? DT ?
12:22
<
marex >
is that some regulator configuration stuff ?
12:23
<
Clamor >
Yes, device tree
12:23
<
Clamor >
It calls regulator autoconfiguration
12:23
<
Clamor >
So there is no need is calls from board
12:24
<
marex >
Clamor: and that cannot happen at probe time because the regulators might not all be available yet ?
12:24
<
marex >
Clamor: hence the post probe ?
12:24
sng has quit [Remote host closed the connection]
12:24
sng has joined #u-boot
12:25
<
Clamor >
Not to call it in every regulator driver probe
12:26
<
marex >
Clamor: why not ?
12:26
<
marex >
I think mmc subsystem does it too
12:26
<
marex >
for example ... it does call generic function in each driver probe I think
12:27
<
Clamor >
Driver probe replaces generic probe
12:28
<
Clamor >
Post probe in this case is uclass extension of driver probe
12:42
<
marex >
Clamor: you might want to double check how the uclass post* functions really behave
12:44
<
marex >
Clamor: the only other reason I can think of why the driver would be removed is some internal DM state corruption, which would be real bad
12:55
<
Clamor >
marex: It behaves exactly as intended, and I see no reason why the post probe should not be used in a way it was used.
12:58
Brainzman has quit [Quit: Brainzman]
13:06
Clamor has quit [Ping timeout: 246 seconds]
13:14
Clamor has joined #u-boot
13:56
ikarso has quit [Quit: Connection closed for inactivity]
14:06
prabhakarlad has joined #u-boot
14:32
Wouter0100670440 has joined #u-boot
14:46
sng has quit [Remote host closed the connection]
14:48
sng has joined #u-boot
15:07
Clamor has quit [Ping timeout: 256 seconds]
15:08
sakman has quit [Remote host closed the connection]
15:09
swiftgeek has quit [Quit: swiftgeek]
15:11
sakman has joined #u-boot
15:11
swiftgeek has joined #u-boot
15:19
swiftgeek has quit [Quit: swiftgeek]
15:20
swiftgeek has joined #u-boot
15:24
Perflosopher has quit [Quit: Ping timeout (120 seconds)]
15:24
swiftgeek has quit [Client Quit]
15:26
Perflosopher has joined #u-boot
15:27
swiftgeek has joined #u-boot
15:38
frieder has quit [Ping timeout: 245 seconds]
15:44
macromorgan has quit [Ping timeout: 245 seconds]
15:44
macromorgan has joined #u-boot
15:47
Brainzman has joined #u-boot
15:47
swiftgeek has quit [Quit: swiftgeek]
15:49
swiftgeek has joined #u-boot
15:51
frieder has joined #u-boot
15:52
frieder has quit [Remote host closed the connection]
16:06
macromorgan has quit [Ping timeout: 246 seconds]
16:15
macromorgan has joined #u-boot
16:15
prabhakarlad has quit [Quit: Client closed]
16:17
macromorgan is now known as Guest7868
16:17
macromorgan has joined #u-boot
16:20
sng has quit [Remote host closed the connection]
16:21
Guest7868 has quit [Ping timeout: 245 seconds]
16:23
mmu_man has quit [Ping timeout: 246 seconds]
16:31
Clamor has joined #u-boot
16:40
mmu_man has joined #u-boot
16:44
prabhakarlad has joined #u-boot
16:53
Clamor has quit [Ping timeout: 250 seconds]
16:55
prabhakarlad has quit [Quit: Client closed]
17:29
Brainzman has quit [Ping timeout: 256 seconds]
17:41
tepperson has joined #u-boot
17:48
ikarso has joined #u-boot
18:11
tepperson has quit [Quit: Client closed]
18:23
mmu_man has quit [Ping timeout: 244 seconds]
18:28
ezulian has quit [Ping timeout: 248 seconds]
18:37
sng has joined #u-boot
18:39
mmu_man has joined #u-boot
18:59
silurian_invader has joined #u-boot
19:50
silurian_invader has quit [Read error: Connection reset by peer]
19:51
sng has quit [Remote host closed the connection]
19:52
sng has joined #u-boot
20:04
___nick___ has quit [Ping timeout: 260 seconds]
20:17
sng has quit [Remote host closed the connection]
20:26
silurian_invader has joined #u-boot
20:32
prabhakarlad has joined #u-boot
20:43
prabhakarlad has quit [Quit: Client closed]
21:12
gsz has quit [Ping timeout: 260 seconds]
21:52
prabhakarlad has joined #u-boot
22:25
lucascastro has joined #u-boot
22:26
ikarso has quit [Quit: Connection closed for inactivity]
22:27
Wouter0100670440 has joined #u-boot
22:49
lucascastro has quit [Ping timeout: 245 seconds]
22:59
camus1 has joined #u-boot
22:59
camus has quit [Ping timeout: 248 seconds]
22:59
camus1 is now known as camus
23:03
cakes has quit [Quit: No Ping reply in 180 seconds.]
23:04
cakes has joined #u-boot
23:04
cakes has joined #u-boot
23:13
persmule has quit [Remote host closed the connection]
23:14
persmule has joined #u-boot
23:30
goliath has quit [Quit: SIGSEGV]
23:34
naoki has joined #u-boot