buzzmarshall has quit [Quit: Konversation terminated!]
vagrantc has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
Daaanct12 has joined #linux-amlogic
Daanct12 has quit [Ping timeout: 248 seconds]
naoki has quit [Quit: naoki]
ldevulder has joined #linux-amlogic
George41 has joined #linux-amlogic
marc|gonzalez has joined #linux-amlogic
<marc|gonzalez>
narmstrong: xdarklight: Hello! Is it possible that a node uart-a-ao-c is missing in arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi ?
<marc|gonzalez>
(inside the ao_pinctrl: pinctrl@14 node)
<narmstrong>
marc|gonzalez: it’s probable if none of the current board used it
<narmstrong>
Or exposed it
<marc|gonzalez>
AFAIU, my board muxes the console & the SDcard slot, and apparently the pin setup depends on uart-a-ao-c
<marc|gonzalez>
(I must say that I know very little about this topic)
<marc|gonzalez>
If I'm not mainlining support for a board that uses these pins, there is no point in submitting a patch for the node?
ndufresne0 has joined #linux-amlogic
<marc|gonzalez>
narmstrong: also, did you see my email about the typo in the 3rd patch? I don't know if there are git fixups at this stage?
<narmstrong>
marc|gonzalez: you can but if it’s untestable there’s little point in doing this
<narmstrong>
marc|gonzalez: I saw this, I haven’t sent the pr yet so I can fix stuff
<marc|gonzalez>
narmstrong: untestable = on a non-public board?
<narmstrong>
marc|gonzalez: whatever board, if you can validate it then yes it’s ok to be upstreamed
<marc|gonzalez>
I have validated it on the sei530 board. I tried using a different pin config, and the console stopped working :)
<marc|gonzalez>
Maybe some baylibre devs have an sei530 board to test with
<phh>
[13:28:40] <marc|gonzalez> AFAIU, my board muxes the console & the SDcard slot, and apparently the pin setup depends on uart-a-ao-c <--- they all do
<marc|gonzalez>
phh: OK then I am confused why the pin setup is different than on the sei510 board?
<marc|gonzalez>
Is it a minor tweak from SEI?
<phh>
marc|gonzalez: because "normal" people solder serial port, and we're lazy, we just use the sdcard connector rather than dismantling the box
<phh>
but we do have the same non-sd "debug" uarts test points as sei510
<marc|gonzalez>
phh: you mean the data path are muxed, but our board goes further and muxes the physical slot?
<phh>
marc|gonzalez: our board doesn't do anything specific
<phh>
it's the way we use it
<marc|gonzalez>
My confusion stems from the different pin setup required for the sei530 board
<phh>
it's not related to the board, it's only related to the fact that the serial port you're using is over serial port, but you could just dismantle the box and solder the serial port on the PCB, and you'd be using same device-tree as SEI510
<phh>
amlogic bootloader automatically detects on boot whether you have the uart-over-sd-connector adapter, and changes pinmux based on that
<phh>
vendor kernel also does that auto-detection
<marc|gonzalez>
For the record, mainline reports "meson-g12a-pinctrl ff634400.bus:pinctrl@40: pin GPIOC_2 already requested by ff803000.serial; cannot claim for ffe05000.sd"
ndufresne0 has quit [Ping timeout: 252 seconds]
ndufresne6 has joined #linux-amlogic
ndufresne6 has quit [Client Quit]
ndufresne9 has joined #linux-amlogic
ndufresne9 has quit [Client Quit]
ndufresne2 has joined #linux-amlogic
ndufresne2 has quit [Client Quit]
ndufresne3 has joined #linux-amlogic
ndufresne3 has quit [Client Quit]
<narmstrong>
this auto detection could be done by u-boot, and DT altered to enabled the UART instead of the SD port, but to far this isn't needed on the public SBC boards
<narmstrong>
we have access to debug uart over headers
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-amlogic
JohnnyonFlame has quit [Ping timeout: 248 seconds]
<hays>
has anyone had the issue where occasionally boot gets stuck at uboot prompt for some reason without hitting a key or even having serial console connected?
<hays>
i wonder if there is noise on the pin header
<hays>
seeing it with n2-plus
<hays>
somewhere between 2-5% of the time
<narmstrong>
yep it must be noise on the uart
<hays>
i wonder if i can patch or configure uboot to require a specific key
<hays>
hmm you know what i bet this is just happening because i have that long serial uart attached to it and it is disconnected on the other end. basically i've made an antenna
<xdarklight>
you have to make a better antenna for UART over the air ;-)
<xdarklight>
just joking, chewitt recently found CONFIG_AUTOBOOT_STOP_STR, CONFIG_AUTOBOOT_DELAY_STR and CONFIG_AUTOBOOT_KEYED
<xdarklight>
I think these (in some combination) can be used to make u-boot only pause for a specific string
Daaanct12 has quit [Remote host closed the connection]
Daaanct12 has joined #linux-amlogic
kenny has joined #linux-amlogic
Daaanct12 has quit [Remote host closed the connection]
<Cheaterman>
It seems really good from what I can see and really compatible with their usage ; I was wondering if you'd have some comments
<Cheaterman>
It's worth noting they're a company too, not an individual maker, so if you have alternatives for sourcing that might be more reliable than Aliexpress (if more expensive) please let me know
leadf00t has joined #linux-amlogic
<leadf00t>
<waves> Hello!
<Cheaterman>
Welcome leadf00t :-) they're the pal in question hehe
<leadf00t>
I ordered an S922X SOM + carrier board that has a MIPI DSI conenctor. I was wondering if there was a chance at all I'd be able to get an LCD panel working with it :)
<leadf00t>
I'm working with Waveshare and their panels, so hopefully they might have some tips.
<leadf00t>
Is the S922X known to work with MIPI DSI panels already ?