#
…

2021-04-01

00:00troseman has joined #asahi
00:00neunon has quit [Quit: ZNC 1.8.2 - https://znc.in]
00:00Graypup_ has quit [Quit: ZNC 1.6.1 - http://znc.in]
00:00neunon has joined #asahi
00:01Graypup_ has joined #asahi
00:04rjeli has quit [Ping timeout: 248 seconds]
00:05rjeli has joined #asahi
00:24arcsor5 has joined #asahi
00:40odmir has joined #asahi
00:54raster has quit [Quit: Gettin' stinky!]
01:00odmir has quit [Ping timeout: 268 seconds]
01:17__rjeffman__ has joined #asahi
01:17_rjeffman has quit [Read error: Connection reset by peer]
01:21brentr123[m] has joined #asahi
01:26odmir has joined #asahi
01:30odmir has quit [Ping timeout: 240 seconds]
01:43odmir has joined #asahi
01:59odmir has quit [Ping timeout: 268 seconds]
02:11phiologe has quit [Ping timeout: 276 seconds]
02:11PhilippvK has joined #asahi
02:37aquijoule_ has joined #asahi
02:39richbridger has quit [Ping timeout: 240 seconds]
02:42troseman has quit [Read error: Connection reset by peer]
02:46mxw39 has quit [Quit: Konversation terminated!]
02:47mxw39 has joined #asahi
02:53mxw39 has quit [Quit: Konversation terminated!]
02:54mxw39 has joined #asahi
02:59bisko has joined #asahi
03:01bisko_ has quit [Ping timeout: 260 seconds]
03:02odmir has joined #asahi
03:12marvin24 has quit [Ping timeout: 245 seconds]
03:13marvin24 has joined #asahi
03:15jeffmiw has joined #asahi
03:20jeffmiw has quit [Ping timeout: 265 seconds]
03:34plainbits has joined #asahi
03:34plainbits has quit [Client Quit]
03:44arcsor5 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:58odmir has quit [Remote host closed the connection]
05:27VinDuv has joined #asahi
05:31ephe_meral has joined #asahi
06:01niv has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
06:03DarkShadow44 has quit [Read error: Connection reset by peer]
06:04niv has joined #asahi
06:06niv has quit [Client Quit]
06:06niv has joined #asahi
06:07niv has quit [Client Quit]
06:07niv has joined #asahi
06:09niv has quit [Client Quit]
06:10DarkShadow44 has joined #asahi
06:10DarkShadow44 has quit [Client Quit]
06:10jeffmiw has joined #asahi
06:11niv has joined #asahi
06:12niv has quit [Read error: Connection reset by peer]
06:15jeffmiw has quit [Ping timeout: 265 seconds]
06:18DarkShadow44 has joined #asahi
06:19DarkShadow44 has quit [Client Quit]
06:19DarkShadow44 has joined #asahi
06:20DarkShadow44 has quit [Client Quit]
06:21DarkShadow44 has joined #asahi
06:21DarkShadow44 has quit [Client Quit]
06:24DarkShadow44 has joined #asahi
06:25DarkShadow44 has quit [Client Quit]
06:25VinDuv has quit [Quit: Leaving.]
06:32DarkShadow44 has joined #asahi
06:33DarkShadow44 has quit [Client Quit]
06:35DarkShadow44 has joined #asahi
06:36DarkShadow44 has quit [Client Quit]
06:38DarkShadow44 has joined #asahi
06:40DarkShadow44 has quit [Client Quit]
06:41DarkShadow44 has joined #asahi
06:41niv has joined #asahi
06:51Necrosporus has quit [Killed (card.freenode.net (Nickname regained by services))]
06:51Necrosporus has joined #asahi
07:01Necrosporus has quit [Ping timeout: 240 seconds]
07:06Necrosporus has joined #asahi
07:10Empus has joined #asahi
07:10Empus has quit [Changing host]
07:12Necrosporus has quit [Ping timeout: 265 seconds]
07:18maor26 has joined #asahi
07:24vimal has joined #asahi
07:24Bublik has quit [Ping timeout: 268 seconds]
07:26Bublik has joined #asahi
07:33Necrosporus has joined #asahi
07:37svenokay, so there are gated clocks and clocks with a configurable frequency probably.
07:37sventhe gated clocks seems to have some dependencies as well (e.g. UART0 seems to depend on UART_P and SIO)
07:38svenand i think uart can be switched to UART_N possibly but testing that is a little bit tricky
07:38sventhe frequency clocks are defined in the "arm-io" ADT node but i can't figure out the clock-ids -> clock register mapping and i'm also too scared to flip bits in those registers
07:41Necrosporus has quit [Killed (verne.freenode.net (Nickname regained by services))]
07:41Necrosporus has joined #asahi
07:41svenoh, and there some PLLs. so i guess the PLLs generate some base frequencies and the freq clocks can select (or are hardwired) to one of those and allow that base freq to be divided down.
07:42maor26 has quit [Ping timeout: 265 seconds]
08:54marcanI think the UART has at least two clocks (the current driver patch does not attempt to support that; we can start to experiment now that we have non-UART channels)
08:56svenyeah, there are two clock-ids in the ADT. i think they are gated with UART_P and UART_N
08:56svenand additionally it probably needs UART0 enabled
09:00bngs[m] has quit [Quit: Idle for 30+ days]
09:00AONeiLL[m] has quit [Quit: Idle for 30+ days]
09:10bisko_ has joined #asahi
09:12bisko has quit [Ping timeout: 240 seconds]
09:36marcanyes, AIUI nominally the UART peripheral has one core clock and N baud clocks
09:36marcanthough presumably one of the baud clock options could be shared with the core clock
09:41svenso if the ADT is to be trusted there is one gating clock (UART0) and two clock-ids that i can't map to anything yet. but i believe these are UART_N and UART_P which could be two baud clocks
09:41sveni'll have to some experiments
09:41sven(and all this only started anyway because i was trying to figure out the i2c clock...)
09:46kettenis1correllium only has gating clocks for i2c
09:47sveni'm not sure they have added all clocks fwiw
09:48sveni have i2c working with the pasemi driver. i'd just like to see if i can find the clock that determines the frequency as well
09:48kettenis1sure, but it indicates the other clocks aren't important
09:48svenyeah, agreed
09:49sventhis is more me being curious than doing something that's directly useful ;)
09:49kettenis1correllium has some pinmuxing for the i2c pins
09:49sventhat's not required
09:49svenor, well, at least iboot leaves those pins in the correct state
09:49kettenis1yeah, that makes sense
09:50sveni'll need some gpio controller for the interrupt though
09:50svenbut i got distracted by the clocks :-)
09:51svenhttps://github.com/svenpeter42/linux/commits/i2c-wip that's the current i2c stuff i have. still needs a lot of work though, like e.g. the device tree bindings for which i'd like to figure out the clocks
10:16maor26 has joined #asahi
10:18maor has joined #asahi
10:19kettenis1presumably you'd want to set the divisor based on a clock-frequency property
10:21maor26 has quit [Ping timeout: 246 seconds]
10:22svenideally get the frequency of some parent clock and then calculate the divisor based on that
10:24raster has joined #asahi
10:26kettenis1that suggests it is possible to bring the i2x signals out
10:27kettenis1so with the right tools you might be able to actually measure the clock
10:27svenDevice addresses seen (unshifted): 0x38, 0x3f
10:27kettenis1the bus clock that is
10:27sventhose are the addresses of the ti usbc chips on that bus
10:27kettenis1that suggests it is the same bus then
10:28svensounds like that, yes
10:29kettenis1it will be hard to figure out though what the real input clock is to the block
10:31kettenis1and in the end it won't really matter of course
10:31sveni suspect the clock-ids in the ADT refers to it. i just don't what *exactly* that ids maps to. but maybe that's not even required. we could just have a dummy fixed-frequency clock for each of these ids
10:32kettenis1an "effective" model of the hardware is good enough
10:32sveni don't want to touch clock registers except for the gating ones anyway because i might actually be able to break the hardware that way
10:48marcanI'd be surprised if you could bork something permanently by touching clocks
10:49marcanbut I'd be happy to do the riskier bits :)
10:50marcanand yes, I was planning on looking at those i2c pins to measure the clock and other i2c behavior
10:50marcansince i need to port over that pasemi driver
10:50marcananyway, enough distractions, let me do one final change to AIC and push v4 out already now
10:51marcanffs it's been one thing after the other the past few weeks, personal things, then stallman...
10:51sveni already have that pasemi one kinda working fwiw
10:51marcanjust mostly as-is?
10:51svenpretty much
10:51marcanI have the pasemi doc so I should be able to add IRQ support based on that
10:51svenjust had to add a platform_device frontend on top of the current pci frontend
10:52svenand the one in the m1 needs a mystery bit set in the CTL register for transactions to work
10:52svenbut otherwise it's just the same thing
10:52marcanwhat bit?
10:52arndsven, marcan: if we can get consensus on the binding for the i2c port, this might be something to include in the initial dt
10:52sven0x800 in REG_CTL
10:53marcanarnd: if the existing driver works as-is, and we just need bog standard stuff, then we can definitely get this in after the initial series
10:53marcan(in the same merge window)
10:54arndright, that's what I meant
10:54svenit did need a little bit of refactoring to split the PCI parts out fwiw
10:54marcanyeah, as expected
10:54svenif we trust the ADT we can also just use two dummy clocks like the UART for now
10:54arnddoesn't have to be in the v4 series, but we may have enough time to get it into the pull request that I will send to torvalds for v5.13
10:55marcansven: 26:16 in CTL is a counter
10:55marcanmaximum slave size write
10:55marcanthat would need to be 1 to receive single bytes from the target
10:55arndsven: IIRC ojn said he intentionally left out irq support when he wrote that driver originally. You could ask him about that when he shows up on #armlinux the next time
10:55marcanlarger for larger reads
10:56svenhuh, interesting. i just stole the value that was pre-configured by iboot
10:56marcan(assuming this is the same as the pasemi one)
10:56marcanarnd: I already emailed him about this
10:56marcanhe can test once we have the improvements
10:56sveni'm not sure we need irq support for the i2c. it would just be nice to have
10:56marcanso we should be good
10:56marcanwell, we definitely want that
10:56svenbut that typec ti chip needs and irq and it gets that one from the gpio controller
10:56marcanotherwise it turns into a crappy blocking game
10:57svenfair enough
10:57marcanbut it's not required to *work* of course
10:57marcanjust to not suck :-)
10:57svenyeah, pretty much :)
10:57svenbut at least the ti chip doesn't have much traffic
10:57marcanso the original PCI so there's no DT binding, right?
10:57marcanbut the DT bindings should be 100% bog standard i2c stuff anyway
10:57marcanand PCI means the IRQ stuff is standard
10:58marcanso this should all be extremely simple
10:58svenyeah, pretty much
10:58kettenis1i'd say you only need to ducument "reg" and "compatible"
10:58svenso the i2c needs one clock gate and probably one clock for the base frequency
10:58marcankettenis1: exactly
10:58marcanand interrupts
10:58marcanwell, and clock and maybe power
10:59marcanbut again, these are all standards things every i2c controller on every soc pretty much has
10:59sveni'll look into cleaning up what i have for the pasemi one so far and c&p some simple i2c dt binding then
11:01sveni guess it's fine to already have the interrupt in the binding but just not use it in the driver for now, isn't it?
11:03kettenis1I'd say so
11:04arndah, the driver is so old we didn't document the bindings back then
11:06arndnevermind, I missed that this is a pci_driver in the original version
11:13arndagreed on documenting the interrupt
11:15marcanI bet the binding can be reduced to picking an existing simple i2c one and s//ing the name
11:16marcanthere have to be a good dozen or so ~identical ones along these lines
11:21arndNot sure what the current method is for having multiple i2c drivers with the same i2c_algorithm. I'd probably start out having one module that exports it as i2c_pasemi_algorithm, and then duplicate the probe() function into one module for pci and platform each.
11:22arndTraditionally, the algorithm would be in drivers/i2c/algos/, with an abstract probe function, but this is probably more work than necessary
11:23arndthe other way would be to have everything in one file, with some #ifdefs to deal with the possible combinations of platform and pci support, but that seems ugly
11:23marcanyeah, splitting it into separate modules seems saner
11:25arndout of the three remaining i2c algorithms that remain in drivers/i2c/algos, only the bitbang version is actually used by more than two drivers, the other two each have an ISA (!) frontend and a platform front-end
11:25svenright now i just have it one file but i can easily split that
11:28Calchan has quit [Ping timeout: 240 seconds]
11:32Calchan has joined #asahi
11:54TheJollyRoger has quit [Remote host closed the connection]
11:55TheJollyRoger has joined #asahi
12:15TheLink has quit [Quit: Blubb]
12:15choozy has joined #asahi
12:20TheLink has joined #asahi
12:58choozy has quit [Ping timeout: 245 seconds]
13:00choozy has joined #asahi
13:02frode_0xa has joined #asahi
13:02frode_0xa has quit [Client Quit]
13:06frode_0xa has joined #asahi
13:07frode_0xa has quit [Client Quit]
13:08frode_0xa has joined #asahi
13:08frode_0xa has quit [Client Quit]
13:10frode_0xa has joined #asahi
13:11frode_0xa has quit [Client Quit]
13:14frode_0xa has joined #asahi
13:23odmir has joined #asahi
13:28odmir has quit [Ping timeout: 250 seconds]
13:51Behemoth has quit [Quit: Quit]
13:51Behemoth has joined #asahi
13:54Behemoth has quit [Client Quit]
13:55Behemoth has joined #asahi
14:21choozy has quit [Ping timeout: 245 seconds]
14:33bisko has joined #asahi
14:33bisko_ has quit [Ping timeout: 268 seconds]
15:45scooby2_ is now known as scooby2
15:45scooby2 has quit [Changing host]
15:45scooby2 has joined #asahi
16:03arcsor5 has joined #asahi
16:18choozy has joined #asahi
16:34ephe_meral has quit [Ping timeout: 240 seconds]
16:39ephe_meral has joined #asahi
16:46odmir has joined #asahi
16:51arcsor5 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:53vilhalmer has quit [Ping timeout: 265 seconds]
17:00VinDuv has joined #asahi
17:00vilhalmer has joined #asahi
17:12djhworld has quit [Quit: The Lounge - https://thelounge.chat]
17:13djhworld has joined #asahi
17:14roxfan2 is now known as roxfan
17:14Calchan has quit [Quit: ZNC - http://znc.in]
17:18djhworld has quit [Quit: The Lounge - https://thelounge.chat]
17:19djhworld has joined #asahi
17:24jeffmiw has joined #asahi
17:28jeffmiw has quit [Ping timeout: 246 seconds]
17:34bisko has quit [Ping timeout: 240 seconds]
17:34bisko has joined #asahi
17:44__rjeffman__ has quit [Remote host closed the connection]
17:54kettenis1 has quit [Ping timeout: 246 seconds]
18:06kettenis1 has joined #asahi
19:03markiehill has joined #asahi
19:07markiehi_ has joined #asahi
19:08markiehi_ has quit [Client Quit]
19:08markiehi_ has joined #asahi
19:09markiehi_ has quit [Client Quit]
19:09markiehi_ has joined #asahi
19:10markiehill has quit [Ping timeout: 240 seconds]
19:12markiehi_ has quit [Remote host closed the connection]
19:35noc0lour1 has joined #asahi
19:55kettenis1 has quit [Ping timeout: 240 seconds]
19:57kettenis1 has joined #asahi
20:13ephe_meral has quit [Ping timeout: 268 seconds]
20:20odmir has quit [Remote host closed the connection]
20:20odmir has joined #asahi
20:25odmir has quit [Ping timeout: 250 seconds]
20:40TheLink has quit [Quit: Blubb]
20:43TheLink has joined #asahi
20:51odmir has joined #asahi
20:53VinDuv has quit [Quit: Leaving.]
21:12raster has quit [Quit: Gettin' stinky!]
21:27odmir has quit [Ping timeout: 245 seconds]
22:08jeffmiw has joined #asahi
22:12jeffmiw has quit [Ping timeout: 240 seconds]
22:16odmir has joined #asahi
22:27odmir has quit [Remote host closed the connection]
22:28odmir has joined #asahi
22:33qyousef_ has quit [Ping timeout: 268 seconds]
22:34qyousef_ has joined #asahi
23:14The_DarkFire_[m] has joined #asahi
23:42bisko_ has joined #asahi
23:42bisko has quit [Ping timeout: 268 seconds]
23:47raster has joined #asahi
23:57maor has quit [Ping timeout: 246 seconds]
…