ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
apritzel has quit [Ping timeout: 248 seconds]
<hanetzer>
broonie: re: regmaps. is there a way to 'easily' attach a regmap driver via dts? as in, I'm just looking for an easyish way to read/write regs from userspace in bulk instead of having to loop devmem calls :P
sakman has joined #armlinux
tre has joined #armlinux
luispm has quit [Quit: Leaving]
krzk has quit [Remote host closed the connection]
iivanov has joined #armlinux
frieder has joined #armlinux
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
frieder has quit [Ping timeout: 240 seconds]
frieder has joined #armlinux
frieder has quit [Ping timeout: 246 seconds]
guillaume_g has joined #armlinux
luispm has joined #armlinux
<maz>
HdkR: this looks odd indeed. there is *one* platform that mixed GICv3 with something that looked like v2m (but really wasn't), but that's not Tegra, and that wasn't with DT anyway.
sszy has joined #armlinux
<HdkR>
I'll blame Nvidia quirkiness and not worry about it for now
frieder has joined #armlinux
frieder has quit [Ping timeout: 246 seconds]
nsaenz has joined #armlinux
alexels has joined #armlinux
matthias_bgg has joined #armlinux
frieder has joined #armlinux
monstr has joined #armlinux
monstr has quit [Remote host closed the connection]
monstr has joined #armlinux
headless has joined #armlinux
<ardb>
maz: but could it explain why VFIO is unhappy?
haritz has quit [Ping timeout: 276 seconds]
headless has quit [Ping timeout: 248 seconds]
headless_ has joined #armlinux
<maz>
ardb: v2m doesn't have IRQ_DOMAIN_FLAG_MSI_REMAP, so you need to additional convincing for vfio to use such a device.
<maz>
s/to/some/
headless_ is now known as headless
<maz>
but that's still odd. it'd be interesting to see what topology is reported by the kernel (which devices belong to which iommu groups).
<broonie>
hanetzer: no, the driver has to do it.
scosu[m] has joined #armlinux
<hanetzer>
blerg. well, thanks. I could probably write a small stub driver for the purpose :)
headless has quit [Quit: Konversation terminated!]
apritzel has joined #armlinux
milkylainen has quit [Quit: Ping timeout (120 seconds)]
krzk has joined #armlinux
haritz has joined #armlinux
haritz has joined #armlinux
haritz has quit [Changing host]
iivanov has left #armlinux [Leaving...]
iivanov has joined #armlinux
<Xogium>
so trying to hook up a IR sensor on my board here and it is a gpio one. I wondered, what determines if I must set gpio_active_high or low ? How can I know ?
<geertu>
Xogium: you have to check the sensor's datasheet
<geertu>
and the schematics, in case there's an inverter
<Xogium>
hmmm I don't know if there's an inverter on the stm32mp157f-dk2
<Xogium>
I hooked it up to gpioa8 on the st dev board
<Xogium>
I tested active_high first, but ir-keytable in testing mode sees nothing no matter what I try
<Xogium>
so I don't know if I should use low instead, or if I'm just doing it wrong lol
<Xogium>
it could also be the battery that's dead but I don't really know, and being blind with no light perveption at all probably doesn't help me here
<Xogium>
*perception
<Xogium>
or however you write that hah
<Xogium>
fun times
<Xogium>
being unable to check any schematics, friend of mine came up with a text version of the pinout on the dk2 board for me, so I could hook everything properly
sszy has quit [Ping timeout: 260 seconds]
<hanetzer>
hrm. kexec hangs after starting new kernel (there's just a smidge of dmesg over serial before it halts [visually, at least])
<mrutland>
Which kernel version, and are you using GICv3?
<mrutland>
... and is that 32-bit or 64-bit?
milkylainen has joined #armlinux
<maz>
and are you using DT or CPI, and are you using EFI to boot?
<maz>
ACPI*
<Xogium>
I think HdkR said kernel is 5.10.65, something like that
<hanetzer>
mrutland: kver is 5.19-rc*, tbh not sure about the gic, I have it specified as a pl390 in the dts for now. 32 bit.
<Xogium>
ah sorry, I thought it was for HdkR's issue since there was mention of gicv
<hanetzer>
and dtb (initial 'normal' boot is a uImage containing a zImage+dtb, because the u-boot on it doesn't support fit/etc for the board
<mrutland>
hanetzer: ah, then that's not gicv3, and not the issue I was suspecting
<hanetzer>
(u-boot-2010.06)
<maz>
huh. ancient stuff. that's the original GICv1.
<mrutland>
I can only suggest playing with earlycon and maybe keep_bootcon to get more UART output
<mrutland>
Ok, so you have earlycon output, and got as far as build_mem_type_table() before things went wrong
<mrutland>
So it should be possible to drop some debug prints into setup_arch() and figure if you get past early_mm_init(), etc
<hanetzer>
yay for early bringup woes.
<hanetzer>
I *would* just reboot, but rebooting (either via syscon-reboot or hisi-reboot, which both just write a value to a reg) kicks me back to the bootrom lol
<hanetzer>
vendor kernel has no problem rebooting in this regard.
<hanetzer>
actually, that's wrong. syscon-reboot kicks me into bootrom, hisi-reboot just fails and halts the system
<hanetzer>
ah, btw. re: gic stuff. is there a mechanism for definitively identifying them? I know you can id a bunch of primecell IPs by reading some regs, 0x0ff* or 0x0fe*, forget offhand?
headless has joined #armlinux
<hanetzer>
where can I get an older (3.10) vanilla kernel? gonna diff the vendor bsp kernel against it and see if they do any fudgery.
iivanov__ has joined #armlinux
iivanov has quit [Ping timeout: 256 seconds]
<maz>
hanetzer: reading the IIDR register would help identifying it.
* hanetzer
notes
<j`ey>
hanetzer: git has 3.10
<hanetzer>
j`ey: grabbed a tarball, but thanks :)
<hanetzer>
git has all of it eh? up to a point
<j`ey>
hanetzer: up to 2.6
* hanetzer
is at least glad he's not having to translate a 2.6 vendor kernel to ~mainline
<Xogium>
up to a point indeed. That moment where you find a bug that visibly predates the dawn of git history
cbeznea has joined #armlinux
iivanov has joined #armlinux
iivanov__ has quit [Ping timeout: 240 seconds]
iivanov has quit [Ping timeout: 244 seconds]
headless has quit [Quit: Konversation terminated!]
iivanov has joined #armlinux
Nact has joined #armlinux
robmur01 has joined #armlinux
jayBL has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
<robmur01>
HdkR: re VFIO, it'll be at least two things - the presence of any non-GICv3-ITS MSI domain means you'd need the "allow_unsafe_interrupts" parameter, but also if everything's stuffed into the same IOMMU group then if anything still has a driver bound that VFIO doesn't like it will also say no
<robmur01>
pretty much, yeah. The less said about UHCI the better :)
<Xogium>
uhci ? That sounds weird
* hanetzer
never heard of uhci tbh
<Xogium>
Universal Host Controller Interface ( UHCI) is a proprietary interface created by Intel for USB 1.x (full and low speeds). It requires a license from Intel. A USB controller using UHCI does little in hardware and requires a software UHCI driver to do much of the work of managing the USB bus.
<Xogium>
yech !
<hanetzer>
seems my IIDR is 0x0100143B
<marex>
UHhhhhh
<hanetzer>
yes?
<marex>
sorry, couldn't help myself /wrt the UHCI/OHCI USB 1.x discussion
<hanetzer>
heh.
<marex>
hanetzer: btw DWC2 core is capable of both USB LS/FS/HS and its neither ;-)
<hanetzer>
blerp.
<marex>
also, Mentor USB (musb), same thing ... but that has random bugs in random hardware, esp. omap, fun
<hanetzer>
but yeah. I just went thru the diff between 3.10.0 and '3.10.y' (as provided by the vendor) and nothing much stands out regarding their reboot handling.
<marex>
hanetzer: maybe they call PSCI voodoo hidden in firmware ?
<hanetzer>
maybe? I do know that bootrom_sel is set to 1. Maybe I need to poke around in the brom's 'source' some more and see if there's a thing there.
torez has quit [Quit: torez]
prabhakarlad has joined #armlinux
amitk has quit [Quit: leaving]
amitk has joined #armlinux
jayBL has quit [Quit: Client closed]
<hanetzer>
hrm. nothing in the brom I can see.
iivanov__ has joined #armlinux
iivanov has quit [Ping timeout: 260 seconds]
sudeepholla has quit [Ping timeout: 246 seconds]
tre has quit [Remote host closed the connection]
sudeepholla has joined #armlinux
jlinton has joined #armlinux
elastic_dog has quit [Ping timeout: 248 seconds]
elastic_dog has joined #armlinux
torez has joined #armlinux
alexels has quit [Ping timeout: 248 seconds]
amitk has quit [Quit: Lost terminal]
amitk has joined #armlinux
alexels has joined #armlinux
amitk has quit [Ping timeout: 260 seconds]
amitk_ has joined #armlinux
monstr has quit [Remote host closed the connection]
mraynal has quit [Ping timeout: 246 seconds]
Pali has joined #armlinux
frieder has quit [Remote host closed the connection]
cbeznea has quit [Quit: Leaving.]
cbeznea has joined #armlinux
matthias_bgg has quit [Read error: Connection reset by peer]
prabhakarlad has quit [Quit: Client closed]
luispm has quit [Ping timeout: 276 seconds]
guillaume_g has quit [Quit: Konversation terminated!]
matthias_bgg has joined #armlinux
luispm has joined #armlinux
matthias_bgg has quit [Quit: Leaving]
luispm has quit [Quit: Leaving]
jlinton has quit [Quit: Client closed]
<hanetzer>
good news tho. had a realization that since it kicks me back to brom I can use the hisilicon serial download protocol and load u-boot over serial to regain control of the device
Pali has quit [Ping timeout: 256 seconds]
alexels has quit [Quit: WeeChat 3.5]
headless has joined #armlinux
Nact has quit [Quit: Konversation terminated!]
prabhakarlad has joined #armlinux
apritzel has quit [Ping timeout: 246 seconds]
sudeepholla has quit [Quit: Ex-Chat]
nsaenz has quit [Quit: Leaving]
cbeznea has quit [Quit: Leaving.]
mraynal has joined #armlinux
NonaSuomy has joined #armlinux
Nact has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
headless has quit [Quit: Konversation terminated!]