narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
vagrantc has joined #linux-amlogic
Flole has quit [Remote host closed the connection]
Consolatis has quit [Ping timeout: 265 seconds]
Consolatis has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
buzzmarshall has quit [Quit: Konversation terminated!]
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-amlogic
JohnnyonFlame has quit [Read error: Connection reset by peer]
Daaanct12 has quit [Remote host closed the connection]
nobbb has joined #linux-amlogic
JohnnyonFlame has joined #linux-amlogic
nobbb has quit [Read error: Connection reset by peer]
tkna has joined #linux-amlogic
vagrantc has joined #linux-amlogic
<xdarklight> narmstrong: https://patchwork.ozlabs.org/project/devicetree-bindings/patch/0a82be92-ce85-da34-9d6f-4b33034473e5@gmail.com/ can cause a new warning in arch/arm64/boot/dts/amlogic/meson-khadas-vim3.dtsi because phy-supply is not allowed for &usb3_pcie_phy - but the other two PHYs also have a phy-supply property (which looks strange at first glance)
<xdarklight> narmstrong: I *think* we need to use compatible = "usb-a-connector" nodes with vbus-supply = ...; but I have no way of testing this
tkna has quit [Remote host closed the connection]
dliviu has quit [Quit: Going away]
dliviu has joined #linux-amlogic