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
scosu_ has joined #armlinux
jn has quit [Ping timeout: 240 seconds]
jn has joined #armlinux
jn has joined #armlinux
jn has quit [Changing host]
scosu has quit [Ping timeout: 240 seconds]
apritzel has quit [Ping timeout: 240 seconds]
<HdkR> Is there a system register to determine LSE2 granularity. Or is it just a try and find the fault problem?
jlinton has joined #armlinux
LeSpocky_ has joined #armlinux
LeSpocky has quit [Ping timeout: 240 seconds]
LeSpocky_ has quit [Ping timeout: 240 seconds]
LeSpocky has joined #armlinux
Drek45 has quit [Remote host closed the connection]
russ has joined #armlinux
elastic_dog has quit [Ping timeout: 240 seconds]
sakman has quit [Remote host closed the connection]
elastic_dog has joined #armlinux
shailangsa has quit [Ping timeout: 240 seconds]
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 240 seconds]
sakman has joined #armlinux
Shailangsa_ has joined #armlinux
amitk has joined #armlinux
Nact has quit [Remote host closed the connection]
apritzel has joined #armlinux
frieder has joined #armlinux
apritzel has quit [Ping timeout: 250 seconds]
tre has joined #armlinux
Pali has joined #armlinux
scosu_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
scosu has joined #armlinux
tudorel has joined #armlinux
scosu has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
eduardas has joined #armlinux
Pali has quit [Ping timeout: 252 seconds]
djrscally has joined #armlinux
apritzel has joined #armlinux
<arnd> mmind00, geertu: I see that 2a1c55d4762d ("soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally") allows turning off the driver when compile-testing an ARCH_ROCKCHIP driver, is that intentional?
<arnd> mmind00: also, 53a05c8f6e8e ("arm64: dts: rockchip: remove interrupt-names from iommu nodes") looks odd: the description just mentions that the driver doesn't use the interrupt-names property, but I don't see why that is a reason to change the dts here
<arnd> is this a property that was never meant to be there? Are you sure that nothing outside of Linux uses them?
<arnd> most likely the change is correct, but the description is not great
<mmind00> arnd: interrupt-names ... yep that is not part of the binding at all
<arnd> right, it also doesn't seem to make sense to have different names for the interrupt in each node, so adding it to the binding also would not help
<arnd> mmind00: I'm still undecided about the entire rockchip/dt-64 branch, it came really late for something of its size
<arnd> I did merge the 32-bit dt changes because they are fairly small
<arnd> would it be ok to postpone the branch to 5.16?
<mmind00> arnd: on the one hand, the very most of it is in linux-next for weeks - I "just" sort-of stumbled with the pull timing ... but if you feel uncomfortable with it, then yeah we can of course postpone
<mmind00> arnd: as for the grf-driver ... it is not a necessity on every Rockchip soc, so it is possible to disable it ... the basic funcionality is provided by the syscon-part of the "General Register Files"
<mmind00> the driver does just handle settings that in an ideal world the bootloader would have already set
<arnd> ok, let's leave it as it is then
Shailangsa_ has quit [Remote host closed the connection]
<arnd> robher: I had applied your "arm/arm64: dts: Fix remaining dtc 'unit_address_format' warnings" to the 5.14 fixes branch already, but noticed now that it has a minor conflict against the arm/dt branch, and that you did not actually specify whether this is 5.14 or 5.15 material.
<arnd> robher: can you clarify which release you were targetting? If I can merge it for 5.15, I can take care of the conflict while applying, but if there are existing warnings in 5.14 that we should really fix now, that is also possible
<arnd> I only have three trivial fixes left for 5.14 otherwise
shailangsa has joined #armlinux
eduardas has quit [Ping timeout: 250 seconds]
eduardas has joined #armlinux
alpernebbi has joined #armlinux
monstr has joined #armlinux
<robher> arnd: 5.15. They're all hidden behind W=1 still.
<arnd> robher: ok, thanks
<la_mettrie> file command thinks that ARM64 kernel-image is "MS-DOS executable"
<j`ey> la_mettrie: that's true
<j`ey> la_mettrie: it's the EFI stub causing that
<Xogium> then again… file command is pretty easy to confuse, in my experience, since it only looks at a few bytes
<Xogium> it still thinks any arm binary that isn't aarch64 is armv5, no matter that it is armv5, armv6 or armv7
tre has quit [Remote host closed the connection]
CrashTestDummy2 has joined #armlinux
CrashTestDummy has quit [Ping timeout: 250 seconds]
torez has joined #armlinux
luisgpm has quit [Ping timeout: 240 seconds]
luisgpm has joined #armlinux
alpernebbi has quit [Quit: No Ping reply in 180 seconds.]
alpernebbi has joined #armlinux
bps has quit [Ping timeout: 240 seconds]
Nact has joined #armlinux
Amit_T has joined #armlinux
eduardas has quit [Quit: Konversation terminated!]
russ has quit [Ping timeout: 250 seconds]
headless has joined #armlinux
russ has joined #armlinux
Amit_T has quit [Ping timeout: 240 seconds]
Drek45 has joined #armlinux
frieder has quit [Remote host closed the connection]
Amit_T has joined #armlinux
Pali has joined #armlinux
Amit_T has quit [Read error: Connection reset by peer]
tudorel has quit [Quit: tudorel]
Amit_T has joined #armlinux
amitk has quit [Ping timeout: 250 seconds]
apritzel has quit [Ping timeout: 250 seconds]
alpernebbi has quit [Quit: alpernebbi]
Drek45 has quit [Ping timeout: 250 seconds]
Drek45 has joined #armlinux
Drek45 has quit [Ping timeout: 240 seconds]
Amit_T has quit [Quit: Leaving]
bps has joined #armlinux
bps has quit [Changing host]
bps has joined #armlinux
Drek45 has joined #armlinux
monstr has quit [Remote host closed the connection]
alyssa has joined #armlinux
<alyssa> sven: suggested I ask here--
<alyssa> Given a physical address corresponding to ordinary RAM (not device memory) allocated outside of the kernel (not kmalloc), how can I map it and get a virtual address?
<alyssa> ioremap and friends are for I/O memory, not regular RAM (unless it also works the same?)
<alyssa> phys_to_virt seems to be valid only for memory Linux allocated and knows about (it won't actually map it into the CPU MMU)
<alyssa> trying to take over IOMMU page tables for the DART driver (apple m1)
<alyssa> kmap seems promising but the API seems extremely low level
<alyssa> Ah, ioremap_cache?
torez has quit [Quit: torez]
macromorgan has quit [Quit: Leaving]
macromorgan has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
CrashTestDummy3 has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 250 seconds]
jlinton has quit [Quit: Client closed]
Drek45 has quit [Remote host closed the connection]
punit_ has joined #armlinux
mal``` has joined #armlinux
arnd_ has joined #armlinux
mal`` has quit [Read error: Connection reset by peer]
mwalle has quit [Ping timeout: 276 seconds]
arnd has quit [Ping timeout: 276 seconds]
punit has quit [Read error: Connection reset by peer]
arnd_ is now known as arnd
headless has quit [Quit: Konversation terminated!]
mwalle has joined #armlinux
CrashTestDummy2 has joined #armlinux
CrashTestDummy3 has quit [Ping timeout: 250 seconds]
CrashTestDummy3 has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
CrashTestDummy2 has joined #armlinux
CrashTestDummy3 has quit [Ping timeout: 240 seconds]
prabhakarlad has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
<alyssa> ioremap_cache seems to work, don't know if it's correct though.
<alyssa> Could always send the patch and then if I wake up to 12 angry emails the next day I know it's incorrect 😉
apritzel has joined #armlinux
djrscally has quit [Ping timeout: 250 seconds]
Pali has quit [Ping timeout: 250 seconds]
Drek45 has joined #armlinux