<macromorgan>
is there an easy way to get the i2c bus the PMIC is on in SPL mode in U-Boot? Wondering if there's a macro or something I'm missing...
<macromorgan>
I figured out that if I pull PE11 high I can check the input to see if I have a joystick or not (0 = joystick, 1 = no) and PG5 pulled high can check if I have wifi or not (0 = wifi and 1 = no)
<macromorgan>
now I'm just trying to figure out how to probe the same i2c bus as the PMIC for a device at address 0x51
<apritzel>
can't you just read a PMIC register and see if that fails?
<macromorgan>
I need to read a register on a device other than the PMIC
<macromorgan>
sometimes an external RTC is present and sometimes it's not
<macromorgan>
I want to avoid hard coding the i2c bus if possible in case other ones get enabled
<macromorgan>
but I can hard code the path on the device tree
apritzel has quit [Ping timeout: 480 seconds]
gsz has joined #linux-sunxi
macromorgan has quit [Ping timeout: 480 seconds]
macromorgan has joined #linux-sunxi
gsz_ has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]
bauen1 has joined #linux-sunxi
gsz_ has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
<apritzel>
macromorgan: are we still talking about detecting one out of five very specific devices? And you do this in the SPL?
<apritzel>
macromorgan: assuming yes and yes: there is no point in being generic here: this is a very specific firmware quirk, you can (and should) hardcode everything.
<apritzel>
If a sixth device appear, we will deal with that then
<apritzel>
we don't promise anything other than: this firmware image works for any of those specifically listed Anbernic devices. Future devices are not supported (yet).
<apritzel>
besides: in the SPL you have only one I2C bus anyway: the one selected via CONFIG_{R_,}I2C{,0,1}_ENABLE. And the RTC *is* on the same bus as the PMIC, isn't it?
ftg has quit [Read error: Connection reset by peer]
Schimsalabim has quit [Read error: Connection reset by peer]