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
nashpa has quit [*.net *.split]
vagrantc has quit [*.net *.split]
anessen97 has quit [*.net *.split]
dliviu has joined #linux-amlogic
vagrantc has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
rapha has joined #linux-amlogic
rapha has quit [Changing host]
camus has quit [Read error: Connection reset by peer]
camus has joined #linux-amlogic
c0rnelius has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
camus has quit [Ping timeout: 252 seconds]
camus has joined #linux-amlogic
elastic_dog has quit [Ping timeout: 260 seconds]
elastic_dog has joined #linux-amlogic
chewitt_ has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
chewitt_ has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
tdebrouw has joined #linux-amlogic
tdebrouw has quit [Quit: Leaving.]
tdebrouw has joined #linux-amlogic
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-amlogic
warpme__ has joined #linux-amlogic
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
Guest4917 has quit [Remote host closed the connection]
chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #linux-amlogic
chewitt_ is now known as chewitt
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus1 is now known as camus
camus has quit [Ping timeout: 252 seconds]
camus has joined #linux-amlogic
jernej has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-amlogic
anessen97 has joined #linux-amlogic
<gbisson> hi all, playing around more with a311d brought a couple of questions: 1) isn't there any cpufreq driver available? can't seem to find any scaling governors for the CPU. 2) is the internal PHY (10/100M) supposed to work out of the box? doesn't seem to probe on my end
jernej has quit [Ping timeout: 252 seconds]
sputnik has joined #linux-amlogic
sputnik is now known as Guest2050
<xdarklight> gbisson: both should work. are you using the arm64 defconfig or a custom one?
<xdarklight> gbisson: for cpufreq you want CONFIG_CPUFREQ_DT + CONFIG_REGULATOR_PWM + meson PWM driver ...
Guest2050 has quit [Remote host closed the connection]
<gbisson> xdarklight: I based my defconfig on khadas one (their 5.14 branch) I'll check the PWM driver
<gbisson> xdarklight: looks like i have all the config already enabled :(
<gbisson> xdarklight: you confirm that in your case it appears under /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors?
<xdarklight> gbisson: I don't have any A311D based boards but it should list all frequencies which are defined in arch/arm64/boot/dts/amlogic/meson-g12b-a311d.dtsi
<xdarklight> gbisson: can you please share your kernel log (dmesg)?
sputnik_ has joined #linux-amlogic
<xdarklight> gbisson: just checked on an GXL based board: /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governor has the following in it: ondemand userspace powersave performance
<xdarklight> gbisson: do you see the frequencies which you expect in /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies ?
<gbisson> xdarklight: no I don't see any cpufreq folder which is why I was surprised
tdebrouw has quit [Quit: Leaving.]
<xdarklight> gbisson: can you please share the output of "cat /sys/kernel/debug/regulator/regulator_summary" and "cat /sys/kernel/debug/clk/clk_summary" ?
<xdarklight> gbisson: also in your kernel log I see that it detected an AR8035 RGMII PHY. are you expecting this to work at the same time as the internal 100M PHY?
sputnik_ has quit [Remote host closed the connection]
<gbisson> xdarklight: for the ethernet I expected to be able to have 2 ports: 1 external PHY + 1 internal PHY, but I now realize that there's only 1 MAC
<xdarklight> gbisson: yep, one MAC means the choice between external or internal PHY is exclusive
sputnik_ has joined #linux-amlogic
<gbisson> xdarklight: thanks for the confirmation. I edited the gist to add the output you requested.
<xdarklight> gbisson: thanks. regulator output is suspicious since it's not showing any VDDCPU* regulator. can you please check your .dts and make sure that 1) each CPU node has a cpu-supply property 2) this cpu-supply refers a regulator (typically one which has compatible = "pwm-regulator") and 3) that the PWM controller which is used in the "pwms" property of the regulator has status = "okay";
<xdarklight> for step 3) you can also check cat /sys/kernel/debug/pwm
<gbisson> xdarklight: oh actually we're using FAN parts for the regulators, maybe i'm simply missing their conf, lemme check
<gbisson> xdarklight: indeed the fan5355 were missing their drivers...
<xdarklight> gbisson: ah, great that it works now :-)
<gbisson> xdarklight: thanks for the support!
<xdarklight> gbisson: you're welcome!
buzzmarshall has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik has joined #linux-amlogic
sputnik is now known as Guest6552
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
vagrantc has joined #linux-amlogic
Guest6552 has quit [Remote host closed the connection]