Ultrasauce has quit [Remote host closed the connection]
sauce has joined #linux-sunxi
<MoeIcenowy>
jernej: because the DT binding is not accepted
<MoeIcenowy>
apritzel: model A ?
apritzel has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
cnxsoft has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
vagrantc has joined #linux-sunxi
stipa has quit [Read error: Connection reset by peer]
stipa has joined #linux-sunxi
<jernej>
apritzel: what change?
junari has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
stipa is now known as Guest3096
stipa has joined #linux-sunxi
Guest3096 has quit [Ping timeout: 480 seconds]
junari has joined #linux-sunxi
apritzel has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
apritzel has quit [Ping timeout: 480 seconds]
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
Brandon has joined #linux-sunxi
Brandon has quit []
vpeter has quit [Remote host closed the connection]
szemzoa has quit [Remote host closed the connection]
vpeter has joined #linux-sunxi
szemzoa has joined #linux-sunxi
szemzoa has quit [Remote host closed the connection]
szemzoa has joined #linux-sunxi
junari_ has quit []
stipa has quit [Remote host closed the connection]
junari has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari has quit [Read error: Connection reset by peer]
junari__ has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
<apritzel>
jernej: I meant MoeIcenowy's DT change that you linked to yesterday. I just applied that on otherwise mainline software bits, and it worked out of the box
<apritzel>
dt-validate just complains about the connector subnode not known, but this should be a simple binding fix
<apritzel>
MoeIcenowy: did you already send a binding change to introduce the connector node? Was that the one that was rejected?
<apritzel>
the USB connector binding speaks of the connector being a subnode of the "USB interface controller" node, I guess that would mean the ehci/ohci node?
indy has joined #linux-sunxi
Net147 has quit [Quit: Quit]
Net147 has joined #linux-sunxi
megi has quit [Quit: WeeChat 3.6]
megi has joined #linux-sunxi
<MoeIcenowy>
apritzel: yes the binding says "controller"
<MoeIcenowy>
it's weird
<MoeIcenowy>
and the rejected binding change is in the patchset
junari_ has joined #linux-sunxi
junari__ has quit [Ping timeout: 480 seconds]
<apritzel>
MoeIcenowy: I agree with you that the supply should be closer to the PHY, not the HCI
JohnDoe_71Rus has quit []
junari__ has joined #linux-sunxi
junari_ has quit [Read error: No route to host]
junari_ has joined #linux-sunxi
smaeul has joined #linux-sunxi
junari__ has quit [Ping timeout: 480 seconds]
grming has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
cnxsoft has quit []
<apritzel>
MoeIcenowy: and two more things: - the snps,dwc3 binding does not allow a connector child either (yet)
<apritzel>
- the Marvell DTs specifying an usb-a-connector also put them in their (Combo-)PHY nodes
mkazantsev has joined #linux-sunxi
DarkNeutrino has quit [Ping timeout: 480 seconds]
DarkNeutrino has joined #linux-sunxi
infu has joined #linux-sunxi
DarkNeutrino has quit [Read error: No route to host]
DarkNeutrino has joined #linux-sunxi
DarkNeutrino has quit [Ping timeout: 480 seconds]
diego71_ has joined #linux-sunxi
diego71 has quit [Ping timeout: 480 seconds]
DarkNeutrino has joined #linux-sunxi
<jernej>
apritzel: disable usb2 nodes and usb3 will also stop working...
<jernej>
call to enable regulator needs to be added anyway
<apritzel>
jernej: you mean it's just the status="okay"; in the dwc3 node that makes it work?
<jernej>
no, pineh64 uses same regulator for usb2 and usb3 ports
<jernej>
since it's enabled for usb2, naturally, it will work with simple DT patch
<apritzel>
yeah, that's what I meant: the connector node was a red herring
<jernej>
ah, sorry, yes
<apritzel>
good find anyway
<jernej>
and I went down same rabbit hole yesterday regarding USB descriptions in various DT files
<jernej>
I agree that PHY seems natural choice for declaring connectors
<apritzel>
indeed, now we just need to convince Rob ;-)
<jernej>
but on the other hand, USBs are often OTG capable and controller needs to know when to switch
<jernej>
based on properties (id-gpios or vbus-gpios) in connector node
pg12_ has joined #linux-sunxi
<jernej>
and I saw same design for HDMI nodes - HDMI controller has PHY phandle, but connector is again connected to controller, not PHY
<jernej>
so there must be some reason, unknown to me
pg12 has quit [Ping timeout: 480 seconds]
junari_ has quit [Ping timeout: 480 seconds]
<apritzel>
I guess we need to start a discussion with Rob again. Care to just re-send MoeIcenowy's patch? Maybe adding a binding patch, to allow a connector in the PHY subnode?
<apritzel>
more as a discussion base, really
<jernej>
I guess we should change our approach for sending patch series. There were many misunderstandings this cycle. It's best to always target only one tree.
ftg has joined #linux-sunxi
<jernej>
apritzel: do we know if USB3 is OTG capable?
<jernej>
driver says if core revision is 330a or higher, it's not. Integration could further limit that.
<apritzel>
I have no clue at the moment, but I guess we could figure that out?
<apritzel>
would the PHY be involved in the OTG switching? Or is it a pure DWC3 thing?
<jernej>
no idea, really
<jernej>
manual mentions only host
<apritzel>
jernej: I just hope that not every of the "trivial" patches you plan to upstream requires this kind of effort ;-)
<jernej>
well, it was trivial only on surface
vagrantc has joined #linux-sunxi
<jernej>
speaking of seemingly easy improvements, montjoie, your OrangePi 3 ethernet series was only partially merged, right?
<jernej>
montjoie_ ^
Net147 has quit [Ping timeout: 480 seconds]
digetx has quit [Ping timeout: 480 seconds]
Net147 has joined #linux-sunxi
digetx has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
<jernej>
apritzel: do you remember me talking about boot issue with TF-A on Tanix-TX6 with disabled regulators via param?
<apritzel>
jernej: is there something else on those PL pins?
<jernej>
not that I know. I checked Android DT, but there is no reference.
<apritzel>
so if I see this correctly it hangs on the first attempt to communicate with the PMIC
<jernej>
correct
<jernej>
well, it fails a few cycles later. UART always prints one character of next message
<jernej>
note that I have Crust included, but it's not started at that point, right?
<jernej>
changing bus speed also doesn't help
<apritzel>
I am undecided between providing a build option to disable PMIC support at all, or doing this at runtime
<apritzel>
I guess I2C would somehow fail if there is no device (SDA/SCL floating), but maybe this I2C wrapper command in the RSB hardware cannot deal with this gracefully?
JohnDoe_71Rus has quit []
<jernej>
still, even if not, why it would cause CPU lock up?
NekoMay has quit [Ping timeout: 480 seconds]
<jernej>
apritzel: do you have any idea how to check for pmic node in DT in TF-A?
<apritzel>
lol, I am just implementing that ;-)
<apritzel>
the simplest (read smallest in code size) seems to be fdt_node_offset_by_compatible
<apritzel>
and then check the status property
<jernej>
I'm eager to test that and if you don't mind, I would integrate it in LE image
<jernej>
which can bring some additional test coverage
<apritzel>
yeah, my main concern is that it blows up the A64 build, so I am looking at saving some code elsewhere
NekoMay has joined #linux-sunxi
<jernej>
aren't fdt functions already included?
<jernej>
how tight is A64 build?
<jernej>
I guess I have some room since I disabled enabling regulators
<apritzel>
very tight
<apritzel>
H6 is not really the problem, IIRC, but I want to keep this new code common
<apritzel>
some fdt functions are included, but this would pull in some more
<jernej>
what about fdt_path_offset()? it could be used to check if path exists and only two are needed, i2c and rsb
<apritzel>
that was plan B, but I don't know if this is really smaller in code size, let's see
ftg has quit [Ping timeout: 480 seconds]
DarkNeutrino has quit [Read error: Connection reset by peer]
DarkNeutrino has joined #linux-sunxi
<apritzel>
jernej: just realised that we were cheating all the time on the PineH64: the RSB node is disabled there (because of that extra I2C RTC), but we were still using it
<jernej>
yeah, I noticed
<jernej>
so RTC didn't work?
<apritzel>
well, no, but we were driving the I2C bus with both RSB frequency and RSB signals
<jernej>
I'll have to test it separately, maybe Crust saved the day
<jernej>
I believe it uses I2C on that board
<apritzel>
I think it's fine, in practise, but it's fragile at the very least, and violates the DT
<jernej>
apritzel: so H616 will also have this issue with axp313a
<jernej>
it has i2c only bus
<jernej>
I mean, AXP313a supports I2C only
<apritzel>
indeed, hence I wanted a common solution
<apritzel>
we need to think about how to (or whether to?) support the AXP313a anyway
<jernej>
btw, fdt_node_offset_by_compatible() works nicely
<apritzel>
yeah, it's inefficient, but we don't care here
<apritzel>
on H6 the size doesn't change at all (because all sections are padded to 4K pages)
<mkazantsev>
hello! Is there by chance an LVDS support patch for D1/T113? I have a T113-S3 Evaluation Board with an LVDS LCD, trying to make it show things