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
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
<gbisson> ndufresne: FYI I tried your v4l2videodec series about dynamic resolution change and it didn't fix the VFIFO issue but it might be because of my test env (debian bullseye with gst1.18 whereas your series was made on 1.19) so I'll double check on a more recent distro
Las[m] has joined #linux-amlogic
Tartarus has joined #linux-amlogic
<gbisson> narmstrong: hi, regarding the mmc clk phase, is the patch a wip because aml changes the phase depending on the speed?
<gbisson> narmstrong: any guidlines for adding combinations to the pinctrl driver? By that I mean how do you decide the order? For instance for pwm_f why is the order "GPIOX GPIOH", is it to match the doc order?
<ndufresne> gbisson: ack
<narmstrong> gbisson: it’s wip because the actual solution would need more work to implement yes
<narmstrong> gbisson: i don’t understand your question about pinctrl combinations
<gbisson> narmstrong: I'm trying to understand the order of the different options, for pwm_f for instance it is not alphabetical order nor pin number order, my guess is it is in doc order
<narmstrong> line 1071 ?
<narmstrong> gbisson: order isn't important at all
<gbisson> why is it x first, then h? because I want to add z and a options
<gbisson> ok, just making sure if there was any logic behind it
<narmstrong> the only thing important is the meson_g12a_periphs_groups mapping
<gbisson> ok, my patch is working right now, I can use the pwm_f on another pin so I know it is working, it's just that I wanted to check the order before submission, I'll try to do that today
buzzmarshall has joined #linux-amlogic
jernej has joined #linux-amlogic
jernej has quit [Quit: Konversation terminated!]
jernej has joined #linux-amlogic
chewitt has joined #linux-amlogic
<gbisson> narmstrong: for AOSP, GKI isn't used because uboot isn't capable to merging the ramdisk from vendor_boot yet correct?
<narmstrong> gbisson: I haven't followed latest GKI requirements, this seems new to me
<gbisson> narmstrong: ok no problem I'll look into it later, current way to build should be ok to get started anyway
<narmstrong> gbisson: for kernel, GKI would need an effort to either: add meas support to yukawa to use panfrost OR build kbase arm driver and list all required API for this driver
<gbisson> narmstrong: oh ok, I'm surprised mali isn't supported in the standard kmi, anyway it's fairly easy to update that list, I thought the limitation was coming from U-Boot and vendor_boot support
vagrantc has joined #linux-amlogic
chewitt has quit [Quit: Zzz..]
jelly is now known as le
le is now known as jelly
jernej has quit [Ping timeout: 240 seconds]