<marex>
whether ther pinctrl-0 &nor_pins are actually configured in the pinmux hardware
<bswartz>
It says pinctrl-0 = <&nor_pins>; in that file
<bswartz>
But where else do I have to look?
mmu_man has quit [Ping timeout: 245 seconds]
<bswartz>
I tried the lower frequency and no change
<bswartz>
When I follow the include chain back to meson-g12-common.dtsi I see the nor_pins are defined there
<marex>
drivers/pinctrl/meson/pinctrl-meson-g12a.c -> see if that configures the pin groups as it should
<bswartz>
I don't know what I'm comparing this to
<bswartz>
The driver defines 6 pins related to NOR flash, and groups them
<bswartz>
The dts file refers to 4 of them
<bswartz>
I have no idea if the pin mappings are correct
<bswartz>
The config definitely enables this pinmux driver
<marex>
bswartz: either dump the pinmux controller registers and compare with downstream u-boot, or check datasheet -> pinmux section , for the SPI NOR IOMUX settings
<bswartz>
How would one dump the pinmux controller registers?
<bswartz>
Oh I just found the pinmux command
<bswartz>
There is a lot here
<marex>
bswartz: md 0xaddress -> address is in SoC datasheet
<marex>
I am not familiar with the details of the amlogic soc
<bswartz>
Right
<marex>
but there should be something like iomux/pinmux/gpio-mux whatever section in the datasheet
<bswartz>
I will have to go digging to find datasheet
<bswartz>
The weird thing is that the u-boot documentation says that SPI flash is definitely working for this board
<marex>
look at the memory map, look up the pin controller address in DT -> determine the name of that block -> look at the chapter
<bswartz>
So someone must have tested it at some point and it must have worked
<marex>
bswartz: where does it say so ?
<marex>
bswartz: reset on the commit which added that information ?
<bswartz>
Last time I looked at this I mixed up S905 and S905X3
<bswartz>
FML
<bswartz>
Okay well this solves the mystery -- it doesn't work yet
<bswartz>
Thanks for the help, I'm going to bed
<marex>
U-Boot for ODROID-HC4 (S905X3) ... so uh ... isn't this the board you have ?
<bswartz>
Yes it's the one
<marex>
oh, hum
<marex>
bswartz: does it work in Linux ?
<bswartz>
Yeah it works fine in Linux and with vendor uboot
<marex>
In mainline Linux ?
<bswartz>
Yeah
<marex>
if so, then just git log drivers/mtd/ or drivers/spi/ or wherever that spifc driver resides these days and see what they did to support this SoC
<marex>
it would likely be simple to add
<bswartz>
Yeah but I'm too tired to work on it tonight
<bswartz>
I'll look again later
macromorgan has joined #u-boot
indy- has quit [Ping timeout: 260 seconds]
ewwphoria has joined #u-boot
sakman_ has joined #u-boot
persmule has quit [Remote host closed the connection]
sakman has quit [Ping timeout: 260 seconds]
naoki has quit [Quit: naoki]
sng has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng has joined #u-boot
sng has quit [Ping timeout: 260 seconds]
sakman_ has quit [Read error: Connection reset by peer]
sakman_ has joined #u-boot
sng has joined #u-boot
sng_ has joined #u-boot
sng has quit [Ping timeout: 246 seconds]
sakman__ has joined #u-boot
sakman_ has quit [Ping timeout: 246 seconds]
sng_ has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Ping timeout: 260 seconds]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
naoki has joined #u-boot
Hypfer1 has joined #u-boot
Hypfer has quit [Ping timeout: 250 seconds]
Hypfer1 is now known as Hypfer
sakman__ has quit [Read error: Connection reset by peer]
sakman__ has joined #u-boot
mmu_man has joined #u-boot
sng_ has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng has quit [Read error: Connection reset by peer]
mmu_man has joined #u-boot
sng has joined #u-boot
mmu_man has quit [Ping timeout: 245 seconds]
mmu_man has joined #u-boot
bq has quit [Ping timeout: 258 seconds]
sng has quit [Remote host closed the connection]
bq has joined #u-boot
sng has joined #u-boot
bq has quit [Ping timeout: 258 seconds]
vulpes2[m] has quit [Read error: Connection reset by peer]
LinuxHackerman has quit [Write error: Connection reset by peer]
jluthra has quit [Read error: Connection reset by peer]
<sjg1>
sng: I see. So long as there are docs and examples I expect people can figure it out
<sjg1>
sng: It seems that the main hangup with binman is that it doesn't use files for everything
<sng>
sjg1 very true. it takes some time to get around the idea of nodes being representative of binaries. that is little more trickier when it comes to section images.
<sng>
sjg1 nonetheless, i have put out the v7 of the patches. kindly take a look.
sng has quit [Read error: Connection reset by peer]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
<sjg1>
Forty-Bot: Re: " find a board with CONFIG_FOO enabled, or with CONFIG_FOO but not CONFIG_BAR" - you can use moveconfig.py for that
<sjg1>
Forty-Bot: What Tom is talking about is having buildman automatically build boards with a certain CONFIG combination. Unfortunately it takes a while to build that database (moveconfig.py -b)
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
sng has quit [Remote host closed the connection]
sng has joined #u-boot
justache is now known as reddit-boat
reddit-boat is now known as justache
sng_ has joined #u-boot
sng has quit [Read error: Connection reset by peer]
sng_ has quit [Remote host closed the connection]
<Tartarus>
Now I do think that with some dep rules, for the users of buildman that we have, we could possibly ship the db, and if not, no worry about it too much