kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
WoC` has quit [Remote host closed the connection]
WoC` has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
WoC` has quit [Remote host closed the connection]
WoC` has joined #linux-rockchip
vagrantc has joined #linux-rockchip
WoC has joined #linux-rockchip
WoC` has quit [Ping timeout: 245 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
kaspter has joined #linux-rockchip
superherointj has quit [Quit: Leaving]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
vagrantc has quit [Quit: leaving]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 252 seconds]
kaspter has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery1 is now known as kevery
vstehle has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 268 seconds]
kevery1 is now known as kevery
ldevulder has quit [Remote host closed the connection]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
warpme_ has joined #linux-rockchip
<Net147>
any suggestions for getting DisplayPort Alt Mode to work over USB-C connector for RK3399 with mainline kernel to connect a DisplayPort monitor?
ldevulder has joined #linux-rockchip
<robmur01>
Net147: yes - rewrite the upstream type C phy driver to use the type C APIs rather than extcon
<robmur01>
it only works with the cros-ec on Chromebooks, not any other type C port controller chips :(
<macc24>
robmur01: it works with anything? LOL
matthias_bgg has joined #linux-rockchip
<robmur01>
IIRC the Manjaro kernel for the Pinebook pro has some horrible extcon hacks on top of mainline to make things work with FUSB302, but a proper upstream solution is still outstanding
kaspter has quit [Ping timeout: 252 seconds]
kaspter has joined #linux-rockchip
kevery1 has joined #linux-rockchip
<macc24>
robmur01: does cros ec linux driver not support generic c api?
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
<macc24>
c api as in usb type c
<robmur01>
no - there were some patches a while back to start implementing some of the power reporting bits (or something similar?), but not that would make any difference to RK3399 (and nothing on the corresponding RK3399 tcphy end)
<macc24>
i don't understand... does it support it or not? because when you said 'no' you could be saying that it is not supporting type c api, but you could also be denying that it doesn't support it, which would mean that it cros ec driver supports type c api
<robmur01>
that would be an affirmative no :P
<macc24>
…
<robmur01>
as in, "Does it not? No it does not."
<macc24>
ok
<robmur01>
English is fun...
<macc24>
it sure is
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 268 seconds]
camus is now known as kaspter
stikonas has joined #linux-rockchip
kevery1 has joined #linux-rockchip
field^Zzz1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
field^Zzz1 has quit [Ping timeout: 252 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
psydruid[m] has quit [Ping timeout: 276 seconds]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
unrelentingtech has quit [Ping timeout: 260 seconds]
psydruid[m] has joined #linux-rockchip
dianders has quit [Ping timeout: 260 seconds]
unrelentingtech has joined #linux-rockchip
dianders has joined #linux-rockchip
maz has quit [Remote host closed the connection]
maz has joined #linux-rockchip
<mmind00>
- check if that cros-ec type-c+power-delivery works correctly on rk3399 chromebooks
<mmind00>
macc24: when rk3399 got used in Chromebooks, cros-ec didn't support the kernel's type-c framework, hence the cros-ec extcon connecting to the rk3399-typec-phy ... meanwhile from what I've seen, cros-ec got type-c subsystem integration, including power-delivery, so todo for interested parties:
<mmind00>
- adapt rockchip type-c phy driver into the kernels type-c infrastructure + migrate mainline to cros-ec-pd (to not break existing functionality)
<mmind00>
- enable real type-c handling on none chromeos rk3399 boards ;-)
<macc24>
when i'm bored - maybe
<macc24>
now i got a new toy to play with >:D
<macc24>
a supermicro server
<mmind00>
macc24: be more bored then ;-)
<mmind00>
macc24: but I fully understand the not being bored part ... normally for me there isn't enough "day" remaining for everything I want to do
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
mriesch has quit [Quit: No Ping reply in 180 seconds.]
kevery1 is now known as kevery
mriesch has joined #linux-rockchip
<mps>
mmind00: what does mean 'in Chromebooks, cros-ec didn't support the kernel's type-c framework'
<mps>
I run mainline kernels on rk3399 gru-kevin chromebook
<mmind00>
mps: but only due to the extcon "hack" ;-)
<mps>
what is 'extcon "hack"'
<mmind00>
mps: i.e. back in 2016, the kernel's whole type-c infrastructure was still pretty new, so "someone" introduced that extcon connection between cros-ec and the rockchip tcphy to allow to transmit usb-c states
<mps>
ah
<mps>
thanks for explanation
<mmind00>
mps: the _correct_ way is to actually _use_ the kernel's real type-c framework to do that ... hence usb-c on rk3399 chromebooks works quite nicely (including displayport when I checked that a long time ago) ... but not on all other rk3399 boards
kevery has quit [Ping timeout: 240 seconds]
kevery has joined #linux-rockchip
<mps>
I didn't checked with displayport, for my use case its display is enough
ldevulder has quit [Remote host closed the connection]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
ldevulder has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 268 seconds]
matthias_bgg has joined #linux-rockchip
macromorgan has quit [Quit: Leaving]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
kevery1 is now known as kevery
uis has joined #linux-rockchip
macromorgan has joined #linux-rockchip
indy has quit [Ping timeout: 240 seconds]
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus is now known as kaspter
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 265 seconds]
camus is now known as kaspter
superherointj has joined #linux-rockchip
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
WoC has quit [Remote host closed the connection]
archetech has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
archetech has quit [Quit: Konversation terminated!]
alpernebbi has quit [Quit: alpernebbi]
superherointj has joined #linux-rockchip
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
<Net147>
I am more interested in usb-c on other rk3399 boards with fusb302 since I don't have any chromebooks
superherointj has quit [Quit: Leaving]
superherointj has joined #linux-rockchip
superherointj has quit [Client Quit]
superherointj has joined #linux-rockchip
<macromorgan>
so if I'm doing a printk("%p", dev->regbase); and I get an address of 000000008adac08b, is there a reason why printk("%p", dev-regbase + VALUE1); would give me an address of 00000000bd143d67 if VALUE1 is defined as 0x10? I can confirm the regbase is a valid __iomem.
<macromorgan>
just to confirm I mean printk("%p", dev->regbase + VALUE1); (I missed a greater than in the example posted, but the code is correct)
macromorgan has quit [Quit: Leaving]
macromorgan has joined #linux-rockchip
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
<urjaman>
macromorgan: %p prints hashes of the address, not the actual address these days, to avoid leaking kernel memory layout
<macromorgan>
any way I can force the issue? This is for driver development and nothing goes into production with this...
<urjaman>
%px
<macromorgan>
I'm getting an error the instant I try to read or write to a register (readl/writel)
<macromorgan>
thank you, you've answered my question and I can confirm my addresses are correct. Still not sure why a readl/write causes an SError Interrupt
<macromorgan>
especially when they don't in U-boot
<macc24>
macromorgan: something tells me printk("%d", &dev->regbase)
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
psydruid[m] has quit [Ping timeout: 245 seconds]
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 252 seconds]
camus is now known as kaspter
stikonas has quit [Remote host closed the connection]
psydruid[m] has joined #linux-rockchip
<robmur01>
macromorgan: power domains, clocks, that sort of thing - once you get into Linux, other drivers start turning things off that were on by default at boot time
<robmur01>
SError is actually the "nice" result of trying to access something that can't respond, since the other most likely outcome is just deadlocking in the interconnect
kaspter has quit [Remote host closed the connection]